Which versions of coingenerator are malicious?

The following PyPI versions of coingenerator are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate coingenerator if I installed it?

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

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

Yes — coingenerator is associated with the RLMA-2025-01946, 2025-02-coinanalyze, RLUA-2026-00206 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 coingenerator 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 coingenerator (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging coingenerator across your stack and pipelines.

Malicious package

coingeneratorPyPI

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

MAL-2025-2948

Immediate action

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

pip uninstall coingenerator

What this malware does

Package contains obfuscated code that exfiltrate basic data and awaits for commands from the remote server to execute them. This is a malicious copy of legitimate https://pypi.org/project/coinanalyse/ package.

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

Campaign: 2025-02-coinanalyze

Reasons (based on the campaign):

backdoor
typosquatting
obfuscation
clones-real-package
crypto-related
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

7b4e9a220b4e470034bb0e08ca502bcdc263dddaf798d5eda4a7c1e5d359bcc2

5783a8540271b781c1260dfb3b3f3996f6682710c86906941fa127cb6f8cc688

78810d9638861bd92d3f96d7e29a552a41eb97b69b8deba84892cc7f458fb8c0

29b3f8437ee44a3f11b8b2cdc180c138e684ce3bbcd4d9004ec05efee5df0e10

fa011ed661f807a2f47cc311981a796b74d749df97b6fd56bf05d239f329e2a3

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

Campaign

RLMA-2025-019462025-02-coinanalyzeRLUA-2026-00206

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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