Malicious Code Injection in xaver-kue72-breki: A Threat to npm Packages
Summary
MAL-2025-76307: Malicious code in xaver-kue72-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-kue72-breki is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards related to the tea protocol, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in xaver-kue72-breki originates from its malicious intent to modify package.json files by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly incorporate these malicious packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xaver-kue72-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 xaver-kue72-breki package altogether. If it is already in use, consider removing it from your package.json and running npm install to clean up your dependencies. Additionally, you can use the following command to uninstall the package: npm uninstall xaver-kue72-breki.
Conclusion
The xaver-kue72-breki package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for xaver-kue72-breki →
FAQ
xaver-kue72-breki is an npm package linked to the tea.xyz token reward campaign, designed to manipulate the npm registry.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and functionality.
You should immediately uninstall the package and check your project for any unintended consequences caused by its presence.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
