@chatbridgeworld/baileys@1.0.0
WhatsApp Baileys multifunction by ChatBridge
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package silently uses the user's authenticated WhatsApp account to follow publisher-selected newsletters whenever the ordinary socket is created. This is an unrequested account action and meets the malicious account-action rule.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A user creates the package's normal WhatsApp socket; the action runs after a 90-second delay.
Impact
The user's account joins channels chosen by the publisher without a request from the user.
Mechanism
The newsletter socket schedules FOLLOW queries for a hard-coded list of newsletter JIDs using the authenticated WhatsApp connection.
Attack narrative
Creating the normal socket stack reaches makeNewsletterSocket, which schedules FOLLOW requests for hard-coded newsletter JIDs after 90 seconds. These account actions use the user's WhatsApp connection to join channels selected by the package publisher without an explicit request.
AI rationale
The package silently uses the user's authenticated WhatsApp account to follow publisher-selected newsletters whenever the ordinary socket is created. This is an unrequested account action and meets the malicious account-action rule.
Evidence
lib/index.jslib/Socket/messages-send.jslib/Socket/newsletter.js
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The public entry point exports makeWASocket.
- The ordinary message socket constructs a newsletter socket as part of socket setup.
- Newsletter socket setup schedules a timer containing hard-coded newsletter JIDs.
- When the timer fires, the code sends a FOLLOW action for each listed JID.
- The preinstall script only checks the Node.js major version.
Evidence against
- The package is presented as a WhatsApp Baileys library, so WhatsApp network access and newsletter features fit its purpose.
- The install-time script does not contact the network or collect data.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedUrlStrings
GitDependency
Source & flagged code
4 flaggedpackage.jsonView file
•scripts.preinstall = node ./engine-requirements.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgWAProto/index.jsView file
•path = WAProto/index.js
kind = oversized_source_file
sizeBytes = 8472622
magicHex = [redacted]
Medium
Oversized Source File
Package contains source files above the normal full-analysis size ceiling.
WAProto/index.jsView on unpkglib/Utils/messages-media.jsView file
•matchType = normalized_sha256
matchedPackage = ipungg-baileys@1.0.4
matchedPath = lib/Utils/messages-media.js
matchedIdentity = npm:aXB1bmdnLWJhaWxleXM:1.0.4
similarity = 1.000
summary = normalized source hash matched finalized malicious source
Findings
3 High4 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighKnown Malware Source Similaritylib/Utils/messages.js
MediumNetwork
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @chatbridgeworld/baileys@1.0.0.
See all versions of @chatbridgeworld/baileys for other recorded verdicts.
- Avoid installing @chatbridgeworld/baileys@1.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.