Malicious Code Injection in xaver-buburayam60-breki: A Threat to npm Packages
Summary
MAL-2025-76287: Malicious code in xaver-buburayam60-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 xaver-buburayam60-breki is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to manipulate package.json files, which can lead to significant security risks for developers and users alike.
Vulnerability Detail
The vulnerability in xaver-buburayam60-breki originates from its association with a malicious campaign that floods the npm registry with derivative packages. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional exposure of sensitive information and the potential for further exploitation by malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xaver-buburayam60-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 prevent the installation of this malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that your package-lock.json file does not include xaver-buburayam60-breki. You can also use tools like Vulert to monitor for vulnerabilities in your project without requiring access to the code or installation.
Conclusion
The xaver-buburayam60-breki package poses a significant security risk due to its malicious code designed to manipulate package.json files and pollute the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for xaver-buburayam60-breki →
FAQ
xaver-buburayam60-breki is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the exposure of sensitive information, pollution of the npm registry, and potential exploitation by malicious actors.
You should uninstall the package immediately using the command npm uninstall xaver-buburayam60-breki and review your dependencies for any other potentially malicious packages.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
