Malicious Code Injection in nurul-kue3-breki Package
Summary
MAL-2025-74643: Malicious code in nurul-kue3-breki (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-kue3-breki 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 exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the nurul-kue3-breki package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which can pollute the npm registry and potentially compromise the integrity of applications relying on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation of these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nurul-kue3-brekiIf 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 avoid using the nurul-kue3-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file using tools like Vulert, which alerts you to open-source vulnerabilities in real-time.
Conclusion
The nurul-kue3-breki package poses a significant risk due to its malicious code injection, which can compromise the integrity of applications. It is essential to remove this package and monitor your dependencies for vulnerabilities to ensure the security of your projects.
See every vulnerability recorded for nurul-kue3-breki →
FAQ
The nurul-kue3-breki package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of applications that depend on this package.
You should uninstall the nurul-kue3-breki package immediately and check for alternative packages that are secure.
You can use tools like Vulert to monitor your package-lock.json file for vulnerabilities without needing to access the code or install additional software.
Yes, 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.
