Which versions of ethaddrlib are malicious?

The following PyPI versions of ethaddrlib are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate ethaddrlib if I installed it?

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

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

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

Malicious package

ethaddrlibPyPI

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

MAL-2025-191624

Immediate action

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

pip uninstall ethaddrlib

What this malware does

Package claims to validate mnemonic, a sensitive part of cryptocurrency system. The responsible functions, however, send given data to a remote service, and not even process the response. Thus, the only functionality is exfiltrating sensitive data.

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

Campaign: 2025-10-ethaddrlib

Reasons (based on the campaign):

crypto-related
exfiltration-crypto

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

f2dc712cb3c59a9bdf95640acf22e21961c4b8725ffe59ce53e32c83e0c0cfa5

29db029463728839443ccdcfafc6a525872204d70f6170d2fe58565bdc14d52c

9dc2b3682a4269e98a57e232f473846d94e0c74209349b54e1ccc5c669110c47

dbf64522b910926876184ba7f1e2d99bb4a02105cd5cb07dc19d13f5212cfcca

01f03343a23d735566781c342ad88e46cac4e048d1bbf4dd3f88eb42df345684

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

Campaign

RLMA-2025-055922025-10-ethaddrlibRLUA-2026-00298

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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