Malicious Code Injection in nurul-lapis72-ruro Package - npm Vulnerability
Summary
MAL-2025-106432: Malicious code in nurul-lapis72-ruro (npm). Affected versions are not published. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The nurul-lapis72-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry by creating and publishing derivative packages with altered metadata.
Vulnerability Detail
The vulnerability originates from the nurul-lapis72-ruro package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically modify and republish themselves with randomized names, thereby inflating developer reputation scores for token rewards. The malicious payload alters the package.json file by removing private flags and changing version numbers, leading to potential security risks and pollution of the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nurul-lapis72-ruroIf 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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include nurul-lapis72-ruro in its dependencies. You can also use the following command to uninstall the package if it is already installed: npm uninstall nurul-lapis72-ruro.
Conclusion
The nurul-lapis72-ruro package has been identified as a malicious entity within the npm ecosystem, capable of compromising application security through automated scripts. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for nurul-lapis72-ruro →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the pollution of the npm registry and may compromise the security of your application by introducing malicious code.
You should uninstall the nurul-lapis72-ruro package immediately and check for any other affected packages in your project.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
