@zanxiky/baileys
A WebSockets library for interacting with WhatsApp Web — iky fork of Baileys
This report shows the evidence for @zanxiky/baileys@1.1.0, the only known version.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package silently follows a hard-coded publisher newsletter after ordinary socket creation. This uses the user's WhatsApp account for an action the user did not request, which meets the account-action abuse rule.
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 normal message socket; the follow is scheduled 150 seconds later.
Impact
Uses the user's WhatsApp account to follow the publisher's chosen newsletter without a request to follow it.
Mechanism
The newsletter socket decodes a hard-coded newsletter ID and sends a FOLLOW mutation through WhatsApp's w:mex query.
Attack narrative
When the normal message socket is created, it constructs a username socket and then a newsletter socket. That socket schedules a request for 150 seconds later, decodes a hard-coded newsletter ID labeled “About Iky,” and sends a WhatsApp FOLLOW mutation. This performs an account action toward a publisher-selected target without the user requesting the follow.
AI rationale
The package silently follows a hard-coded publisher newsletter after ordinary socket creation. This uses the user's WhatsApp account for an action the user did not request, which meets the account-action abuse rule.
Evidence
lib/Socket/newsletter.jslib/Socket/username.jslib/Socket/messages-send.js
Network endpoints1
WhatsApp service (w:mex query)
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- Socket creation schedules a delayed follow request for a hard-coded newsletter labeled “About Iky.”
- The scheduled request decodes the pinned newsletter ID and sends a FOLLOW mutation to WhatsApp.
- The default message socket factory constructs the username socket, which constructs the newsletter socket and triggers the timer.
Evidence against
- The preinstall script only checks the Node.js major version and exits when it is below 20.
- The package describes itself as a WhatsApp Web library, so its WhatsApp protocol traffic otherwise fits its purpose.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
GitDependency
Source & flagged code
9 flaggedpackage.jsonView file
•scripts.preinstall = node ./engine-requirements.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkglib/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 · L600Findings
6 High5 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHigh Secretlib/WABinary/constants.js
HighSemantic Analysis Limitedlib/Utils/business.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighKnown Malware Source Fingerprint Signaturelib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
MediumNetwork
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
Affected versions and remediation
This report applies to @zanxiky/baileys@1.1.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @zanxiky/baileys@1.1.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.