MAL-2026-13622 Malicious code in @depup/astro (npm)
Malicious package
Published
MAL-2026-13622 is a malicious package: @depup/astro (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-13622/ (Markdown: https://insights.sbomify.com/MAL-2026-13622/index.md)
- Package
- @depup/astro
- Registry
- npm
What is MAL-2026-13622?
MAL-2026-13622 is a malicious package in @depup/astro, published on 7 Aug 2026.
Official description
This package is published under the @depup scope but sets author to 'withastro' and repository to github.com/withastro/astro, framing itself as a routine dependency-bump of the upstream astro framework. Its package.json systematically replaces well-known astro dependencies with same-shape lookalike names controlled by different maintainers, including picocolors→piccolore (^0.1.3), debug→obug (^2.1.4), and @astrojs/markdown-remark→@astrojs/markdown-satteri (0.3.5), alongside other atypical names such as tinyclip, am-i-vibing, and fontace. The shipped source has been mass-rewritten to import from the lookalikes (e.g.,
import colors from "piccolore" in place of picocolors), so a normal npm install and subsequent build resolves and executes code from those lookalike packages rather than the genuine upstream dependencies. The advertised version numbers (astro 7.2.0, vite 8, esbuild 0.28, zod 4) do not correspond to real upstream releases, and README keywords like 'security', 'latest', and 'patched' are used to normalize the substitutions as a maintenance update.What should I do about MAL-2026-13622?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.