Malicious Code Injection in nurul-menjes69-breki: A Threat to npm Ecosystem
Summary
MAL-2025-74651: Malicious code in nurul-menjes69-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-menjes69-breki' is part of a malicious campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages with random names, aiming to inflate developer reputation scores for token rewards. Its functionality poses a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nurul-menjes69-breki' originates from its malicious code 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 pollutes the npm registry and can compromise the security of applications relying on these packages. The malicious payload is part of a broader scheme to exploit the npm ecosystem for fraudulent gains.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nurul-menjes69-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 measure, you can avoid using the 'nurul-menjes69-breki' package and replace it with a trusted alternative. Regularly monitor your dependencies and consider using tools like Vulert to keep track of vulnerabilities in your project.
Conclusion
The 'nurul-menjes69-breki' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package data and inflate developer reputation scores. It is crucial to remove this package and monitor your dependencies to maintain application security.
See every vulnerability recorded for nurul-menjes69-breki →
FAQ
The impact includes potential exposure to malicious code that can compromise application integrity and security, leading to unauthorized access or data breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application against this vulnerability using the Vulert playground without any signup.
If immediate removal is not possible, ensure that your application is not using any features of the affected package and monitor for any unusual behavior.
Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities and provide alerts in real-time.
Using compromised packages can lead to ongoing security risks, including data breaches, loss of user trust, and potential legal ramifications.
