Malicious Code Injection in nurul-rangi7-breki: A Threat to npm Packages
Summary
MAL-2025-74660: Malicious code in nurul-rangi7-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-rangi7-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages. The vulnerability stems from the package's design, which includes scripts that manipulate package metadata, making it susceptible to exploitation.
Vulnerability Detail
The vulnerability in 'nurul-rangi7-breki' originates from its association with the tea.xyz token reward campaign. The package contains autopublish scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The ramifications include a loss of trust in the npm ecosystem and the risk of developers unknowingly using compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nurul-rangi7-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, consider removing the 'nurul-rangi7-breki' package from your project until a secure version is available. You can do this by executing the command: 'npm uninstall nurul-rangi7-breki'. Additionally, monitor your package-lock.json file for any changes that may indicate the presence of malicious packages.
Conclusion
The 'nurul-rangi7-breki' package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. It is crucial for developers to update or remove this package to maintain the integrity of their applications. Utilizing tools like Vulert can help in monitoring and managing such vulnerabilities effectively.
See every vulnerability recorded for nurul-rangi7-breki →
FAQ
The main issue is that it contains malicious code that modifies package metadata and republishes variants, which can compromise the integrity of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If you cannot update the package, consider removing it from your project and monitoring your dependencies for any signs of malicious activity.
While specific exploits have not been detailed, the malicious behavior of the package can lead to the proliferation of compromised packages in the npm registry.
Vulert uses your package-lock.json file to monitor for vulnerabilities in real-time, providing alerts and insights without requiring code access or installation.
