Critical Malicious Code Vulnerability in @lui-ui/lui-nuxt Package
Summary
MAL-2025-191243: Malicious code in @lui-ui/lui-nuxt (npm). Affects @lui-ui/lui-nuxt versions 0.1.1. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The @lui-ui/lui-nuxt package is a component library designed for use with Nuxt.js, providing UI components that enhance the development of web applications. However, it has been compromised, leading to significant security risks for users who have installed it. The vulnerability stems from a malicious payload that can steal sensitive information and propagate itself to other packages.
Vulnerability Detail
This vulnerability originates from a malicious NPM worm known as Sha1-Hulud: The Second Coming. It is capable of stealing tokens and credentials from the user's environment and publishing them to GitHub. The worm can also propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions. Additionally, it poses a risk of destroying the user's home directory, making it a severe threat to system integrity and data security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @lui-ui/lui-nuxtIf 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 measure, users should avoid using the @lui-ui/lui-nuxt package until it has been confirmed safe. Additionally, consider using alternative UI component libraries that do not have known vulnerabilities.
Conclusion
The @lui-ui/lui-nuxt package has been compromised, leading to a critical vulnerability that can severely impact users' systems. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to monitor their projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for @lui-ui/lui-nuxt →
FAQ
Immediately remove the package and rotate any secrets or keys stored on the affected machine.
The malicious code can propagate to other NPM packages owned by the user and establish persistence through GitHub actions.
It is advisable to review the security of other packages from the same author before using them, as they may also be compromised.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
