GitHub malicious-dependency incident touching protocol deps
A threat intelligence & recon factor in the v1.7.0 rubric. Measured per protocol on a e cadence.
Methodology how we score #
**What this measures** This episodic signal fires when a security advisory on GitHub (GHSA), npm, PyPI, or crates.io flags a malicious release or critical vulnerability in a package that is a direct or transitive dependency of the monitored protocol's deployment pipeline or frontend. The signal is generated by cross-referencing the protocol's dependency manifest (package.json, Cargo.toml, requirements.txt) against the GitHub Advisory Database and the OSV vulnerability feed. Category 11 context: malicious dependency injection (software supply-chain attack) represents an attacker-side vector that bypasses smart contract audits entirely by compromising the build or deployment toolchain.
**Why it matters** The XZ Utils supply-chain attack (March 2024) demonstrated that a two-year contribution pattern could precede a single malicious commit to a widely-used package. In DeFi, supply-chain attacks on npm packages used in frontend code or deployment scripts could enable unauthorized contract deployments or transaction manipulation. Team Finance ($14M, 2021) involved a migrate() function exploit — the attack vector was not a dependency compromise but the pattern of trusting third-party tooling without independent verification is the same. The Cetus Protocol case ($223M, 2025) involved a shared math library bug across four protocols — a supply-chain contagion pattern. GitHub Advisory monitoring provides automated tracking of the upstream dependency risk surface.
**Green / Yellow / Red** Green is the baseline when no current GHSA advisories or malicious-release flags exist for any package in the protocol's declared dependency manifest. Yellow fires when a moderate-severity advisory affects a transitive dependency (three or more hops removed from the protocol's direct imports) — real but distant risk. Red fires when a high or critical advisory — including a confirmed malicious-release flag — affects a direct dependency of the protocol's smart contract compilation pipeline or deployment scripts.
**Common gray cases** Gray applies when the protocol's dependency manifest is not publicly accessible or uses private package registries not covered by public advisory feeds, or when the protocol's smart contracts are compiled with no npm/PyPI dependencies (e.g., pure Foundry with pinned lib versions via git submodules).
**Notable historical examples** No cross-hacked incidents currently linked in database for this factor.
Measurement what to look for #
Determine whether a security advisory flags a malicious release in a dependency consumed by this protocol.