Which versions of ethrpc-accounts are malicious?

The following PyPI versions of ethrpc-accounts are flagged malicious: 0.9.1, 0.9.2. Treat any of these as compromised.

How do I remediate ethrpc-accounts if I installed it?

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

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

Yes — ethrpc-accounts is associated with the 2026-02-old-ethrpc-keys 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 ethrpc-accounts 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 ethrpc-accounts (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ethrpc-accounts across your stack and pipelines.

Malicious package

ethrpc-accountsPyPI

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

MAL-2026-948

Immediate action

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

pip uninstall ethrpc-accounts

What this malware does

This package is a clone of legitimate eth-accounts. The malicious code is hidden in the dependency, ethrpc-keys, which exfiltrates private keys.

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

Campaign: 2026-02-old-ethrpc-keys

Reasons (based on the campaign):

clones-real-package
exfiltration-crypto
crypto-related
action-hidden-in-lib-usage
The malicious code is intentionally included in a dependency of the package

Malicious versions

2 flagged

0.9.10.9.2

Indicators of compromise (SHA-256)

6372ce82342ae30022a83501fc348d1c63ec3cb27b19dba0678430efdfeeb077

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

Campaign

2026-02-old-ethrpc-keys

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks ethrpc-accounts-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