@ruthless-imperium/baileys@1.0.2
WhatsApp Web API Library
AI Security Review
scanned 3h ago · by lpm-firewall-aiThe package performs publisher-chosen newsletter follow and mute actions automatically when a WhatsApp connection opens. This is unauthorized account activity, so the package is malicious.
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
When the application creates the normal socket and its WhatsApp connection opens.
Impact
Changes the user's WhatsApp newsletter subscriptions and preferences without a request to follow or mute those targets.
Mechanism
The newsletter socket looks up a hard-coded invite and follows it after five seconds. A second handler decodes another fixed newsletter JID, follows it, then mutes it after the connection opens.
Attack narrative
Creating a WhatsApp socket installs connection-open handlers that use the user's authenticated account to follow a hard-coded newsletter and to follow and mute another hard-coded newsletter. These account actions run automatically without the user requesting them.
AI rationale
The package performs publisher-chosen newsletter follow and mute actions automatically when a WhatsApp connection opens. This is unauthorized account activity, so the package is malicious.
Evidence
lib/Socket/messages-send.jslib/Socket/newsletter.jslib/Socket/messages-recv.js
Network endpoints2
web.whatsapp.comwss://web.whatsapp.com/ws/chat
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The standard socket creates the newsletter socket; on connection, it automatically looks up a hard-coded invite and follows that channel.
- A second connection-open handler decodes a fixed newsletter JID and invokes newsletterFollow, then newsletterMute.
- The preinstall script only checks the Node.js version; it does not perform the account action.
Evidence against
- The package describes itself as a WhatsApp Web API library, and newsletter follow and mute operations are part of that API.
- The flagged prepare script only prints a message.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
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.2.
See all versions of @ruthless-imperium/baileys for other recorded verdicts.
- Avoid installing @ruthless-imperium/baileys@1.0.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.