librastandardlib

GHSA-g4fg-jh8h-vf3p

Malicious code in librastandardlib (npm)

Details

**Severity:** Critical

**Affected versions:** `= 45.0.0`

## Source: amazon-inspector (519c28eb8d9df0a16d93e1b1c486f1ad4a9092a9bf958aed56f273cfe1fcfc14)
package.json at line 11 declares a dependency whose key equals the package's own name (librastandardlib) and whose value is an off-registry HTTPS URL (https://repo.securityctrl.com/librastandardlib) instead of a registry version range. On `npm install`, npm fetches whatever bytes that URL returns and installs them as the resolved dependency, running any lifecycle scripts inside with no version pin and no integrity check. The implausibly high version (45.0.0) and the self-referential dependency name are consistent with a dependency-confusion shape designed to win resolution against an internal package. The shipped index.js is an inert stub, so the manifest URL is the entire delivery mechanism — whoever controls repo.securityctrl.com controls code executed on the installer's machine at install time.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/d75ebb673b0185a99abe46e9e4a60aaa467fa7d8/osv/malicious/npm/librastandardlib/MAL-2026-15538.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/d75ebb673b0185a99abe46e9e4a60aaa467fa7d8/osv/malicious/npm/librastandardlib/MAL-2026-15538.json
- https://www.npmjs.com/package/librastandardlib/v/45.0.0
- https://github.com/advisories/GHSA-g4fg-jh8h-vf3p

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.