@denzz221/baileys@8.0.6
WhatsApp API Modification By denzz221
AI Security Review
scanned 1h ago · by lpm-firewall-aiThe package performs an unrequested account action by following a hard-coded WhatsApp newsletter whenever a normal socket is created. The preinstall hook only checks the Node version, but that does not affect the runtime account 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
A consumer creates the normal socket; the follow query runs 90 seconds after newsletter socket construction.
Impact
The user’s WhatsApp account follows a newsletter chosen by the package publisher.
Mechanism
The timer submits a FOLLOW query for the fixed newsletter ID through the WhatsApp connection, without an explicit follow request from the user.
Attack narrative
When a consumer creates the normal socket, the message socket constructs the newsletter socket. That constructor schedules a FOLLOW query 90 seconds later for the hard-coded newsletter 120363400780200098@newsletter. This uses the consumer’s WhatsApp account to follow a publisher-selected target without a user request.
AI rationale
The package performs an unrequested account action by following a hard-coded WhatsApp newsletter whenever a normal socket is created. The preinstall hook only checks the Node version, but that does not affect the runtime account action.
Evidence
lib/Socket/messages-send.jslib/Socket/newsletter.js
Network endpoints1
WhatsApp service (S_WHATSAPP_NET; @s.whatsapp.net)
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Creating the message socket constructs the newsletter socket, which starts a timer to send a FOLLOW query for the hard-coded newsletter 120363400780200098@newsletter after 90 seconds.
- The newsletter query is sent to the WhatsApp service, and the package’s newsletterFollow method uses the same FOLLOW query ID.
- The preinstall script only checks the Node.js major version and exits for versions below 20.
Evidence against
- The package is a WhatsApp API library, so communicating with WhatsApp is part of its stated purpose.
- The preinstall hook does not contact the network or collect host or project data.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedUrlStrings
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.0.6.
See all versions of @denzz221/baileys for other recorded verdicts.
- Avoid installing @denzz221/baileys@8.0.6. 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.