@axo_cuy/baileyss@1.0.1
A WebSockets library for interacting with WhatsApp Web.
AI Security Review
scanned 2h ago · by lpm-firewall-aiThe package performs an unsolicited WhatsApp account action: normal socket construction schedules a follow request to a hard-coded newsletter. The action is independent of an explicit follow request, so this 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 consumer calls the package’s normal socket creation flow; the follow request runs about 10 seconds later.
Impact
Uses the user’s connected WhatsApp account to follow a channel without the user requesting that action.
Mechanism
The newsletter socket decodes a hard-coded newsletter ID and submits a FOLLOW request through the WhatsApp messaging query.
Attack narrative
When the package’s normal messaging socket is created, its newsletter layer schedules a follow request for a fixed, encoded newsletter ID after 10 seconds. This uses the connected WhatsApp account to follow a publisher-selected channel without the user asking for it.
AI rationale
The package performs an unsolicited WhatsApp account action: normal socket construction schedules a follow request to a hard-coded newsletter. The action is independent of an explicit follow request, so this is malicious.
Evidence
lib/Socket/newsletter.jslib/Socket/username.jslib/Socket/messages-send.jslib/Socket/messages-recv.jslib/Socket/business.jslib/Socket/index.js
Network endpoints1
wss://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
- Creating a newsletter socket schedules an unconditional follow request after 10 seconds, using a base64-encoded fixed newsletter ID.
- The newsletter socket is built into the normal messaging socket construction chain.
- The package’s makeWASocket function creates the core socket layers that reach the messaging stack.
- The preinstall script only checks the Node.js major version.
Evidence against
- The package is described as a WhatsApp Web library, and newsletter operations are part of its feature set.
- No credential theft or local file changes were identified in the reviewed paths.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
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 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 High4 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
HighKnown Malware Source Fingerprint Signaturelib/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
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptolib/Utils/validate-connection.js
Affected versions and remediation
This report applies to @axo_cuy/baileyss@1.0.1.
See all versions of @axo_cuy/baileyss for other recorded verdicts.
- Avoid installing @axo_cuy/baileyss@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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.