Which versions of bitforger are malicious?

The following PyPI versions of bitforger are flagged malicious: 0, 0.0, 0.1.0, 1.1.2, 1.1.3, 2.3.4, 2.3.5, 5.1, 5.1.4, 6.1.2, 8.1. Treat any of these as compromised.

How do I remediate bitforger if I installed it?

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

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

Yes — bitforger is associated with the RLMA-2024-10981, 2024-09-bitbit, RLUA-2026-00149 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 bitforger 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 bitforger (11 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bitforger across your stack and pipelines.

Malicious package

bitforgerPyPI

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

MAL-2024-11536

Immediate action

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

pip uninstall bitforger

What this malware does

When running the module, this package attempts - depending on the version - to exfiltrate user files, a screenshot, or crypto wallets data (8.1.4).

Later continued under different package names.

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

Campaign: 2024-09-bitbit

Reasons (based on the campaign):

files-exfiltration
crypto-related

Malicious versions

11 flagged

00.00.1.01.1.21.1.32.3.42.3.55.15.1.46.1.28.1

Indicators of compromise (SHA-256)

87a11094f7b45e601e1a3832288695a1c8974868bffef13c2dedb55f33f74e16

8b428db04dbf710c24a731141654e1114f3d8d2ac8b2017b1bf56d2a7da5ae1f

9dff60a2be2c253f919aae6a6724cd140df2a3ca9bdcca9e637ea74bc987ac0f

27e4076848e0ef04dd12dd6a9c3a503b141bcf249313b814f5365b52a750057a

f97ede4616ee9fd0bf4ab4bba9dd44920e5c394c6591e1bfffd6ee73cf95a9e9

50f6baf1663a03e7fc7fe94b90e7c0f526441c9ff365100d3717b597739315ad

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

Campaign

RLMA-2024-109812024-09-bitbitRLUA-2026-00149

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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