@zetagoaurum-socket/wasocket@2.2.1
WhatsApp API Modification ZetaGo
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18927 confirms this npm version as malicious.
WhatsApp API Modification ZetaGo
OpenSSF/OSV advisory MAL-2026-18927 confirms this npm version as malicious.
LPM's AI review found this version suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The package silently saves incoming WhatsApp sender identifiers and timestamps into files in the consuming project directory, an unexpected data-collection behavior for a socket library. The inspected source shows no exfiltration, so this warrants a warning rather than a malicious verdict.
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
package.json1 critical · 1 highlib/Utils/link-preview.js1 highlib/Utils/messages-media.js1 highWAProto/index.js1 mediumpackage.json2 findingslib/Utils/link-preview.js1 findinglib/Utils/messages-media.js1 findingTarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage contains source files above the normal full-analysis size ceiling.
WAProto/index.jsView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
lib/Utils/link-preview.jsView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/Utils/messages-media.jsView on unpkgThis report applies to @zetagoaurum-socket/wasocket@2.2.1.
See all versions of @zetagoaurum-socket/wasocket for other recorded verdicts.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.
WAProto/index.js1 finding