diezyxhao-baileys@1.2.1
DIEZYXHAO BAILEYS - Advanced WhatsApp Web API Library with Latest Protocol Support
AI Security Review
scanned 3h ago · by lpm-firewall-aiThe socket factory automatically follows a publisher-selected WhatsApp newsletter using the user's account, without a user request. The opt-out does not make that action requested, so this is malicious account-action behavior.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Creating a socket; the follow is scheduled 15 seconds later.
Impact
An unsolicited account action follows a channel selected by the package publisher.
Mechanism
The socket factory initializes a newsletter channel manager with a hard-coded publisher newsletter and calls autoFollowAll, which submits the follow using the authenticated WhatsApp socket. Users must opt out through configuration.
Attack narrative
When a client creates a socket, the package schedules an automatic follow of the publisher's hard-coded WhatsApp newsletter. The channel manager sends the follow through the authenticated socket. This account action occurs by default and can only be prevented with an opt-out setting.
AI rationale
The socket factory automatically follows a publisher-selected WhatsApp newsletter using the user's account, without a user request. The opt-out does not make that action requested, so this is malicious account-action behavior.
Evidence
lib/Socket/newsletter.jslib/Utils/channel-manager.jslib/Socket/messages-send.js
Network endpoints2
s.whatsapp.netWhatsApp newsletter service
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Socket creation schedules a newsletter follow after 15 seconds by default; the only opt-out is config.autoFollowChannels = false.
- The default target is the publisher's hard-coded WhatsApp newsletter, 120363411407993897@newsletter.
- The channel manager performs the follow through the socket's newsletterFollow method or a WhatsApp query.
- The package's socket construction path invokes the newsletter socket factory.
Evidence against
- The package is a WhatsApp Web API library, so WhatsApp network traffic is part of its stated purpose.
- The default follow can be disabled with config.autoFollowChannels = false.
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.2.1.
See all versions of diezyxhao-baileys for other recorded verdicts.
- Avoid installing diezyxhao-baileys@1.2.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.