Which versions of ethrpc are malicious?

The following PyPI versions of ethrpc are flagged malicious: 6.6.2, 6.6.3, 6.6.4. Treat any of these as compromised.

How do I remediate ethrpc if I installed it?

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

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

Yes — ethrpc 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 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 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ethrpc across your stack and pipelines.

Malicious package

ethrpcPyPI

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

MAL-2026-947

Immediate action

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

pip uninstall ethrpc

What this malware does

The malicious code is in the ethrpc-keys package, which is a clone of legitimate eth-keys, but contains a modification that silently exfiltrates the user's private key. Other packages in the campaign are also clones of legitimate packages, but the only modification is in pulling (directly or traversally) the malicious dependency. At the end, all packages in the campaign exfiltrate the private key.

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

3 flagged

6.6.26.6.36.6.4

Indicators of compromise (SHA-256)

b1eff108aebd0c94cd1b2c9dd2321060f61236e0dbf655c62f729169dcd5d5b3

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 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ethrpc across your stack and pipelines.
If you installed it — respond
ethrpc 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 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 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 on PyPI has been identified as a malicious package (versions 6.6.2, 6.6.3, 6.6.4 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-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