@wanzforme/bails@2.0.0
A WebSockets library for interacting with WhatsApp Web.
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource inspection confirms an automatic, publisher-selected WhatsApp account action during normal socket construction. The preinstall hook is only a Node version check and does not change that runtime finding.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Creating the package's normal socket stack.
Impact
The authenticated WhatsApp account may subscribe to a newsletter without the account holder requesting it.
Mechanism
A timer issues a newsletter FOLLOW request for a fixed newsletter identifier after ten seconds.
Attack narrative
When the normal socket stack is constructed, it reaches the newsletter socket, which schedules a follow request for a fixed newsletter after ten seconds. The request runs without checking user consent or a setting that disables it, so an authenticated account may be subscribed without its owner asking.
AI rationale
Source inspection confirms an automatic, publisher-selected WhatsApp account action during normal socket construction. The preinstall hook is only a Node version check and does not change that runtime finding.
Evidence
lib/Socket/index.jslib/Socket/messages-send.jslib/Socket/username.jslib/Socket/newsletter.jslib/Socket/mex.js
Network endpoints1
WhatsApp messaging query endpoint
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package exports a socket constructor through its main entrypoint.
- Building the message sending socket constructs the username socket, which constructs the newsletter socket.
- The newsletter socket schedules a FOLLOW request for a hardcoded newsletter ten seconds after construction, without checking consent or configuration.
- The request is sent through the WhatsApp messaging query path.
- The socket constructor merges default and caller configuration before creating the communities socket layer.
Evidence against
- The preinstall hook only checks for Node.js 20 or newer and exits on older versions.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
GitDependency
Source & flagged code
8 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
5 High5 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHigh Secretlib/WABinary/constants.js
HighSemantic Analysis Limitedlib/Utils/business.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
MediumNetwork
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptolib/Utils/validate-connection.js
LowFilesystem
Affected versions and remediation
This report applies to @wanzforme/bails@2.0.0.
See all versions of @wanzforme/bails for other recorded verdicts.
- Avoid installing @wanzforme/bails@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.