alipclutch-baileysnpm
Advisory published Updated
alipclutch-baileys is a confirmed malicious npm package (MAL-2026-12108) that steals credentials and exfiltrates sensitive data (malicious versions 8.6.58, 8.6.59, 8.6.60…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in alipclutch-baileys (npm)
What this malware does
This Baileys fork modifies the outgoing WhatsApp rich-media send path in lib/Socket/messages-send.js so that every image and video preview payload carries a hardcoded sourceUrl attribute pointing to https://fiora.nixel.my.id/. The URL is not present as a string literal — it is assembled at runtime from a decimal-ASCII array via String.fromCharCode(104,116,116,112,115,58,47,47,102,105,111,114,97,46,110,105,120,101,108,46,109,121,46,105,100,47), and the associated internal key prefix uses unicode-escaped characters (\u004E\u0049\u0058\u0045\u004C_LATEX_ / _HYPERLINK_ / _CITATION_) so the 'NIXEL'/'fiora' identifiers do not appear in plaintext anywhere else in the package. The advertised purpose of the library is to send WhatsApp messages on behalf of the caller; the caller does not opt into any attribution to fiora.nixel.my.id, and no configuration surface exposes this destination. The behavior is a covert attribution/traffic-attribution side-effect using the caller's WhatsApp session — no credential theft, environment scraping, remote code execution, filesystem persistence, or backdoor is present in this code path; recipients of the caller's messages who click the media preview would be directed to the author-controlled host. The obfuscation choices (charcode-assembled destination plus unicode-escaped brand token) are consistent with deliberate concealment of the destination from source review rather than incidental minification.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for alipclutch-baileys (29 malicious versions).
If you installed it — respond
alipclutch-baileys is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If alipclutch-baileys was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks alipclutch-baileys-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.