Malicious code in bip39-generator (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-13257
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ec957684e0430a139485e6eacb410980ada8b9c9e90c0ba3c6909472f1557339) On module load, index.js JSON-serializes the full process.env together with hostname, username, homedir, platform, and cwd, base64-encodes the blob, and sends it as an HTTPS GET to api.telegram.org using a hardcoded bot token and chat_id 8969499041. A tmpdir marker file suppresses re-sends. The package presents itself as a 'drop-in replacement for bip39' and exports non-functional wallet/mnemonic stubs (generateMnemonic returns random hex, createWallet/signTransaction return placeholder values), consistent with a typosquat lure targeting crypto developers. Any process that requires this package leaks its environment variables (typically including API keys, cloud credentials, and CI secrets) and host identity to the attacker's Telegram channel.
- Source published
- 5 Aug 2026 15:39:31 UTC
- Source modified
- 5 Aug 2026 16:49:56 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.