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

cti-ctf-challengesPyPI

Malicious code in cti-ctf-challenges (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191709
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall cti-ctf-challenges

What this malware does

If the method from the module is called, it attempts to download a malicious code (identified as msf payload) and save it locally. In the analysed version, the code starting the malicious code was commented out.

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

Campaign: 2025-07-web3dummycti

Reasons (based on the campaign):

  • The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

  • action-hidden-in-lib-usage

  • Downloads and executes a remote malicious script.

Malicious versions

3 flagged
0.1.00.1.10.1.2

Indicators of compromise (SHA-256)

1c8af945364e0fba34cda9b3380142e8b5488188ec068411ba89e84d63c1ecca
1cefe6c8a9ac6ede7c6ba497cf17011bf431812980749bb0068995ebba4039d9
c3e6812abe8c36025c79adab1c9156f7ebc995f407c4b3d0e6cc4fbd4a7e592f

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 cti-ctf-challenges (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cti-ctf-challenges across your stack and pipelines.

  2. If you installed it — respond

    cti-ctf-challenges 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 cti-ctf-challenges 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 cti-ctf-challenges 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. cti-ctf-challenges on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-07-web3dummycti

References

Credits

  • Kamil Mańkowski (kam193)

Detect & block this

O3 blocks cti-ctf-challenges-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

cti-ctf-challenges (PyPI) malicious package — MAL-2025-191709 | O3 Security