@denzz221/baileys@8.0.8
WhatsApp API Modification By denzz221
AI Security Review
scanned 1h ago · by lpm-firewall-aiThe package automatically follows a hard-coded WhatsApp newsletter when its normal client socket is created. This is an unrequested account action toward a target chosen by the publisher, so the package 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
Creating the normal message socket; the follow request is scheduled for 90 seconds later.
Impact
Uses the user's WhatsApp account to follow a channel selected by the package publisher.
Mechanism
A timer calls the newsletter query with a hard-coded newsletter ID and the FOLLOW query ID, without an explicit user request.
Attack narrative
When the application creates its regular message socket, the package schedules a WhatsApp newsletter follow request for 90 seconds later. The request targets newsletter 120363400780200098@newsletter and uses the FOLLOW query ID, so it acts through the user's connected account without an explicit request to follow that publisher-selected channel.
AI rationale
The package automatically follows a hard-coded WhatsApp newsletter when its normal client socket is created. This is an unrequested account action toward a target chosen by the publisher, so the package is malicious.
Evidence
lib/Socket/newsletter.jslib/Socket/messages-send.jslib/Types/Newsletter.js
Network endpoints1
s.whatsapp.net
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Creating the newsletter socket schedules a request after 90 seconds to follow the hard-coded newsletter 120363400780200098@newsletter.
- The normal message-socket constructor calls makeNewsletterSocket, so the scheduled action runs when the client socket is created.
- The hard-coded request uses QueryIds.FOLLOW, which is defined as the FOLLOW query.
Evidence against
- The package is a WhatsApp API library, so connecting to WhatsApp and implementing user-requested newsletter actions fit its purpose.
- The preinstall script only checks that Node.js is version 20 or newer; prepare is empty.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedUrlStrings
GitDependency
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 High4 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
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.0.8.
See all versions of @denzz221/baileys for other recorded verdicts.
- Avoid installing @denzz221/baileys@8.0.8. 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.