@zdxnv/baileys@1.0.2
A WebSockets library for interacting with WhatsApp Web.
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource inspection confirms an automatic, publisher-directed change to authenticated account subscriptions after login. This is concrete account abuse, 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
Trigger
Importing and constructing the package's socket, followed by a successful connection.
Impact
The account follows publisher-selected newsletters without the user's request.
Mechanism
The routine fetches newsletter IDs from a fixed GitHub-hosted list and sends follow queries for valid IDs after login.
Attack narrative
When a socket is constructed, the newsletter module retrieves a list of newsletter IDs from a fixed GitHub URL. Once the WhatsApp connection opens, it schedules follow requests for each valid ID. This performs publisher-selected account actions without a user request.
AI rationale
Source inspection confirms an automatic, publisher-directed change to authenticated account subscriptions after login. This is concrete account abuse, so the package should be blocked.
Evidence
package.jsonlib/Socket/messages-send.jslib/Socket/username.jslib/Socket/newsletter.jslib/Types/Mex.js
Network endpoints2
raw.githubusercontent.comgraph.whatsapp.com
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package entrypoint loads the socket stack that reaches the newsletter module through the message socket and username socket.
- The newsletter module decodes a fixed GitHub URL and fetches its channel list during socket construction.
- After the WhatsApp connection opens, it schedules follow queries for every valid newsletter ID in that remote list.
- The follow query uses the newsletter-follow action, changing the authenticated account's subscriptions without a user request.
Evidence against
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
WildcardDependency
Oversized source lightweight scan
Source & flagged code
7 flaggedlib/WABinary/constants.jsView file
600patternName = google_api_key
severity = high
line = 600
High
High Secret
Package contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L600600patternName = google_api_key
severity = high
line = 600
High
Secret Pattern
Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L600lib/Utils/validate-connection.jsView file
107pull: false,
L108: devicePairingData: {
L109: buildHash: appVersionBuf,
...
L134: const { details, hmac, accountType } = proto.ADVSignedDeviceIdentityHMAC.decode(deviceIdentityNode.content);
L135: let hmacPrefix = Buffer.from([]);
L136: if (accountType !== undefined && accountType === proto.ADVEncryptionType.HOSTED) {
...
L158: ]);
L159: account.deviceSignature = Curve.sign(signedIdentityKey.private, deviceMsg);
L160: const identity = createSignalIdentity(lid, accountSignatureKey);
Findings
5 High4 Medium6 Low
HighHigh Secretlib/WABinary/constants.js
HighBase64 Obscured Urllib/Socket/newsletter.js
HighSemantic Analysis Limitedlib/Utils/business.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
MediumNetwork
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
MediumWildcard Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptolib/Utils/validate-connection.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @zdxnv/baileys@1.0.2.
See all versions of @zdxnv/baileys for other recorded verdicts.
- Avoid installing @zdxnv/baileys@1.0.2. 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.