local-ip-helper (npm) · Malicious Code
Affects local-ip-helperSource GCVE Database
Malicious package : remove local-ip-helper and rotate any secrets on hosts that installed it.
Data as of 11 Jul 2026, 09:43 UTC
Malicious package
Published to npm · OSV MAL-2026-6282
What to do
Remove local-ip-helper 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 |
|---|---|---|
| npmlocal-ip-helper | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5741cea5f57c51246c2944fda4ecf601f191b482e5c6effa22b640f8701a00e8) index.js imports child_process and calls execSync with bash and zsh (lines 301 and 317). Without further context, it is unclear whether these invocations are part of a benign helper that resolves the local IP address by querying shell utilities, or whether they execute attacker-influenced content. No hardcoded external network destinations, credential reads, or install-time lifecycle hooks were observed. Recommend human review of the exact commands passed to bash/zsh and of how the package is invoked (library import vs. CLI) before allowing or blocking. ## Source: ghsa-malware (62edd1422ec623ef603b4c1d5bf898041000bb1a55470dc798519bdb4e0452b5) 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.