@mikudeveloper/baileys
WhatsApp API Modification By Miku Developer
This report shows the evidence for @mikudeveloper/baileys@1.0.0. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
This package appears in our research on the malicious Baileys forks, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe default socket path includes a hidden delayed fetch of a maintainer-controlled channel list and an automatic follow loop against the user's WhatsApp session. That is unconsented account abuse, not ordinary newsletter helper APIs.
Decision evidence
public snapshot- Creating the default WhatsApp socket starts a hidden two-minute timer that downloads a remote JSON channel list from GitHub and tries to follow each ID on the user's session.
- Follow attempts swallow errors and wait 11 seconds between IDs, which hides the behavior from the host app.
- The newsletter layer is on the default makeWASocket import path, so ordinary socket use activates it.
- The GitHub file is maintainer-controlled and can change after publish, so the follow targets are not fixed in the package.
- preinstall only checks that Node.js is 20 or newer and then exits.
- The follow call uses undefined Types_1.QueryIds.FOLLOW, so the WhatsApp follow query may throw before it is sent.
- Scanner hits on protocol string tables, ffmpeg thumbnails, and a git libsignal dependency match a normal Baileys-style WhatsApp library.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L600Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L600Findings
Affected versions and remediation
This report applies to @mikudeveloper/baileys@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @mikudeveloper/baileys@1.0.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.