NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

ecto-spirit-win-k4n8npm

Advisory published Updated

ecto-spirit-win-k4n8 is a confirmed malicious npm package (MAL-2026-5691) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ecto-spirit-win-k4n8 (npm)

MAL-2026-5691
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ecto-spirit-win-k4n8

What this malware does

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.

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.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

bca2b14b2c93ed832aa83a138c20bc53b4e053cf282ef5878333b1f50b803e55
8082c12f69dfbb45e83017fa0baf4f88f9500649dd443e80f2d7d4f858020814

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for ecto-spirit-win-k4n8 (version 1.0.0).

  2. If you installed it — respond

    ecto-spirit-win-k4n8 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If ecto-spirit-win-k4n8 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. ecto-spirit-win-k4n8 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-h2hh-hg37-42gqIN-MAL-2026-009482

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ecto-spirit-win-k4n8-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

ecto-spirit-win-k4n8 (npm) malicious package — MAL-2026-5691 | O3 Security