Which versions of iam-scripts are malicious?

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

How do I remediate iam-scripts if I installed it?

Remove iam-scripts 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.

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

If iam-scripts 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 iam-scripts part of a known attack campaign?

Yes — iam-scripts is associated with the RLMA-2026-05110, RLUA-2026-06277 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 iam-scripts across my projects, lockfiles, and CI pipelines?

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

Malicious package

iam-scriptsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

iam-scripts is a confirmed malicious npm package (MAL-2026-7296) 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 iam-scripts (npm)

MAL-2026-7296

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall iam-scripts

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

ac273713b82f3bc21ad74272e49e62305b747c806e27e15eae01a1be6736ea73

50f34fedf328d849897f03b8868e6c457cc1a449b92f037383c48f5d5cac7afa

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for iam-scripts (version 99.9.9).
If you installed it — respond
Remove iam-scripts 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.
Did it already run?
If iam-scripts 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. iam-scripts 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-05110RLUA-2026-06277

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks iam-scripts-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database