Malicious code in runtimekit (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-6477
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ffa393dec171ebd22b63776d7550006d3f9f60ad8726ce1153784080e9038acd) lib/index.cjs and lib/index.mjs (re-required from lib/readonly.cjs) contain a self-executing IIFE that decodes two opaque strings via a custom shuffle routine (`YWG`), recovers the identifier `constructor` from one of them, retrieves the Function constructor via property access, then builds and invokes nested Function-constructor calls — `Function('', Function('', decoded1))(decoded2)(7942)` — executing arbitrary decoded JavaScript at module load. Before the synthesis, the loader assigns `global.r = require` and `global.m = module`, deliberately smuggling Node's require and module bindings into the global scope so the dynamically constructed function (which does not inherit the module's closure) can reach them. A marker `global._V = "A6-Shadow-16"` is also set. The package advertises itself as a validation/runtime utility but ships an obfuscated self-injecting loader with no legitimate purpose for hiding code from Function constructors. Any consumer that does `require('runtimekit')` or `require('runtimekit/readonly')` runs the decoded payload in-process with full Node privileges. ## Source: ghsa-malware (fcff2793bd5cb43e32af39afe8d2667a9a0f8b4cf75d3d85e55d86349fe213cc) 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
- 25 Jun 2026 21:55:52 UTC
- Source modified
- 11 Aug 2026 12: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.