Which versions of enumerate-iam are malicious?

Every published version of enumerate-iam on PyPI is considered malicious. Remove the package entirely.

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

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

If enumerate-iam 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.

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

Search your lockfiles and build artifacts for enumerate-iam (all published versions).

Malicious package

enumerate-iamPyPI

enumerate-iam is a confirmed malicious PyPI package (MAL-2023-8360) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in enumerate-iam (PyPI)

MAL-2023-8360

Immediate action

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

pip uninstall enumerate-iam

What this malware does

Malicious Typosquatting packages campaign targeting developers, steals cloud service credentials

Attack targeted at users of Alibaba, AWS and Telegram via malicious packages published to PyPI.

The malicious code was hidden in strategicly chosen functions and would only trigger when these functions were called. The malicious code does not automatically run on install or import, helping the packages evade detection.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

cc5e304091eeb9848bd177dfd300a7df7778e3913b42af19741f6cddec4be752

bfefcae6c29da10e63d630fc7e012995d730cc5c0af3a8144dc517f26382a3bd

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for enumerate-iam (all published versions).
If you installed it — respond
enumerate-iam 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 enumerate-iam 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. enumerate-iam on PyPI has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

Checkmarx · finder
Phylum · finder

Detect & block this

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