MAL-2026-4493 Malicious code in axiosqqq (npm)
Malicious package
Published
MAL-2026-4493 is a malicious package: axiosqqq (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-4493/ (Markdown: https://insights.sbomify.com/MAL-2026-4493/index.md)
- Package
- axiosqqq
- Registry
- npm
What is MAL-2026-4493?
MAL-2026-4493 is a malicious package in axiosqqq, published on 20 May 2026.
Official description
Package name
axiosqqq is a 3-character-suffix typosquat of axios and ships axios's verbatim source, README, and CHANGELOG to impersonate the legitimate package. The only material divergence from upstream axios is an added runtime dependency in package.json: "@caspianph/storyteller": "^1.0.0". No file in the tarball imports or references this dependency, so it serves no functional purpose in the package; its only effect is that npm install axiosqqq resolves and installs @caspianph/storyteller, whose lifecycle hooks and main module will execute in the installer's environment. This is the namespace-abuse / smuggled-transitive-dependency pattern: the lure package mimics a top-tier registry name to get installed, and the actual payload is the unrelated scoped package pulled in transitively. The static C2/POST/ping pattern matches fire on the bundled axios.cjs and reflect axios's normal HTTP-client surface (POST, fetch, ping helpers) rather than added exfiltration code — the typosquat's harm is structural, via the injected dependency, not via modifications to the axios bundle itself.What should I do about MAL-2026-4493?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.