@bellaxchan/bailtech@1.1.0
A WebSockets library for interacting with Customize WhatsApp.
AI Security Review
scanned 2h ago · by lpm-firewall-aiThe default socket-construction path reaches newsletter setup, which schedules a follow to a fixed, publisher-selected channel. This is an unauthorized 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; source fingerprint signature matched known malicious package; routed for review
Trigger
Creating the standard WhatsApp socket; the follow is scheduled for 10 seconds later.
Impact
Uses the connected account to follow a channel selected by the package publisher.
Mechanism
The newsletter socket decodes a fixed newsletter ID and sends a FOLLOW query over WhatsApp’s w:mex protocol without a user request or consent check.
Attack narrative
When the standard socket is created, its constructor chain reaches the newsletter socket, which schedules a follow request for a fixed channel about 10 seconds later and sends it through the user’s WhatsApp connection without consent.
AI rationale
The default socket-construction path reaches newsletter setup, which schedules a follow to a fixed, publisher-selected channel. This is an unauthorized account action, so the package should be blocked.
Evidence
lib/Socket/index.jslib/Socket/communities.jslib/Socket/business.jslib/Socket/messages-send.jslib/Socket/username.jslib/Socket/newsletter.jslib/Socket/mex.jslib/Defaults/index.js
Network endpoints1
wss://web.whatsapp.com/ws/chat
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- Creating the standard socket builds a chain through the messages and username sockets to the newsletter socket.
- The newsletter socket schedules a follow request 10 seconds after construction, decoding a fixed channel ID and making no consent or configuration check.
- The request is sent through WhatsApp’s `w:mex` protocol over the package’s default WhatsApp WebSocket endpoint.
Evidence against
- The package is described as a WhatsApp WebSockets library, and its preinstall script only checks the Node.js version.
- The library exposes ordinary caller-invoked newsletter operations, but that does not explain the scheduled follow to a publisher-selected channel.
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 @bellaxchan/bailtech@1.1.0.
See all versions of @bellaxchan/bailtech for other recorded verdicts.
- Avoid installing @bellaxchan/bailtech@1.1.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.