NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@depup/nuxtnpm

Advisory published Updated

@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
  1. Find it

    Search your lockfiles and build artifacts for @depup/nuxt (version 4.5.0-depup.0).

  2. 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.

  3. Did it already run?

    If @depup/nuxt was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

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.

Explore

@depup/nuxt (npm) malicious package — MAL-2026-13625 | O3 Security