Malicious Code Injection in nurul-enting2-breki: A Threat to npm Packages
Summary
MAL-2025-74636: Malicious code in nurul-enting2-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
Background
The package 'nurul-enting2-breki' is part of a series of npm packages that have been linked to a token reward campaign by tea.xyz. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised due to the presence of malicious scripts that alter its metadata.
Vulnerability Detail
The vulnerability in 'nurul-enting2-breki' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nurul-enting2-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-enting2-breki' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'nurul-enting2-breki' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for nurul-enting2-breki →
FAQ
'nurul-enting2-breki' is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
Using this package can lead to security risks, including the potential for your application to be compromised through malicious code.
You should uninstall the package immediately and look for alternative solutions to avoid security risks.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
