@ruthless-imperium/baileys@1.0.1
WhatsApp Web API Library
AI Security Review
scanned 3h ago · by lpm-firewall-aiThe package performs unsolicited follows on the user's WhatsApp account after connection, targeting hard-coded newsletters. This is an account action toward publisher-chosen targets and warrants blocking.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
A WhatsApp connection opens; one action runs after 30 seconds and another after 5 seconds.
Impact
Uses the user's WhatsApp account to follow channels they did not choose or request.
Mechanism
The receive socket decodes an obfuscated hard-coded newsletter identifier and calls newsletterFollow. The newsletter socket resolves a hard-coded invite code to a channel and sends a FOLLOW query.
Attack narrative
After the WhatsApp socket connects, the package automatically follows a hard-coded newsletter identifier and also resolves a hard-coded invite code before following that channel. These account actions are triggered by connection startup without a user request.
AI rationale
The package performs unsolicited follows on the user's WhatsApp account after connection, targeting hard-coded newsletters. This is an account action toward publisher-chosen targets and warrants blocking.
Evidence
lib/Socket/messages-recv.jslib/Socket/newsletter.js
Network endpoints1
S_WHATSAPP_NET
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- When the WhatsApp connection opens, the receive socket waits 30 seconds and iterates a hard-coded newsletter ID, invoking an obfuscated socket method that decodes to newsletterFollow.
- The newsletter socket schedules an automatic follow five seconds after connection opens, using a hard-coded invite code and issuing the FOLLOW query.
- The manifest’s preinstall hook only runs engine-requirements.js, which checks for Node.js 20 or newer and exits on older versions.
Evidence against
- The package describes itself as a WhatsApp Web API library, so WhatsApp network access and newsletter operations can serve its stated purpose when requested by the user.
- The install-time hook performs a Node.js version check; the identified automatic account actions occur at runtime after connection.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkWebSocket
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 unpkg•matchType = previous_version_dangerous_delta
matchedPackage = @ruthless-imperium/baileys@1.0.0
matchedIdentity = npm:[redacted]:1.0.0
similarity = 0.968
summary = stored previous version shares package body but lacks this dangerous source file
High
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
package.jsonView on unpkglib/WABinary/constants.jsView file
603patternName = google_api_key
severity = high
line = 603
High
High Secret
Findings
7 High4 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
HighPrevious Version Dangerous Deltapackage.json
HighSecret Patternlib/WABinary/constants.js
MediumNetwork
MediumEnvironment Vars
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
Low
Affected versions and remediation
This report applies to @ruthless-imperium/baileys@1.0.1.
See all versions of @ruthless-imperium/baileys for other recorded verdicts.
- Avoid installing @ruthless-imperium/baileys@1.0.1. 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.