Critical Security Breach in @pergel/nuxt: Malicious Code Detected

@pergel/nuxt Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191288: Malicious code in @pergel/nuxt (npm). Affects @pergel/nuxt versions 0.25.5. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @pergel/nuxt package is a Node.js library designed for building applications with the Nuxt.js framework. It provides essential functionalities for server-side rendering and static site generation. However, this package has been compromised, making it vulnerable to a severe security threat that can lead to unauthorized access to sensitive user data.

Vulnerability Detail

The vulnerability originates from the Sha1-Hulud: The Second Coming NPM worm, which has infected the @pergel/nuxt package. This malicious code is capable of stealing tokens and credentials from users, subsequently publishing this sensitive information to GitHub. Furthermore, the worm can propagate itself to other NPM packages owned by the user and establish persistence through a GitHub action. In extreme cases, it may even destroy the user's home directory, leading to significant data loss.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @pergel/nuxt

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can remove the @pergel/nuxt package from your project until a secure version is released. You can do this by executing the command: npm uninstall @pergel/nuxt. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The @pergel/nuxt package has been compromised by a malicious worm that poses serious security risks to users. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your applications.

See every vulnerability recorded for @pergel/nuxt →

Share this vulnerability

FAQ

The vulnerability involves malicious code that can steal sensitive information and propagate itself to other packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If you have installed @pergel/nuxt, it is recommended to uninstall the package immediately and monitor for updates or patches.

Yes, in severe cases, the worm can destroy the user's home directory, leading to significant data loss.

Regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation to mitigate risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @pergel/nuxt

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback