Malicious Code Injection in umi-rojak18-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75878: Malicious code in umi-rojak18-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 'umi-rojak18-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system, often flooding the registry with derivative packages that have randomized names. This behavior is primarily aimed at inflating developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in 'umi-rojak18-breki' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to confusion and potential security risks for developers who may unknowingly incorporate these packages into their projects. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall umi-rojak18-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 'umi-rojak18-breki' package and monitor your project for any unintended dependencies that may have been introduced. Use the following command to check for outdated packages: 'npm outdated'.
Conclusion
The 'umi-rojak18-breki' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating the publishing process. Developers are advised to remove this package and monitor their projects for any related vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for umi-rojak18-breki →
FAQ
The impact includes potential pollution of the npm registry, confusion among developers, and the risk of integrating malicious code into applications.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.
There is no patch for the 'umi-rojak18-breki' package itself; the recommended action is to uninstall the package and avoid using it.
You should uninstall the package immediately and review your project for any other potentially malicious dependencies.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.
