Which versions of crypto-regex-gener are malicious?

The following PyPI versions of crypto-regex-gener are flagged malicious: 1.6.7. Treat any of these as compromised.

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

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

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

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

Malicious package

crypto-regex-generPyPI

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

MAL-2024-11566

Immediate action

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

pip uninstall crypto-regex-gener

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

1 flagged

1.6.7

Indicators of compromise (SHA-256)

c6c8d5ed2fccb8bce245bd40c0956009cdccbea530e9d12a21fb214f4be94b1e

7b87036e2d651df6844b1392a61121fd20a160b9703968a98f2bb77f44ce9145

3236b2ded0bd62e3958fa1c6257142248c46b75e64cdd0a90edd82ffba869335

29f4454f6af62abab79258aef4ae31846bdb1cd4698c8ba0d64be73de296565c

cba07e5db363d72988a90c8b21197d771a3af51b21eb1e03c0e90f929974c55e

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

Campaign

RLMA-2024-110132024-10-fake-usreagentRLUA-2026-00235

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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