@yshtxxproject/baileys
WhatsApp Baileys Library Modification to make it easier for developers to develop for anything
This report shows the evidence for @yshtxxproject/baileys@0.0.1. 1 of 2 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 3h ago · by lpm-firewall-aiThe package automatically uses the user's WhatsApp account to follow publisher-selected channels when a connection opens. The opt-out does not make this a requested action, so the package meets the malicious account-action rule.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The caller creates a socket and its WhatsApp connection opens, unless autoFollowChannels is overridden or disabled.
Impact
The user's account joins channels chosen by the package publisher without an explicit request.
Mechanism
The newsletter socket listens for the first connection-open event and sends a FOLLOW request for each default newsletter JID.
Attack narrative
Creating and connecting a socket triggers an automatic follow of three hard-coded WhatsApp newsletter targets. The follow requests use the user's WhatsApp connection and run by default; disabling them requires caller configuration. This is an unrequested account action toward targets chosen by the publisher.
AI rationale
The package automatically uses the user's WhatsApp account to follow publisher-selected channels when a connection opens. The opt-out does not make this a requested action, so the package meets the malicious account-action rule.
Evidence
lib/Defaults/index.jslib/Socket/newsletter.jslib/Socket/index.js
Network endpoints1
web.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 hard-codes three publisher-chosen WhatsApp newsletter JIDs as its default follow targets.
- The default connection config enables auto-follow for those JIDs unless the caller overrides or disables it.
- When the WhatsApp connection first opens, the socket sends a FOLLOW request for every configured target.
Evidence against
- The preinstall hook only checks the Node.js version and exits on versions below 20.
- The channel-follow behavior is documented in source and can be disabled, but it still runs by default without an explicit user request.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
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
5 High6 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHigh Secretlib/WABinary/constants.js
HighSemantic Analysis LimitedWAProto/index.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
MediumDynamic Requirelib/antiban.cjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Crypto
Affected versions and remediation
This report applies to @yshtxxproject/baileys@0.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @yshtxxproject/baileys@0.0.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.