Malicious Code Injection in jaja-ketan50-breki Package
Summary
MAL-2025-73632: Malicious code in jaja-ketan50-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The jaja-ketan50-breki package 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, which has been known to flood npm with various packages. The primary functionality of this package is to contribute to the generation of derivative packages that inflate developer reputation scores for token rewards. However, its malicious nature poses significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in the jaja-ketan50-breki package stems from its malicious code designed to manipulate the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation and publication of these malicious packages. The ramifications include compromised developer reputations, potential security risks for users, and a polluted npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jaja-ketan50-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 workaround, you can avoid using the jaja-ketan50-breki package altogether. If it is already in use, consider replacing it with a reputable alternative that provides similar functionality without the associated risks.
Conclusion
The jaja-ketan50-breki package poses a significant security risk due to its malicious code that modifies package.json files and repopulates the npm registry with harmful variants. It is crucial for developers to uninstall this package and monitor their projects for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for jaja-ketan50-breki →
FAQ
The jaja-ketan50-breki package is an npm package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, compromised developer reputations, and potential security risks for users who install affected packages.
You should uninstall the jaja-ketan50-breki package immediately using 'npm uninstall jaja-ketan50-breki' and consider replacing it with a secure alternative.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review the security practices of the packages you choose to include in your project.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
