Which versions of iamenumerat are malicious?

The following PyPI versions of iamenumerat are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate iamenumerat if I installed it?

iamenumerat 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 iamenumerat — how do I know if it already compromised me?

If iamenumerat was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is iamenumerat part of a known attack campaign?

Yes — iamenumerat is associated with the RLMA-2025-04774, 2025-08-aws-enumerate, RLUA-2026-00417 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 iamenumerat across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for iamenumerat (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging iamenumerat across your stack and pipelines.

Malicious package

iamenumeratPyPI

Malicious code in iamenumerat (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-47773

Immediate action

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

pip uninstall iamenumerat

What this malware does

Before creating the boto3 client, package exfiltrates user's credentials. Packages from the campaign are used as dependency in a GitHub project promising automating cloud enumeration

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-08-aws-enumerate

Reasons (based on the campaign):

exfiltration-generic
action-hidden-in-lib-usage
exfiltration-credentials

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

612f21ebe359fb8a67c6b80521d4779cbb417b3341e30e24041f21d5ccc02104

2f9d76dc8a847839279a8da624e52510b1f38acba6f507bdb5f5f713fe0ff9ae

469c5e69f2b343a59f385bcbf2cbc4ff0fa7a0b0790a341b9bd07f3990c2ca84

1c58bc13e244b74cdc426f2a931708cdc0d6e1ad187d2782f090704f42682104

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for iamenumerat (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging iamenumerat across your stack and pipelines.
If you installed it — respond
iamenumerat 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 iamenumerat was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks iamenumerat before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. iamenumerat on PyPI 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

RLMA-2025-047742025-08-aws-enumerateRLUA-2026-00417

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks iamenumerat-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