Malicious code in alipclutch-baileys (npm)
Exact source revision recorded 29 Oct 2026 15:12:22 UTC. It does not establish the source's current position. Latest evidence.
osv · MAL-2026-12108
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (6bda065ae67b5aebf16879c88d3aa76bdea7775254fc5237ae10b1a67db67c3e) 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. ## Source: ghsa-malware (09e5b87da389cf9d1ea5964b0bd5f22a4ac0dab50847448dc1352158633f09f1) 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.
- Source published
- 5 Aug 2026 06:16:49 UTC
- Source modified
- 29 Oct 2026 14:30:39 UTC
- Observed here
- 29 Oct 2026 15:12:22 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.