ecto-spirit-win-k4n8 (npm) · Malicious Code
Affects ecto-spirit-win-k4n8Source GCVE Database
Malicious package : remove ecto-spirit-win-k4n8 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-5691
What to do
Remove ecto-spirit-win-k4n8 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 |
|---|---|---|
| npmecto-spirit-win-k4n8 | 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 (8082c12f69dfbb45e83017fa0baf4f88f9500649dd443e80f2d7d4f858020814) The package ships a postinstall.js that imports child_process and references HTTP GET and hostname operations. Without traced-code corroboration of how these primitives are composed (e.g., whether GET fetches attacker-controlled content that is then executed, or whether hostname is exfiltrated to a remote endpoint), the pattern is consistent with both benign install diagnostics and an exfil/dropper shape. Manual review of postinstall.js is needed to confirm intent before publishing a verdict. ## Source: ghsa-malware (bca2b14b2c93ed832aa83a138c20bc53b4e053cf282ef5878333b1f50b803e55) 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.