metemask-sdkPyPI
metemask-sdk is a confirmed malicious PyPI package (MAL-2026-10197) that steals credentials and exfiltrates sensitive data (malicious versions 1.2.0, 1.2.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in metemask-sdk (PyPI)
What this malware does
metemask-sdk is a typosquat of the legitimate metamask-sdk package. On import, the top-level init.py performs an outbound HTTP fetch to https://gateway.pinata.cloud/ipfs/QmWMbuhKt24ssRKXCeiU94NoZGYcEunGnm6uvSKRwkejYP, passes the response body to exec(), and then invokes a main() function from the executed namespace. No integrity check (hash/signature) is performed on the fetched content, the fetch is wrapped in a bare try/except to suppress errors, and the IPFS CID resolves to attacker-controlled content that can change arbitrarily. The package's advertised public API (connect, sign_message, get_balance) is a non-functional stub that returns constants and random bytes, serving as a facade for the import-time dropper.
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 metemask-sdk (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging metemask-sdk across your stack and pipelines.
If you installed it — respond
metemask-sdk 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 metemask-sdk 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 metemask-sdk 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 metemask-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.