Malicious Code Injection in xaver-bubursumsum99-breki Package
Summary
MAL-2025-76288: Malicious code in xaver-bubursumsum99-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 xaver-bubursumsum99-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the security of applications that depend on it.
Vulnerability Detail
The vulnerability in the xaver-bubursumsum99-breki package stems from its inclusion in a series of malicious packages that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers by potentially exposing sensitive information and undermining the reliability of the npm ecosystem. The malicious payload is designed to continuously republish variants, further exacerbating the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xaver-bubursumsum99-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 xaver-bubursumsum99-breki package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The xaver-bubursumsum99-breki package poses significant security risks due to its malicious code injection. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help ensure your applications remain secure.
See every vulnerability recorded for xaver-bubursumsum99-breki →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to the exposure of sensitive information and compromise the integrity of your application by introducing malicious code.
You should uninstall the package immediately and check your package-lock.json file for any references to it.
Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
