Which versions of atlasctf-21-prod-22 are malicious?

The following PyPI versions of atlasctf-21-prod-22 are flagged malicious: 9999.0.8. Treat any of these as compromised.

How do I remediate atlasctf-21-prod-22 if I installed it?

atlasctf-21-prod-22 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 atlasctf-21-prod-22 — how do I know if it already compromised me?

If atlasctf-21-prod-22 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 atlasctf-21-prod-22 part of a known attack campaign?

Yes — atlasctf-21-prod-22 is associated with the RLMA-2025-02994, GENERIC-standard-pypi-install-pentest, RLUA-2026-00117 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 atlasctf-21-prod-22 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 atlasctf-21-prod-22 (version 9999.0.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging atlasctf-21-prod-22 across your stack and pipelines.

Malicious package

atlasctf-21-prod-22PyPI

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

MAL-2025-5097

Immediate action

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

pip uninstall atlasctf-21-prod-22

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

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

1 flagged

9999.0.8

Indicators of compromise (SHA-256)

947dd1c426987f9a3446c84defc8d526d89049e171f3d9ff15104e8aff078b8a

9463f11ecc416922c0a9f767bc65438ee2490dd70e0e146c79fad828c579fde6

bfee78d470601bcc72e8aa74eca9adb869998b939cff36a4a0dc6d12bfd8c297

58ee02dc44daba45609a099664bc01ca2cef013379e72dba44fca87d0e3d4fde

9d7bc82577d0c27fda2286eae7be20ab77fa4aec0bf6b50948eac8e31e4b6f93

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 atlasctf-21-prod-22 (version 9999.0.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging atlasctf-21-prod-22 across your stack and pipelines.
If you installed it — respond
atlasctf-21-prod-22 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 atlasctf-21-prod-22 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 atlasctf-21-prod-22 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-22 on PyPI has been identified as a malicious package (version 9999.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-02994GENERIC-standard-pypi-install-pentestRLUA-2026-00117

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks atlasctf-21-prod-22-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