@denzz221/baileys@8.1.2
WhatsApp API Modification By By DenixXvynix
AI Security Review
scanned 1h ago · by lpm-firewall-aiSocket setup automatically follows a hard-coded WhatsApp newsletter after a delay, an account action the user did not request. The Node-version preinstall check and media processing code are ordinary package behavior and do not explain or authorize that action.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Creating the messages/newsletter socket as part of the normal socket setup.
Impact
The connected WhatsApp account follows a channel without the user requesting that action.
Mechanism
A 90-second timer sends a FOLLOW query for the hard-coded newsletter JID; failures are silently discarded.
Attack narrative
When the socket setup creates a newsletter socket, it schedules a delayed FOLLOW query for a hard-coded WhatsApp newsletter. This uses the connected account to follow a publisher-selected target without an explicit user request.
AI rationale
Socket setup automatically follows a hard-coded WhatsApp newsletter after a delay, an account action the user did not request. The Node-version preinstall check and media processing code are ordinary package behavior and do not explain or authorize that action.
Evidence
lib/Socket/newsletter.jslib/Socket/messages-send.js
Network endpoints1
WhatsApp (S_WHATSAPP_NET)
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- Creating the newsletter socket schedules a FOLLOW request to the hard-coded newsletter `120363400780200098@newsletter` after 90 seconds, with errors silently ignored.
- The messages socket constructs the newsletter socket, and the package’s exported `makeWASocket` creates the registration socket layer.
- The FOLLOW request is sent as a WhatsApp `w:mex` query to `S_WHATSAPP_NET`.
- The preinstall hook only runs a Node-version check and exits for versions below 20.
- The media utility uses ffmpeg to extract video thumbnails, a feature-related use of process execution.
Evidence against
- The preinstall script does not contact a host or collect data; it checks the Node major version.
- Media network and filesystem operations are used for media download, upload, and thumbnail processing.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStrings
Source & flagged code
6 flaggedpackage.jsonView file
•dependencies changed=libsignal; devDependencies changed=@adiwajshing/eslint-config
Critical
Manifest Confusion
Tarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkg•scripts.preinstall = node ./engine-requirements.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgWAProto/index.jsView file
•path = WAProto/index.js
kind = oversized_source_file
sizeBytes = 8472622
magicHex = [redacted]
Medium
Oversized Source File
Package contains source files above the normal full-analysis size ceiling.
WAProto/index.jsView on unpkgFindings
1 Critical4 High3 Medium5 Low
CriticalManifest Confusionpackage.json
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighKnown Malware Source Similaritylib/Utils/messages.js
HighKnown Malware Source Fingerprint Signaturelib/Utils/messages-media.js
MediumNetwork
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @denzz221/baileys@8.1.2.
See all versions of @denzz221/baileys for other recorded verdicts.
- Avoid installing @denzz221/baileys@8.1.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.