gridster-coords

Details

**Severity:** Critical

**Affected versions:** `= 45.0.0`

## Source: amazon-inspector (245882b881fde3396fcb6e1e14f8b0014fc64cd1d02d27f101c8fd2a0b16c944)
package.json line 11 declares the dependency 'gridster-coords' as the bare HTTPS URL https://repo.securityctrl.com/gridster-coords instead of a registry version range. On npm install, npm fetches whatever bytes that URL serves, with no version pin and no integrity check, and executes any lifecycle scripts contained in the fetched tarball on the installer's machine. The dependency key equals the package's own name (dependency-confusion shape), the version '45.0.0' is implausibly high for a package of this name, and the host repo.securityctrl.com is unrelated to any npm registry or documented publisher. The shipped source is otherwise an inert stub, so the manifest line is the entire delivery mechanism.

---

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

**References:**
- https://github.com/ossf/malicious-packages/blob/d75ebb673b0185a99abe46e9e4a60aaa467fa7d8/osv/malicious/npm/gridster-coords/MAL-2026-15535.json
- https://www.npmjs.com/package/gridster-coords/v/45.0.0
- https://github.com/advisories/GHSA-m84w-xx28-rfc4

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.