@mrfurryofc/baileys@1.0.3
A WebSockets library for interacting with WhatsApp Web
AI Security Review
scanned 3h ago · by lpm-firewall-aiThe package automatically follows six hard-coded WhatsApp newsletters when a socket connection opens, using the user's account without an explicit request. This is a publisher-directed account action, so the package should be blocked.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The app creates a socket and its WhatsApp connection opens.
Impact
The user's account joins channels selected by the package publisher without an explicit request.
Mechanism
The socket registers an autofollow handler that reads six hard-coded newsletter IDs from the package's branding configuration and calls newsletterFollow for each. BAILEYS_NO_AUTOFOLLOW is only an opt-out.
Attack narrative
When an application using the package creates a WhatsApp socket and connects, the package automatically follows six publisher-selected newsletters with the user's account. The action is only prevented by setting an opt-out environment variable, so it is an unrequested account action.
AI rationale
The package automatically follows six hard-coded WhatsApp newsletters when a socket connection opens, using the user's account without an explicit request. This is a publisher-directed account action, so the package should be blocked.
Evidence
lib/index.jslib/Socket/index.jslib/Custom/autofollow.jsbranding/config.cjslib/Socket/newsletter.js
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package entry point loads the socket module that registers the behavior.
- Creating a socket attaches the autofollow handler automatically.
- The handler runs when the WhatsApp connection opens; an environment variable can disable it, but that is an opt-out.
- The package ships six hard-coded newsletter IDs in its branding configuration.
- For each configured ID, the handler calls the socket's newsletter-follow operation.
Evidence against
- The preinstall hook only checks the Node.js version and exits on versions below 20.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
10 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
600patternName = google_api_key
severity = high
line = 600
High
High Secret
Package contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L600600patternName = google_api_key
severity = high
line = 600
High
Secret Pattern
Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L600Findings
6 High6 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
HighSecret Patternlib/WABinary/constants.js
HighSecret Patternlib/WABinary/constants.d.ts
MediumDynamic Requirelib/Custom/autofollow.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
Affected versions and remediation
This report applies to @mrfurryofc/baileys@1.0.3.
See all versions of @mrfurryofc/baileys for other recorded verdicts.
- Avoid installing @mrfurryofc/baileys@1.0.3. 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.