Which versions of aws-enumerate are malicious?

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

How do I remediate aws-enumerate if I installed it?

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

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

Yes — aws-enumerate is associated with the RLMA-2025-04112, 2025-08-aws-enumerate, RLUA-2026-00127 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 aws-enumerate 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 aws-enumerate (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 aws-enumerate across your stack and pipelines.

Malicious package

aws-enumeratePyPI

Malicious code in aws-enumerate (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-41621

Immediate action

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

pip uninstall aws-enumerate

What this malware does

Package for enumeratin IAM

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)

8838f069a4b7f5a3fc364958f96b6a2cc74bc8275dfcb3b051360fa921f7c5dd

519c24c53beaee164418c4e2dcbe78c3dbe6bd90a9e14355a5e0225516dc7d92

82e411db1ea78935340bd950942b13579b400264ddef042aa0b07d6952401c45

677340343d240fbdd107c6a62aa9435480d3e2fc7766e124256f910467ae31fd

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 aws-enumerate (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 aws-enumerate across your stack and pipelines.
If you installed it — respond
aws-enumerate 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 aws-enumerate 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 aws-enumerate 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. aws-enumerate 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-041122025-08-aws-enumerateRLUA-2026-00127

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks aws-enumerate-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