alimama-minisite

Details

**Severity:** Critical

**Affected versions:** `= 45.0.0`

## Source: amazon-inspector (e3efd48d631afe828271bb266e4ddb8f2f6d0a8305294f56bde57d614c1cbfef)
package.json declares a self-named dependency alimama-minisite whose value is the off-registry URL https://repo.securityctrl.com/alimama-minisite instead of a semver range from the npm registry. On npm install, npm fetches whatever bytes that host returns and installs them, executing any lifecycle scripts contained in the fetched artifact. The dependency is unpinned and has no integrity check, so the returned content can change at any time. The dependency key equals the package's own name (dependency-confusion shape), and an implausibly high version (45.0.0) is set to win resolution against an internal package of the same name. The shipped index.js is an inert stub; the manifest line is the entire installer-side effect.

---

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

**References:**
- https://github.com/ossf/malicious-packages/blob/8278ab2bd67eee704962fa11801bbf9da85d4939/osv/malicious/npm/alimama-minisite/MAL-2026-15495.json
- https://www.npmjs.com/package/alimama-minisite/v/45.0.0
- https://github.com/advisories/GHSA-587j-f248-fmvr

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.