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

nitro-kutunpm

Advisory published Updated

nitro-kutu is a confirmed malicious npm package (MAL-2025-191132) that steals credentials and exfiltrates sensitive data (malicious version 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nitro-kutu (npm)

MAL-2025-191132
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall nitro-kutu

What this malware does

The package nitro-kutu was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged
0.1.1

Indicators of compromise (SHA-256)

e49eaa55b0b2cddde2728a2d6cfcc512771af0fa1cf78903a09e11d7b564d972
b545008b56323a025035074860f80a8414ec451f58454478528ac44cb80fcbcd
2c730e64b459919c937231de7e767a99ceca04f35011b70d3d95c5616092dead

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for nitro-kutu (version 0.1.1).

  2. If you installed it — respond

    nitro-kutu 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 nitro-kutu 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. nitro-kutu on npm has been identified as a malicious package (version 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hfpq-3gcm-4mmc

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks nitro-kutu-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

nitro-kutu (npm) malicious package — MAL-2025-191132 | O3 Security