Malicious code in diezyyasha-baileys (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-13443
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (1a8260f399be3238031864bd71945720155775a2de8e952a25225337257fd745) diezyyasha-baileys is a fork of the Baileys WhatsApp library that contains an obfuscated network destination in lib/Socket/messages-send.js. At lines 425 and 436 the code constructs a URL 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) which decodes to https://fiora.nixel.my.id/ — a hardcoded third-party host reconstructed from a char-code array rather than a plain string. This destination is embedded inside the message-sending code path of a WhatsApp session library, where the caller has already provided authenticated session credentials and where message content, contacts, and session identifiers are handled. The obfuscated-destination pattern (char-code reconstruction) inside a wallet/messaging-session code path is the exfiltration fingerprint: a first-party integration would use a plain, configurable URL, not a fromCharCode-reconstructed hardcoded host in a fork of an upstream library. ## Source: ghsa-malware (d60ca6b8b819cd26dec799a772e0dfcac120666bffee2f4d686291b2d4e5a3dc) 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
- 6 Aug 2026 14:23:02 UTC
- Source modified
- 7 Aug 2026 12:35:10 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.