aura-instrumentation

Details

**Severity:** Critical

**Affected versions:** `= 45.0.0`

## Source: amazon-inspector (14004b53bc245039cad1473ab4a95c2b2c8fcff2acc4b5f2c0f868da63e103bd)
package.json declares a self-named dependency 'aura-instrumentation' whose source is the bare URL https://repo.securityctrl.com/aura-instrumentation rather than a registry version range. On npm install, npm fetches whatever tarball that host returns, unpinned and with no integrity check, and runs any lifecycle scripts inside it. The shipped source is an inert stub and a placeholder README, so the manifest line is the entire published surface: install-time code execution on the installer's machine is delegated to whoever controls repo.securityctrl.com. The self-referential dependency name and an implausibly high version (45.0.0) for an otherwise empty package are consistent with a dependency-confusion lure aimed at winning resolution against an internal package of the same name.

---

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

**References:**
- https://github.com/ossf/malicious-packages/blob/d75ebb673b0185a99abe46e9e4a60aaa467fa7d8/osv/malicious/npm/aura-instrumentation/MAL-2026-15527.json
- https://www.npmjs.com/package/aura-instrumentation/v/45.0.0
- https://github.com/advisories/GHSA-xfhp-m3mp-45jf

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.