Which versions of generate-iam-token are malicious?

The following npm versions of generate-iam-token are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate generate-iam-token if I installed it?

generate-iam-token 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.

I already installed generate-iam-token — how do I know if it already compromised me?

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.

Is generate-iam-token part of a known attack campaign?

Yes — generate-iam-token is associated with the RLMA-2026-05100, RLUA-2026-06253 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find generate-iam-token across my projects, lockfiles, and CI pipelines?

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

Malicious package

generate-iam-tokennpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

generate-iam-token is a confirmed malicious npm package (MAL-2026-7291) that steals credentials and exfiltrates sensitive data (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

Credential / info stealer

Find it
Search your lockfiles and build artifacts for generate-iam-token (version 99.9.9).
If you installed it — respond
generate-iam-token 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.
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

github.com

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 credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database