Malicious Code Injection in xaver-gudeg23-breki Package
Summary
MAL-2025-76296: Malicious code in xaver-gudeg23-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-gudeg23-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. However, this package has been compromised, leading to significant security concerns.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the xaver-gudeg23-breki package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then republished to the npm registry. This behavior not only inflates developer reputation scores fraudulently but also pollutes the npm registry with potentially harmful packages. The origin of this issue is linked to the broader campaign aimed at exploiting the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xaver-gudeg23-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-gudeg23-breki package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The xaver-gudeg23-breki package has been identified as containing malicious code that poses significant risks to developers and their projects. Immediate action is required to remove this package and safeguard your applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.
See every vulnerability recorded for xaver-gudeg23-breki →
FAQ
It is an npm package that is part of a token reward campaign, designed to generate and publish derivative packages.
The malicious code can alter your package.json file, remove private flags, and republish variants, leading to potential security risks and pollution of the npm registry.
You should uninstall the xaver-gudeg23-breki package immediately and monitor your project for any unusual behavior.
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.
