axis-datagridnpm
axis-datagrid is a confirmed malicious npm package (MAL-2026-15528) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in axis-datagrid (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for axis-datagrid (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging axis-datagrid across your stack and pipelines.
If you installed it — respond
Remove axis-datagrid from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If axis-datagrid was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks axis-datagrid before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks axis-datagrid-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.