Which versions of cryptob are malicious?

The following PyPI versions of cryptob are flagged malicious: 1.6.0, 2.6.0, 2.6.2. Treat any of these as compromised.

How do I remediate cryptob if I installed it?

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

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

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

Malicious package

cryptobPyPI

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

MAL-2025-6488

Immediate action

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

pip uninstall cryptob

What this malware does

Importing starts an infostealer

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

Campaign: 2025-07-cryptoo

Reasons (based on the campaign):

obfuscation
infostealer
exfiltration-browser-data
exfiltration-generic
crypto-related
exfiltration-crypto

Malicious versions

3 flagged

1.6.02.6.02.6.2

Indicators of compromise (SHA-256)

daa37d9c03e4135ee4771a0803db1599f5dcefde3e2e97bf8aeaf29887e958ff

b3d2efbd11d3b9495b523b15a2dced4a56a33732c7519c48fe598bda080fece4

d0ee1f01fb1d9fe3ac1d88bec06c858d0c3e33f2531e7ca1afb30177f0b85e84

d9fe5e76f4529be2bfc93433e93313c9cf8bab61c9ad4f262eb7f80d759859e0

ce40fa50958b027c334c10e9918f5f2273ca48445e7aac8c205754e38e67b59f

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

Campaign

RLMA-2025-035792025-07-cryptooRLUA-2026-00236

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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