Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in bunnyhijack-test-0x00 (npm)

Exploitation and risk

Source status

CISA 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-14310

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (652b21307c316c7a3237991fdfb6dc4d43716997a91268f43fe9c9c65a3fd76e) package.json declares `"bin": { "node": "./shim.js" }`, which causes npm to place a `node` executable into `node_modules/.bin`. Since `node_modules/.bin` is prepended to PATH during npm lifecycle scripts, any sibling dependency whose install/postinstall invokes `node` (e.g., esbuild and similar packages with native build steps) will execute `shim.js` from this package instead of the real Node.js runtime. shim.js demonstrates the hijack by writing a marker file at /tmp/.bunnyhijack-test and printing a banner stating the node command was hijacked via esbuild's postinstall. The package's own description self-identifies as a self-triggering PATH-poisoning proof-of-concept, and the dependency on protoc-gen-grpc-web appears chosen to ensure a sibling lifecycle script invokes `node` during a normal `npm install`. The current shim payload is benign (marker file + console output), but the hijack primitive itself runs arbitrary code under the installer's user during install and would execute any future payload shipped in shim.js. ## Source: ghsa-malware (9a421e1ee8b9fbe1210f431f21d68420b064cc7b685f89189ec685e579951df7) 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
19 Aug 2026 15:20:03 UTC
Source modified
20 Aug 2026 03:30: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.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 21 Nov 06:40 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current