# MAL-2026-15528: Malicious code in axis-datagrid (npm)


- **Type:** Malicious package
- **Package:** `axis-datagrid` (npm)
- **Published:** 28 Aug 2026
- **Also known as:** GHSA-7f64-56gx-r4cm, GHSA-c6gq-r9w4-xg7j

## What is MAL-2026-15528?

MAL-2026-15528 is a malicious package in axis-datagrid, published on 28 Aug 2026. 

### Official description

package.json declares a dependency whose key equals the package's own name (`axis-datagrid`) and whose source is the bare HTTPS URL `https://repo.securityctrl.com/axis-datagrid` instead of a registry version range. On `npm install`, npm fetches whatever bytes that URL returns and installs them, running any lifecycle scripts they contain, with no version pin and no integrity check. The shipped index.js is an inert stub, so the manifest itself is the entire install-time payload: whoever controls repo.securityctrl.com controls code executed on the installer's machine. The self-referential dependency name (dependency-confusion shape) and an implausibly high version (45.0.0) for a package whose actual code is a placeholder are consistent with a package designed to win resolution against an internal name and pull code from an off-registry host.

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-15528?

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-15528 is a malicious package: axis-datagrid (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-15528/ (Markdown: https://insights.sbomify.com/MAL-2026-15528/index.md)
```

## Sources

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

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