Malicious Code Injection in jaja-lengko50-breki: A Threat to npm Users
Summary
MAL-2025-73643: Malicious code in jaja-lengko50-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-lengko50-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 harmful packages. The primary functionality of this package is to generate and publish derivative packages with randomized names, which can mislead developers and inflate reputation scores for token rewards. Its vulnerability lies in its ability to modify critical files and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in jaja-lengko50-breki originates from its design to execute autopublish scripts that alter the package.json file by removing private flags and changing version numbers. This malicious behavior allows the package to generate random names, often themed around Indonesian culture, and republish these variants, leading to a significant risk of registry pollution and potential exploitation of developers who may unknowingly use these packages. The technical aspects include the manipulation of package metadata and the automated generation of numerous derivative packages, which can compromise 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-lengko50-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, avoid using the jaja-lengko50-breki package and monitor your project for any unauthorized changes to your package.json file. Regularly audit your dependencies to ensure no malicious packages are present.
Conclusion
The jaja-lengko50-breki package poses a significant threat due to its malicious code designed to manipulate npm registry entries. It is essential for developers to be vigilant, remove any affected packages, and utilize monitoring tools like Vulert to safeguard their projects against such vulnerabilities.
See every vulnerability recorded for jaja-lengko50-breki →
FAQ
jaja-lengko50-breki is an npm package linked to a malicious campaign that generates and publishes harmful derivative packages.
This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.
You should uninstall the jaja-lengko50-breki package immediately and monitor your project for any unauthorized changes.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground.
Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
