@denzz221/baileys@7.0.0
WhatsApp API Modification By By DenixXvynix
AI Security Review
scanned 1h ago · by lpm-firewall-aiThe package automatically follows a publisher-chosen WhatsApp newsletter when its messages socket is created. This uses the user's account for an unsolicited account action, 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 messages socket, which is part of ordinary socket construction.
Impact
The account performs an unsolicited follow action toward a publisher-chosen target.
Mechanism
A 90-second timer submits a FOLLOW query for channel 120363400780200098@newsletter through the WhatsApp query function.
Attack narrative
Creating a messages socket initializes the newsletter socket, which schedules a follow request to the hard-coded channel 120363400780200098@newsletter. When the timer fires, it sends the FOLLOW query through the WhatsApp connection, using the account without a user request.
AI rationale
The package automatically follows a publisher-chosen WhatsApp newsletter when its messages socket is created. This uses the user's account for an unsolicited account action, so the package is malicious.
Evidence
lib/Socket/messages-send.jslib/Socket/newsletter.js
Network endpoints1
WhatsApp service (WABinary_1.S_WHATSAPP_NET)
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package is a WhatsApp API library whose main entry point is lib/index.js.
- Creating the messages socket creates the newsletter socket.
- The newsletter socket schedules a follow request to the hard-coded channel 120363400780200098@newsletter.
- The follow request is sent as a query to WhatsApp.
Evidence against
- The preinstall script only checks the Node.js major version and exits on versions below 20.
- The other hard-coded newsletter identifier appears in code that constructs an event message for a supplied recipient.
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.8
matchedPath = lib/Utils/messages-media.js
matchedIdentity = npm:QGRlbnp6MjIxL2JhaWxleXM:8.0.8
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@7.0.0.
See all versions of @denzz221/baileys for other recorded verdicts.
- Avoid installing @denzz221/baileys@7.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.