Which versions of crto5 are malicious?

The following PyPI versions of crto5 are flagged malicious: 0.1.0, 0.2.0, 0.5.0. Treat any of these as compromised.

How do I remediate crto5 if I installed it?

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

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

Yes — crto5 is associated with the 2025-07-crpt 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 crto5 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 crto5 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging crto5 across your stack and pipelines.

Malicious package

crto5PyPI

Malicious code in crto5 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191708

Immediate action

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

pip uninstall crto5

What this malware does

Importing the module starts downloading or decrypting, and then executing an executable being a wide recognized malware/Infostealer (Redline family)

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

Campaign: 2025-07-crpt

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.
Downloads and executes a remote malicious script.
exfiltration-crypto
malware

Malicious versions

3 flagged

0.1.00.2.00.5.0

Indicators of compromise (SHA-256)

c6d902cde8d930aa0b1ccdcc7985887501b8be6fc1fca036e02fcc9ab6ce1570

3a906f74f9672d68f42311985b67b1076e3b02caf14d8366b703d3331ff5897b

a84b5149a119f8b0ac61cf2d2956209ac6dfb3bd7147056fc8e60966cad06a9d

0e46bbba999d3b129c5d409d467b17d6212a4f4c0e2dfd85a856850d8ca6b9dc

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

Campaign

2025-07-crpt

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks crto5-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