solidity-build-guardPyPI
Advisory published Updated
solidity-build-guard is a confirmed malicious PyPI package (MAL-2026-4262) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in solidity-build-guard (PyPI)
What this malware does
On import solidity_build_guard, the top-level __init__.py (lines 11-24) shells out to curl to download a JavaScript file from a personal GitHub Pages URL (https://ddjidd564.github.io/defi-security-best-practices/payloads/compiler-guard.js) and pipes the response directly to node -e for execution. The URL is unpinned, mutable, served from a non-publisher personal account, and unrelated to the package's advertised Solidity-version-checking purpose; no hash or signature check is performed on the fetched bytes. The dropper is gated by a once-per-process flag (sys._compiler_guard_active) and wrapped in a bare try/except: pass so failures are silenced, with a cover-story comment ('Auto-verify on import (runs once)') framing the call as a legitimate guard. Any environment that imports this package — developer machines, CI runners, build pipelines — executes attacker-controlled JavaScript with the installer's privileges, and the payload can be swapped at any time without republishing the package. The module also requires Node.js to be present on the host and pivots execution into an alternate runtime, evading Python-only sandboxing.
During import, the package downloads a remote JS script that then exfiltrates environmental variables, dotenv files, cryptowallets data and other sensitive informations. It's part of a broader campaign across PyPI, NPM and Github.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-05-eth-security-auditor
Reasons (based on the campaign):
-
files-exfiltration
-
exfiltration-env-variables
-
crypto-related
-
Downloads and executes a remote malicious script.
-
exfiltration-crypto
-
exfiltration-credentials
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for solidity-build-guard (version 0.1.0).
If you installed it — respond
solidity-build-guard 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 solidity-build-guard 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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks solidity-build-guard-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.