Malicious code in manticore-log (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-14433
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (184c02a26613b94b15f0abe1ed108c7a2a7a061f795213dba4772876e6e0a015) The package's preinstall lifecycle script fires automatically on npm install and collects the installer's OS username, hostname, current working directory, and the enclosing project's package.json name/author/version (obtained by walking up parents of __dirname). The JSON payload is hex-encoded, split into 60-character chunks, and leaked as DNS labels via dns.lookup queries under the hardcoded subdomain da5u87oh92rc72pp1dngqfc6hp8gwshm6.o.jgl.red, with a fallback DNS query on error. The chunked hex-over-DNS transport is a covert-channel technique that evades many egress filters. Package metadata is minimal (placeholder main, empty author) and inconsistent with any legitimate logging library, matching a dependency-confusion reconnaissance beacon pattern.
- Source published
- 24 Aug 2026 16:39:49 UTC
- Source modified
- 24 Aug 2026 17:00:14 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.