Malicious Code Injection in xaver-tempe65-breki Package
Summary
MAL-2025-76332: Malicious code in xaver-tempe65-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-tempe65-breki package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that inflate developer reputation scores. This package, like many others in this campaign, is designed to automatically generate and publish derivative packages, potentially compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the xaver-tempe65-breki package originates from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a significant increase in spam packages, making it difficult for developers to find legitimate packages and potentially introducing security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xaver-tempe65-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-tempe65-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can utilize tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without needing to sign up.
Conclusion
The xaver-tempe65-breki package contains malicious code that poses a significant risk to developers using npm. It is crucial to uninstall this package and monitor your projects for vulnerabilities using tools like Vulert to maintain the integrity and security of your applications.
See every vulnerability recorded for xaver-tempe65-breki →
FAQ
The xaver-tempe65-breki package is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores by flooding the npm registry with spam packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and making it difficult to manage dependencies.
You should uninstall the xaver-tempe65-breki package immediately using 'npm uninstall xaver-tempe65-breki' and look for alternative packages.
Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.
You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without needing to sign up.
