noxleys-baileys@2.0.0
WhatsApp Web API Library
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package silently performs publisher-selected newsletter follow and mute actions using the user's authenticated WhatsApp session whenever the connection opens. This is an unrequested account action, so the package is malicious.
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 WhatsApp connection opens; the actions begin after a 30-second delay.
Impact
The authenticated account is changed without the user's request, including joining publisher-selected channels.
Mechanism
newsletter.js fetches newsletter IDs from a publisher-controlled GitHub URL and follows then mutes each valid ID. messages-recv.js also follows and mutes two hard-coded IDs hidden as character codes.
Attack narrative
When a WhatsApp session connects, the socket automatically fetches a publisher-controlled list of newsletter IDs and follows and mutes each valid channel. A second connection handler performs the same actions for two fixed IDs whose values and action names are encoded in the source. These account changes happen without an explicit user request.
AI rationale
The package silently performs publisher-selected newsletter follow and mute actions using the user's authenticated WhatsApp session whenever the connection opens. This is an unrequested account action, so the package is malicious.
Evidence
lib/Socket/newsletter.jslib/Socket/messages-recv.jslib/index.js
Network endpoints1
raw.githubusercontent.com
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package exports makeWASocket, which creates the socket layers containing the automatic actions.
- When the WhatsApp connection opens, newsletter.js waits 30 seconds and fetches channel IDs from a publisher-controlled GitHub URL.
- For each fetched newsletter ID, the code automatically follows and then mutes it.
- messages-recv.js encodes two fixed newsletter IDs and the names of the follow and mute methods, then invokes those actions after the connection opens.
- The preinstall hook only checks the Node.js major version and exits on versions below 20.
Evidence against
- The manifest describes the package as a WhatsApp Web API library, so WhatsApp socket operations are part of its stated purpose.
- The preinstall hook performs a Node.js version check; no install-time data collection was identified.
Behavioral surface
ChildProcessCryptoEvalFilesystemNetworkWebSocket
HighEntropyStrings
Source & flagged code
9 flaggedpackage.jsonView file
•scripts.preinstall = node ./engine-requirements.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkglib/WABinary/constants.jsView file
603patternName = google_api_key
severity = high
line = 603
High
High Secret
Package contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L603603patternName = google_api_key
severity = high
line = 603
High
Secret Pattern
Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L603Findings
7 High3 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHigh Secretlib/WABinary/constants.js
HighSemantic Analysis LimitedWAProto/index.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighKnown Malware Source Similaritylib/Utils/messages.js
HighKnown Malware Source Fingerprint Signaturelib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
MediumNetwork
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEvallib/Utils/messages-media.js
Affected versions and remediation
This report applies to noxleys-baileys@2.0.0.
See all versions of noxleys-baileys for other recorded verdicts.
- Avoid installing noxleys-baileys@2.0.0. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.