Which versions of eth-agent are malicious?

The following PyPI versions of eth-agent are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate eth-agent if I installed it?

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

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

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

Malicious package

eth-agentPyPI

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

MAL-2026-10195

Immediate action

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

pip uninstall eth-agent

What this malware does

During import, the code downloads and executes a remote script. The script collects sensitive files, including cryptocurrency wallet private keys and seeds, SSH keys, dotenv files and uploads them to IPFS. After that, it communicates with C2 and awaits further commands to execute.

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

Campaign: 2026-07-metemask-sdk

Reasons (based on the campaign):

files-exfiltration
typosquatting
exfiltration-ssh-keys
crypto-related
Downloads and executes a remote malicious script.
exfiltration-crypto
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
uses:ipfs

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

0268950ea20e5566a61026409820d6a1d4ac4d462f475ae4589c72390042fec6

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

Campaign

2026-07-metemask-sdk

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks eth-agent-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