Which versions of crypto-format-checking are malicious?

The following PyPI versions of crypto-format-checking are flagged malicious: 1.7.5, 1.7.6. Treat any of these as compromised.

How do I remediate crypto-format-checking if I installed it?

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

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

Yes — crypto-format-checking is associated with the RLMA-2024-11011, 2024-10-fake-usreagent, RLUA-2026-00233 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 crypto-format-checking 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 crypto-format-checking (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging crypto-format-checking across your stack and pipelines.

Malicious package

crypto-format-checkingPyPI

Malicious code in crypto-format-checking (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11564

Immediate action

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

pip uninstall crypto-format-checking

What this malware does

Inside the library there is a part running code hidden in the attached image, which then exfiltrate user-provided data, downloads and install next stage code, exfiltrate TXT files and finally installs infostealers - Lumma and a custom one. Arround L110

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

Campaign: 2024-10-fake-usreagent

Reasons (based on the campaign):

infostealer
files-exfiltration
clipboard-stealing
obfuscation
clones-real-package
action-hidden-in-lib-usage

Malicious versions

2 flagged

1.7.51.7.6

Indicators of compromise (SHA-256)

cb41607036269bb0a1c45971747774c6892126b1c3c80bcfa6a13040a4f95fd9

a92a8d306075287f4756fade7ae39f19fe83b1819c22fc93a14ac0138ec5c96d

a95b535a5d579db23cf10d4a9897278238afb3093600235b1f39ddf2cca74600

267f2f8f9f1deb4e22e65491feb5819438df12068bfc152174d481bdda85e7b0

0a24b017afcfad583f0d8ef4a8da1bd6234f8d224f4ac254f4789c6e9a28d419

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

Campaign

RLMA-2024-110112024-10-fake-usreagentRLUA-2026-00233

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks crypto-format-checking-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