Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

atlasctf-21-prod-17PyPI

Malicious code in atlasctf-21-prod-17 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6454
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall atlasctf-21-prod-17

What this malware does

On installation or importing, the package attempts to exfiltrate some basic information, e.g. /etc/passwd

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2025-06-atlasctf

Reasons (based on the campaign):

  • exfiltration-generic

  • The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

  • The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged
99.99.9999.99.99.1

Indicators of compromise (SHA-256)

90c58f99ccc7b8615cb1e96a781e0cbdc33e6f4c5523e037bc832f761d6a4b48
3eae432e798f7c860716ba28721595f17299054d826f11f8496cceff8bb39536
0ae7f72936fae89a02869e537528e165a62538cbfdd9d4a441cdcdbd316783da
7d47e622aa06e0bc2ef5089db2a79198942ea66354c853faaa95232f5e0aa390
26b05eabdbda9a90eb2d718e9c667b7786f37d7917e8d8fab53f93bdd703dee5

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    atlasctf-21-prod-17 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.

  3. Did it already run?

    If atlasctf-21-prod-17 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.

  4. How O3 protects you

    O3 blocks atlasctf-21-prod-17 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. atlasctf-21-prod-17 on PyPI has been identified as a malicious package (versions 99.99.99, 99.99.99.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-035392025-06-atlasctfRLUA-2026-00112

References

Credits

  • Kamil Mańkowski (kam193)
  • ReversingLabs · finder

Detect & block this

O3 blocks atlasctf-21-prod-17-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

atlasctf-21-prod-17 (PyPI) malicious package — MAL-2025-6454 | O3 Security