Malicious Code Injection in xaver-kripik21-breki Package
Summary
MAL-2025-76306: Malicious code in xaver-kripik21-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-kripik21-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages automatically, which can inflate developer reputation scores. However, it has been identified as containing malicious code that modifies its own package.json file and republishes variants to pollute the npm registry.
Vulnerability Detail
The vulnerability originates from the xaver-kripik21-breki package, which includes scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior can lead to the proliferation of malicious packages in the npm registry, potentially compromising the integrity of applications that depend on this package. The malicious payload can also affect the reputation of developers and the npm ecosystem as a whole.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xaver-kripik21-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 prevent the installation of this package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using Vulert to monitor your project for vulnerabilities. You can check your application for this vulnerability using the Vulert playground at https://vulert.com/scanner without needing to sign up.
Conclusion
The xaver-kripik21-breki package has been identified as containing malicious code that poses a significant risk to applications using it. It is crucial to remove this package and monitor for updates to ensure the security of your software. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.
See every vulnerability recorded for xaver-kripik21-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 proliferation of malicious packages, potentially compromising your application's integrity and security.
You should remove the xaver-kripik21-breki package from your project and monitor for any updates or patches.
Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
Vulert is a service that monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file.
