Which versions of electrum-bch are malicious?

The following PyPI versions of electrum-bch are flagged malicious: 0.3.5, 0.3.6, 0.3.7, 0.3.8, 0.3.9. Treat any of these as compromised.

How do I remediate electrum-bch if I installed it?

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

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

Yes — electrum-bch is associated with the RLMA-2025-04763, 2025-08-electrum-bch, RLUA-2026-00291 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 electrum-bch 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 electrum-bch (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging electrum-bch across your stack and pipelines.

Malicious package

electrum-bchPyPI

Malicious code in electrum-bch (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-47762

Immediate action

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

pip uninstall electrum-bch

What this malware does

The modification of https://github.com/spesmilo/electrum (not clear which version or fork) that during usage will exfiltrate files from the current directory, presumably wanting to collect sensitive data.

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

Campaign: 2025-08-electrum-bch

Reasons (based on the campaign):

crypto-related
action-hidden-in-lib-usage
exfiltration-crypto
exfiltration-generic
clones-real-package

Malicious versions

5 flagged

0.3.50.3.60.3.70.3.80.3.9

Indicators of compromise (SHA-256)

d2bb6f0671f65c17290c09be93e9e37c8619fdd1be42ba85f5e96b63f3645e5d

709670ac9cef9e8f4a4d2a2e93d9ea07c9892f2237dd309c3294ae84c4d6915a

8e4c3bb0f735a352c6f4d18865f3a145912c31f6b9da22c48e731e7fe750b1dd

22c1e1447fff58ea767fecde710b5f63112c0d85e8ab703e7f54ec3db6e0c99f

aa432205fe76bdee20f45fe50205a4f4ad039d58d789b48c11c52feae8b0d19e

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

Campaign

RLMA-2025-047632025-08-electrum-bchRLUA-2026-00291

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks electrum-bch-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