Which versions of @depup/astro are malicious?

The following npm versions of @depup/astro are flagged malicious: 7.1.3-depup.2, 7.2.0-depup.0. Treat any of these as compromised.

How do I remediate @depup/astro if I installed it?

@depup/astro is a typosquat — you almost certainly intended a legitimately-named package. Remove @depup/astro, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed @depup/astro — how do I know if it already compromised me?

If @depup/astro 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.

Is @depup/astro part of a known attack campaign?

Yes — @depup/astro is associated with the IN-MAL-2026-017129, IN-MAL-2026-017127 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @depup/astro across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @depup/astro (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @depup/astro across your stack and pipelines.

Malicious package

@depup/astronpm

@depup/astro is a confirmed malicious npm package (MAL-2026-13622) that typosquats a legitimate package to trick installs (malicious versions 7.1.3-depup.2, 7.2.0-depup.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @depup/astro (npm)

MAL-2026-13622

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @depup/astro

What this malware does

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.

Malicious versions

2 flagged

7.1.3-depup.27.2.0-depup.0

Indicators of compromise (SHA-256)

75daeef07606b8ba315a6ced4fd25925f79ab11b19032f8a51544c18457c6401

c7c6330072ae71974da0dd2e0e72a33334a35b78ec5679536d95b9f205032225

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @depup/astro (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @depup/astro across your stack and pipelines.
If you installed it — respond
@depup/astro is a typosquat — you almost certainly intended a legitimately-named package. Remove @depup/astro, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @depup/astro 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 @depup/astro 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

No. @depup/astro on npm has been identified as a malicious package (versions 7.1.3-depup.2, 7.2.0-depup.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017129IN-MAL-2026-017127

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @depup/astro-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database