{"id":"MAL-2026-13625","revision":"bd83b05b2f534601a4f61d099e94442d","records":[{"revision":"bd83b05b2f534601a4f61d099e94442d","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-13625","aliases":[],"title":"Malicious code in @depup/nuxt (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (b0811cc3f28ee89cf1ab9a44155c55f9f590f4692bad740986dc00b67dbb8bb3)\nThis 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 nuxt@4.5.0. 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.\n","state":0,"publishedAt":"2026-08-07T17:25:02+00:00","modifiedAt":"2026-08-07T18:05:07.616177+00:00","affected":[{"ecosystem":"npm","name":"@depup/nuxt","ranges":[],"versions":["4.5.0-depup.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@depup/nuxt/v/4.5.0-depup.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-13625","license":"OSV · upstream source license applies","key":"osv:MAL-2026-13625","identifiers":["MAL-2026-13625"]},"retained":false,"historicalAffected":[]}],"coverage":[]}