@denzz221/baileys@8.1.7
WhatsApp API Modification By DenixXvynix
AI Security Review
scanned 1h ago · by lpm-firewall-aiThe package silently follows a hard-coded WhatsApp newsletter through the user’s authenticated account during ordinary socket setup. This is an unrequested account action and warrants blocking.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Normal message socket construction; the follow is scheduled for 90 seconds later.
Impact
The user’s WhatsApp account is made to follow a channel without a request to do so.
Mechanism
A timer calls newsletterWMexQuery with a fixed newsletter ID and the FOLLOW query ID through the authenticated WhatsApp connection.
Attack narrative
When the normal message socket is constructed, the package constructs its newsletter socket too. That socket schedules a FOLLOW request 90 seconds later for newsletter 120363400780200098@newsletter. The request uses the account’s authenticated WhatsApp connection and has no user-request check, causing an account action toward a target chosen by the publisher.
AI rationale
The package silently follows a hard-coded WhatsApp newsletter through the user’s authenticated account during ordinary socket setup. This is an unrequested account action and warrants blocking.
Evidence
lib/Socket/newsletter.jslib/Socket/messages-send.js
Network endpoints1
WhatsApp service via the authenticated socket
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- Creating the newsletter socket schedules a FOLLOW action for the hard-coded newsletter 120363400780200098@newsletter after 90 seconds.
- The message socket factory creates the newsletter socket as part of its normal construction path, so the follow is not gated on a user request.
- The action is sent through the package’s WhatsApp query mechanism using the user’s authenticated socket.
Evidence against
- The preinstall script runs engine-requirements.js, which checks the Node.js major version and exits on versions below 20.
- The flagged fixed newsletter ID in dugong.js appears in forwarded-message attribution within handleEvent, which relays an event to the caller-supplied JID.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedUrlStrings
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 = @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
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 @denzz221/baileys@8.1.7.
See all versions of @denzz221/baileys for other recorded verdicts.
- Avoid installing @denzz221/baileys@8.1.7. 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.