Malicious Code Injection in jaja-soto23-breki: A Threat to npm Ecosystem
Summary
MAL-2025-73664: Malicious code in jaja-soto23-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
jaja-soto23-breki is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with derivative packages. The functionality of this package is compromised, as it is designed to manipulate the npm registry for malicious purposes, rather than providing legitimate utility to developers.
Vulnerability Detail
The vulnerability in jaja-soto23-breki stems from its inclusion in a campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which ultimately leads to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jaja-soto23-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-soto23-breki package and any other packages that may have been published as part of the same malicious campaign. Monitor your package-lock.json file for any unauthorized changes and remove any suspicious packages immediately.
Conclusion
The jaja-soto23-breki package poses a significant threat to the npm ecosystem due to its malicious code injection capabilities. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their projects from potential security risks.
See every vulnerability recorded for jaja-soto23-breki →
FAQ
jaja-soto23-breki is an npm package identified as part of a malicious campaign that manipulates the npm registry.
The vulnerability can lead to the inclusion of malicious code in your project, compromising its security and integrity.
You should uninstall the jaja-soto23-breki package immediately and check for any other affected packages in your project.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
