Which versions of crto0 are malicious?

The following PyPI versions of crto0 are flagged malicious: 1.0.7. Treat any of these as compromised.

How do I remediate crto0 if I installed it?

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

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

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

Malicious package

crto0PyPI

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

MAL-2025-6487

Immediate action

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

pip uninstall crto0

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

1 flagged

1.0.7

Indicators of compromise (SHA-256)

81a159e6209737c1bd1bcb69811610d6559eac3635599081c59ef32545161882

cd86874b6b3f455ff48d6b57466c44fea2da4faf01f891aaa39ea0f0b36fcd8d

8bdcf6d997fa4676ca2da647171f21e944f9b7d0f34010e6ea8da42364a2d03d

3ff2781240b6e360a4a3a4e753225548b5f9f68e456d0b5d188aa1d1f587b2ef

272b807416a374c3cc65dda002b4025d26edcd6ec32ac0a27ce5b3054a4fb6f3

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

Campaign

RLMA-2025-035782025-07-crptRLUA-2026-00231

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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