framework-zero

GHSA-mpm2-wrc3-xqxf

Malicious code in framework-zero (npm)

Details

**Severity:** Critical

**Affected versions:** `= 45.0.0`

## Source: amazon-inspector (bfa0b9f3bb077648bf715ae13565ed44e67471548c98861bd5fb4d9472a3223b)
package.json line 11 declares a dependency whose source is the bare HTTPS URL https://repo.securityctrl.com/framework-zero instead of a registry version range. On npm install this URL is fetched and installed, running any lifecycle scripts in the returned tarball, with no version pin and no integrity check. The dependency key equals the package's own name (framework-zero), a dependency-confusion shape where the manifest itself is the delivery mechanism, and the pinned version 45.0.0 is implausibly high for the name — consistent with a resolution-winning squat against an internal package. The host repo.securityctrl.com is unrelated to any npm registry and can serve arbitrary content that changes at any time after publish.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/8278ab2bd67eee704962fa11801bbf9da85d4939/osv/malicious/npm/framework-zero/MAL-2026-15500.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/8278ab2bd67eee704962fa11801bbf9da85d4939/osv/malicious/npm/framework-zero/MAL-2026-15500.json
- https://www.npmjs.com/package/framework-zero/v/45.0.0
- https://github.com/advisories/GHSA-mpm2-wrc3-xqxf

Compromised versions (1)

= 45.0.0

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.