@denzz221/baileys@8.1.3
WhatsApp API Modification By By DenixXvynix
AI Security Review
scanned 1h ago · by lpm-firewall-aiThe package automatically follows a hard-coded WhatsApp newsletter when its messages socket is created. 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 messages socket; the follow request is scheduled for 90 seconds later.
Impact
An account action the user did not request is performed with their WhatsApp session.
Mechanism
The newsletter socket sends a FOLLOW query for a hard-coded newsletter JID, without asking the user.
Attack narrative
When the messages socket is created, it creates a newsletter socket that schedules a FOLLOW query to the hard-coded newsletter 120363400780200098@newsletter after 90 seconds. This uses the active WhatsApp session to follow a publisher-selected channel without an explicit user request.
AI rationale
The package automatically follows a hard-coded WhatsApp newsletter when its messages socket is created. This is an unauthorized account action, so the package should be blocked.
Evidence
lib/Socket/newsletter.jslib/Socket/messages-send.js
Network endpoints1
WhatsApp socket protocol
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- Creating the messages socket constructs a newsletter socket.
- The newsletter socket schedules a FOLLOW request to the hard-coded channel 120363400780200098@newsletter after 90 seconds, without a user request.
- The preinstall hook only runs a Node version check and exits for versions below 20.
Evidence against
- The flagged media utility’s shell execution is used to extract video thumbnails with ffmpeg.
- The package is a WhatsApp client library, so its socket protocol and network activity serve its stated purpose.
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.1.3.
See all versions of @denzz221/baileys for other recorded verdicts.
- Avoid installing @denzz221/baileys@8.1.3. 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.