raiden-baileys@2.1.0
Raiden-Baileys, baileys modifikasi by kaze
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 4d ago · by lpm-firewall-aiSource inspection confirms an automatic, publisher-selected change to the connected account: the socket construction path schedules a follow request for a fixed newsletter. This concrete unsolicited account action supports blocking publication.
Decision evidence
public snapshot- The package entry point exports makeWASocket, which constructs the registration, business, receive, and send socket layers.
- Constructing the send socket creates the newsletter socket, whose constructor schedules a follow request for a fixed newsletter ID after two minutes.
- The scheduled request uses the FOLLOW query ID and sends a WhatsApp service query; the code does not require a caller-selected newsletter or explicit consent.
- The request targets the WhatsApp service address ending in @s.whatsapp.net.
- The preinstall hook only checks the Node.js version; it does not perform the account action.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L30Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L30Findings
Affected versions and remediation
This report applies to raiden-baileys@2.1.0.
See all versions of raiden-baileys for other recorded verdicts.
- Avoid installing raiden-baileys@2.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.