# MAL-2026-15527: Malicious code in aura-instrumentation (npm)


- **Type:** Malicious package
- **Package:** `aura-instrumentation` (npm)
- **Published:** 28 Aug 2026
- **Also known as:** GHSA-p4vf-c829-4m2m

## What is MAL-2026-15527?

MAL-2026-15527 is a malicious package in aura-instrumentation, published on 28 Aug 2026. 

### Official description

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.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

## What should I do about MAL-2026-15527?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-15527 is a malicious package: aura-instrumentation (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-15527/ (Markdown: https://insights.sbomify.com/MAL-2026-15527/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-15527

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-15527/
Summaries are generated and may contain mistakes; the official description above is the record.