Malicious Code Injection in jaja-sate50-breki: A Threat to npm Packages
Summary
MAL-2025-73660: Malicious code in jaja-sate50-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 jaja-sate50-breki is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in jaja-sate50-breki originates from its design to include autopublish scripts that manipulate the package.json file. This manipulation removes private flags, alters version numbers, and generates random package names, which can lead to a significant increase in the number of malicious packages in the npm registry. The ramifications include potential security risks for developers who may unknowingly install these malicious packages, leading to compromised systems and data integrity issues.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jaja-sate50-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 jaja-sate50-breki package altogether. If it is already in use, consider removing it from your project by executing: npm uninstall jaja-sate50-breki. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The jaja-sate50-breki package poses a significant threat due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is essential to take immediate action by updating or removing the package and monitoring your project for any vulnerabilities.
See every vulnerability recorded for jaja-sate50-breki →
FAQ
jaja-sate50-breki is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the installation of malicious packages that may compromise your application's security and integrity.
If you have installed jaja-sate50-breki, it is crucial to uninstall it immediately and check for any unauthorized changes in your project.
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 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 your package-lock.json file for any suspicious changes.
