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

generate-iam-tokennpm

Advisory published Updated

generate-iam-token is a confirmed malicious npm package (MAL-2026-7291) that executes malicious code on install (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in generate-iam-token (npm)

MAL-2026-7291
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall generate-iam-token

Malicious versions

1 flagged
99.9.9

Indicators of compromise (SHA-256)

7912053f908c1e9ae36b3e0d7fb00116c4b36505d9e60994ff4645dd399a2943
3f72f79d8f7644e1cc1d3d6dfef5f387d48b08f914e6647f19103ba551ad8628

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for generate-iam-token (version 99.9.9).

  2. If you installed it — respond

    Remove generate-iam-token from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

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

Campaign

RLMA-2026-05100RLUA-2026-06253

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks generate-iam-token-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

generate-iam-token (npm) malicious package — MAL-2026-7291 | O3 Security