diezyxhao-baileys@1.3.0
DIEZYXHAO BAILEYS - Advanced WhatsApp Web API Library with Latest Protocol Support
AI Security Review
scanned 3h ago · by lpm-firewall-aiSocket creation automatically uses the user’s WhatsApp account to follow the publisher’s chosen newsletter. The opt-out setting does not make this requested by the user, so this is malicious account abuse.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Creating a messages socket, unless the caller explicitly sets autoFollowChannels to false.
Impact
Uses the user’s WhatsApp account to follow the publisher’s chosen channel without a request, potentially boosting that channel.
Mechanism
The socket schedules a follow request after 15 seconds; its channel manager adds the hard-coded default target and sends the newsletter follow operation.
Attack narrative
When an application creates a messages socket, the package schedules a follow request for the publisher’s hard-coded WhatsApp newsletter. The channel manager includes that target by default and invokes the socket’s follow operation. Users must explicitly opt out with autoFollowChannels=false, so this performs an account action toward a publisher-chosen target without consent.
AI rationale
Socket creation automatically uses the user’s WhatsApp account to follow the publisher’s chosen newsletter. The opt-out setting does not make this requested by the user, so this is malicious account abuse.
Evidence
lib/Socket/newsletter.jslib/Socket/messages-send.jslib/Utils/channel-manager.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
- The package hard-codes the developer’s WhatsApp newsletter as its default follow target; disabling the action requires setting autoFollowChannels to false.
- Creating the messages socket creates the newsletter socket, which schedules the follow action after 15 seconds by default.
- The follow routine includes the hard-coded default channel and calls the socket’s newsletter-follow operation for its target.
Evidence against
- The package is a WhatsApp API library, so WhatsApp network access is expected.
- The manifest has no active install hook; the unauthorized action occurs when the socket is created.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedUrlStrings
GitDependency
Source & flagged code
4 flaggedWAProto/index.jsView file
•stage = ast_semantic_analysis; reason = ast_path_work_budget_exceeded; limitedFiles = 1
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
WAProto/index.jsView on unpkg•path = WAProto/index.js
kind = oversized_source_file
sizeBytes = 4824821
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 = @badzz88/baileys@4.0.0
matchedPath = lib/Utils/messages-media.js
matchedIdentity = npm:QGJhZHp6ODgvYmFpbGV5cw:4.0.0
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Findings
3 High4 Medium5 Low
HighSemantic Analysis LimitedWAProto/index.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighAi Review Evidencelib/Socket/newsletter.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 diezyxhao-baileys@1.3.0.
See all versions of diezyxhao-baileys for other recorded verdicts.
- Avoid installing diezyxhao-baileys@1.3.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.