eth-agentPyPI
eth-agent is a confirmed malicious PyPI package (MAL-2026-10195) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in eth-agent (PyPI)
What this malware does
The top-level eth_agent/init.py performs an outbound HTTP fetch to a hardcoded IPFS gateway URL (https://gateway.pinata.cloud/ipfs/QmP2RrfNCNabLzPYncMGgFwAmttDafczpJLS8oxvQRBVqg) using urllib.request.urlopen, passes the returned bytes to exec() in a new namespace, and then invokes a main() function from that namespace. The entire fetch-and-execute block is wrapped in a bare try/except: pass annotated with a Spanish comment marking the load as silent, so any error is suppressed and the payload load is hidden from the user during import. This fires on every import eth_agent, so simply importing the package after pip install eth-agent runs opaque, attacker-controlled Python code on the installer's machine. The IPFS content is not pinned by hash-verification in code, is served from a third-party gateway, and is unrelated to the package's stated Ethereum RPC helper purpose.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind 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
Campaign
References
Credits
- Amazon Inspector · finder
- 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.