diezyxhao-baileys@1.3.1
DIEZYXHAO BAILEYS - Advanced WhatsApp Web API Library with Latest Protocol Support
AI Security Review
scanned 3h ago · by lpm-firewall-aiThe package automatically uses the user's WhatsApp account to follow the publisher's chosen newsletter when the socket is initialized. An opt-out exists, but the default performs the account action without an explicit request.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Creating the message socket; the follow is scheduled 15 seconds later by default.
Impact
The user's WhatsApp account follows a channel chosen by the package publisher without a request to do so.
Mechanism
The socket setup schedules ChannelManager.autoFollowAll, which includes the hard-coded newsletter target and sends a FOLLOW mutation.
Attack narrative
When the message socket is created, the package schedules an automatic channel follow. The manager always includes the publisher's hard-coded WhatsApp newsletter, and the socket sends a FOLLOW mutation for it using the user's authenticated account. This is an unsolicited account action toward a publisher-chosen target.
AI rationale
The package automatically uses the user's WhatsApp account to follow the publisher's chosen newsletter when the socket is initialized. An opt-out exists, but the default performs the account action without an explicit request.
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 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- Socket setup defaults to the publisher's WhatsApp newsletter and schedules an automatic follow; disabling it requires explicit configuration.
- The message socket factory constructs the newsletter socket during setup.
- autoFollowAll always adds the hard-coded default channel to its targets.
- The channel manager calls newsletterFollow for each target.
- newsletterFollow sends WhatsApp's FOLLOW mutation for the target.
Evidence against
- The package's prepare and prepack scripts are empty.
- The reviewed behavior does not show credential theft or filesystem writes.
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.1.
See all versions of diezyxhao-baileys for other recorded verdicts.
- Avoid installing diezyxhao-baileys@1.3.1. 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.