eth-account-walletPyPI
eth-account-wallet is a confirmed malicious PyPI package (MAL-2026-13372) that steals credentials and exfiltrates sensitive data (malicious version 0.11.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in eth-account-wallet (PyPI)
What this malware does
eth-account-wallet 0.11.2 is a typosquat of the eth-account PyPI package. Its setup.py installs a custom install cmdclass (_PI) that, on pip install, spawns a background thread which harvests installer-side secrets: environment variables including PYPI_TOKEN, TWINE_PASSWORD, GITHUB_TOKEN, AWS_SECRET_ACCESS_KEY, NPM_TOKEN, PRIVATE_KEY, MNEMONIC, SEED_PHRASE; contents of ~/.ssh, ~/.aws/credentials, ~/.pypirc, ~/.npmrc, ~/.docker/config.json, pip and git global config; Chrome/Firefox profile artifacts (Cookies, Login Data, key4.db, logins.json); and wallet directories (.bitcoin,.ethereum,.solana,.metamask,.exodus,.electrum). Collected data is JSON-serialized and transmitted to two hardcoded attacker destinations: the Telegram Bot API (api.telegram.org/bot<token>/sendMessage with hardcoded bot token and chat id) and a Serveo reverse-tunnel C2 at https://40f955f39128bd79-178-249-214-24.serveousercontent.com/collect. The tarball ships no actual module code — the README advertises an eth_account_wallet.create_wallet() API that does not exist — confirming the package is a cover-story lure for the install-time stealer. Author metadata is placeholder (opensource-dev, github.com/dev/eth-account-wallet).
During installation, the package exfiltrates sensitive env variables, browser data, crypto wallets files, ssh keys and other configuration files.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-08-bip39-py
Reasons (based on the campaign):
-
crypto-related
-
The package overrides the install command in setup.py to execute malicious code during installation.
-
exfiltration-crypto
-
exfiltration-browser-data
-
exfiltration-env-variables
-
exfiltration-ssh-keys
-
exfiltration-credentials
-
uses-telegram-bot
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-account-wallet (version 0.11.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eth-account-wallet across your stack and pipelines.
If you installed it — respond
eth-account-wallet 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-account-wallet 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-account-wallet 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-account-wallet-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.