Malicious Code Injection in xaver-gudeg14-breki: A Threat to npm Ecosystem
Summary
MAL-2025-76295: Malicious code in xaver-gudeg14-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-gudeg14-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, notorious for flooding the npm registry with malicious packages. Its primary functionality revolves around generating and publishing derivative packages, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in xaver-gudeg14-breki stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to pollution of the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which exploits npm's package publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xaver-gudeg14-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-gudeg14-breki package and look for alternative packages that provide similar functionality without the risk of malicious code. Additionally, you can use tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The xaver-gudeg14-breki package poses a significant risk due to its malicious code that alters package metadata and inflates developer reputation scores. It is crucial to remove this package from your project and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for xaver-gudeg14-breki →
FAQ
xaver-gudeg14-breki is an npm package associated with the tea.xyz token reward campaign, which has been found to contain malicious code.
The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and affecting your project's integrity.
You should uninstall the xaver-gudeg14-breki package immediately and check your project for any other potentially compromised packages.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time, alerting you to any issues.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
