Which versions of crypto-regex-checker are malicious?

The following PyPI versions of crypto-regex-checker are flagged malicious: 1.6.7, 1.6.8, 1.6.9, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5. Treat any of these as compromised.

How do I remediate crypto-regex-checker if I installed it?

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

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

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

Malicious package

crypto-regex-checkerPyPI

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

MAL-2024-11565

Immediate action

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

pip uninstall crypto-regex-checker

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

8 flagged

1.6.71.6.81.6.91.7.11.7.21.7.31.7.41.7.5

Indicators of compromise (SHA-256)

84667c3f4be75cd2806fbf4e66a14a306eb6cefa9d0c3d779ba6253de1c8c962

127ee4017c49094a53dbfde80a942032bdde632010f2124401910c0cff1d18e1

a849790638e062a67e51026ebcd7d23b06a5cb901a1b74ce74bcf09762511538

5c45daa914d609add30751587cc1a29bc16ab03d1b219dd66963d586bf1f6743

8b49764328c2b17f9c923880d94d095c52874734831fc0066d12a14bc442dc46

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

Campaign

RLMA-2024-110122024-10-fake-usreagentRLUA-2026-00234

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks crypto-regex-checker-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