Which versions of eth-account-api are malicious?

The following PyPI versions of eth-account-api are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.1.0, 1.0.0. Treat any of these as compromised.

How do I remediate eth-account-api if I installed it?

Remove eth-account-api from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed eth-account-api — how do I know if it already compromised me?

If eth-account-api was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is eth-account-api part of a known attack campaign?

Yes — eth-account-api is associated with the RLMA-2024-08195 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 eth-account-api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for eth-account-api (6 malicious versions).

Malicious package

eth-account-apiPyPI

eth-account-api is a confirmed malicious PyPI package (MAL-2024-9973) that executes malicious code on install (malicious versions 0.0.1, 0.0.2, 0.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eth-account-api (PyPI)

MAL-2024-9973

Immediate action

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

pip uninstall eth-account-api

Malicious versions

6 flagged

0.0.10.0.20.0.30.0.40.1.01.0.0

Indicators of compromise (SHA-256)

d735483a355c66b896ac066389700314a0bd3df3fe471727a823558eba35afd1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for eth-account-api (6 malicious versions).
If you installed it — respond
Remove eth-account-api from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If eth-account-api was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. eth-account-api on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.1.0, 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-08195

Credits

ReversingLabs · finder

Detect & block this

O3 blocks eth-account-api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database