Which versions of crpt1 are malicious?

The following PyPI versions of crpt1 are flagged malicious: 1.0.0, 1.0.2, 1.7.0, 1.8.0, 1.9.0. Treat any of these as compromised.

How do I remediate crpt1 if I installed it?

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

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

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

Malicious package

crpt1PyPI

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

MAL-2025-6486

Immediate action

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

pip uninstall crpt1

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

5 flagged

1.0.01.0.21.7.01.8.01.9.0

Indicators of compromise (SHA-256)

35c2145caeebd6f9d05b2b9033a7525da0d0e9612446d531776af57cb1f218b0

b251e28b270d336f209287366d71640c5107ac2893d52abb7139473372f1b1eb

32fcd21a633d14f2794d9038f21c5ba7ecb5178bdb7205e6b0a90e4fc87486b2

fee5503cd4e99d0233d05731728e528dd6a9854231b400f539378c044bd04ec0

f251702634206afd0e27987ce00fbb2cc4dbb5dd21212089e4204c62927996f8

11c352bada459f78e51987727b9cc5ce6c52e9e38a6c2f7acb4cdbe11705b4b6

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

Campaign

RLMA-2025-035772025-07-crptRLUA-2026-00230

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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