Which versions of @depup/nuxt are malicious?

The following npm versions of @depup/nuxt are flagged malicious: 4.5.0-depup.0. Treat any of these as compromised.

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

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

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

If @depup/nuxt 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/nuxt part of a known attack campaign?

Yes — @depup/nuxt is associated with the IN-MAL-2026-017131 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/nuxt 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/nuxt (version 4.5.0-depup.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @depup/nuxt across your stack and pipelines.

Malicious package

@depup/nuxtnpm

@depup/nuxt is a confirmed malicious npm package (MAL-2026-13625) that typosquats a legitimate package to trick installs (malicious version 4.5.0-depup.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @depup/nuxt (npm)

MAL-2026-13625

Immediate action

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

npm uninstall @depup/nuxt

What this malware does

This package presents itself as a routine Nuxt republish with dependency bumps, but ships two coordinated modifications that pull attacker-controlled code into the installer's Nuxt build environment. First, package.json injects a direct runtime dependency on "@dxup/nuxt": "^0.5.3" — a lookalike of the package's own @depup scope — which is not declared in the README or in changes.json among the advertised dep bumps (@nuxt/devtools, @unhead/vue, @vue/shared, devalue, nostics, rolldown-string, undici, unhead, unimport, vue) and does not exist in upstream [email protected]. Second, dist/index.(m)js is tampered to push "@dxup/nuxt" into options._modules when experimental.typescriptPlugin is enabled, so when a consumer uses this package as their nuxt and runs the Nuxt build or dev server, @dxup/nuxt is auto-loaded as a privileged Nuxt module and executes arbitrary code in the build/dev context. The scope name and undocumented injection are consistent with dependency-graph smuggling under cover of a familiar Nuxt republish.

Malicious versions

1 flagged

4.5.0-depup.0

Indicators of compromise (SHA-256)

b0811cc3f28ee89cf1ab9a44155c55f9f590f4692bad740986dc00b67dbb8bb3

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/nuxt (version 4.5.0-depup.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @depup/nuxt across your stack and pipelines.
If you installed it — respond
@depup/nuxt is a typosquat — you almost certainly intended a legitimately-named package. Remove @depup/nuxt, 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/nuxt 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/nuxt 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/nuxt on npm has been identified as a malicious package (version 4.5.0-depup.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017131

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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