native-runner (npm) · Malicious Code
Affects native-runnerSource GCVE Database
Malicious package : remove native-runner and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 16:22 UTC
Malicious package
Published to npm · OSV MAL-2026-17218
What to do
Remove native-runner from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmnative-runner | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package 'native-runner' contains malicious code that, upon import, silently waits for and executes a hidden binary named node_runtime_helper.exe from a Windows system-like directory. This behavior occurs as a side effect of requiring the package, without any explicit API call. The package depends on 'img-to-native', which places the malicious binary on the system. This drop-and-execute chain can lead to full system compromise, and removal of the package does not guarantee eradication of the malware.
References
- github.com/advisories/GHSA-jxw5-69p3-hpm4 (opens in a new tab)
- npmjs.com/package/native-runner/v/1.0.0 (opens in a new tab)
- npmjs.com/package/native-runner/v/1.0.1 (opens in a new tab)
- npmjs.com/package/native-runner/v/1.0.3 (opens in a new tab)
- npmjs.com/package/native-runner/v/1.0.2 (opens in a new tab)