@denzz221/baileys@8.1.1
WhatsApp API Modification By denzz221
AI Security Review
scanned 1h ago · by lpm-firewall-aiThe package automatically follows a hard-coded WhatsApp newsletter after socket creation, using the user's account without a request to follow that channel. This is a concrete, unsolicited account action and warrants blocking.
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 a messages socket; the action is scheduled for 90 seconds later.
Impact
The user's account is made to follow a channel selected by the package publisher.
Mechanism
A timer sends a WhatsApp newsletter FOLLOW query for the hard-coded channel ID, without an explicit user request.
Attack narrative
When the application creates a messages socket, it constructs the newsletter socket, which schedules a FOLLOW query 90 seconds later for the hard-coded channel 120363400780200098@newsletter. This uses the user's WhatsApp account to perform an unrequested action toward a publisher-chosen target.
AI rationale
The package automatically follows a hard-coded WhatsApp newsletter after socket creation, using the user's account without a request to follow that channel. This is a concrete, unsolicited account action and warrants blocking.
Evidence
lib/Socket/messages-send.jslib/Socket/newsletter.js
Network endpoints1
WhatsApp newsletter w:mex query via the existing socket
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- Creating the messages socket constructs the newsletter socket.
- The newsletter socket automatically sends a FOLLOW query for the fixed channel 120363400780200098@newsletter after 90 seconds.
- The package exposes the same FOLLOW query as its explicit newsletterFollow operation.
- The preinstall script only checks the Node.js major version and exits if it is below 20.
Evidence against
- The package is a WhatsApp API library, so WhatsApp network access and user-requested account operations fit its purpose.
- The flagged preinstall hook performs a Node.js version check; the inspected source shows no network or data collection there.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
5 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 = @denzz221/baileys@8.0.5
matchedPath = lib/Utils/messages-media.js
matchedIdentity = npm:QGRlbnp6MjIxL2JhaWxleXM:8.0.5
similarity = 1.000
summary = normalized source hash matched finalized malicious source
Findings
4 High3 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighKnown Malware Source Similaritylib/Utils/messages.js
HighKnown Malware Source Fingerprint Signaturelib/Utils/messages-media.js
MediumNetwork
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @denzz221/baileys@8.1.1.
See all versions of @denzz221/baileys for other recorded verdicts.
- Avoid installing @denzz221/baileys@8.1.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.