Malicious Code Injection in nana-bubur5-breki: A Threat to npm Packages
Summary
MAL-2025-74549: Malicious code in nana-bubur5-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 'nana-bubur5-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nana-bubur5-breki' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the security of applications that depend on this package, potentially allowing unauthorized access or execution of harmful code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nana-bubur5-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 'nana-bubur5-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 'nana-bubur5-breki' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and adopt best practices for package management to safeguard your applications.
See every vulnerability recorded for nana-bubur5-breki →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed the package, you should uninstall it immediately using 'npm uninstall nana-bubur5-breki' and check your project for any other affected packages.
While specific exploits have not been detailed, the malicious behavior of the package can lead to unauthorized access and execution of harmful scripts in dependent applications.
To prevent similar vulnerabilities, always use trusted packages, regularly update your dependencies, and utilize tools like Vulert to monitor for vulnerabilities in your software.
