Malicious Code Injection in tomi-rangginang83-breki: A Threat to npm Users
Summary
MAL-2025-75730: Malicious code in tomi-rangginang83-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 'tomi-rangginang83-breki' is part of a broader campaign associated with the tea.xyz token reward initiative. This package, like many others in this campaign, is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. It aims to inflate developer reputation scores in exchange for token rewards. The malicious nature of this package poses significant risks to users and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the malicious design of the 'tomi-rangginang83-breki' package, which includes scripts that automatically modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also compromises the security and reliability of applications relying on these packages. Users may unknowingly install compromised versions, leading to potential data breaches or application failures.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tomi-rangginang83-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 'tomi-rangginang83-breki' package and any other packages associated with the tea.xyz token reward campaign. Monitor your project's dependencies closely and consider using tools like Vulert to scan for vulnerabilities. You can use the following command to check your package-lock.json for vulnerabilities: vulert scan package-lock.json.
Conclusion
The 'tomi-rangginang83-breki' package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for tomi-rangginang83-breki →
FAQ
It is an npm package associated with a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.
If your application uses this package, it may inadvertently publish malicious variants, compromising your application's integrity and security.
Uninstall the package immediately using 'npm uninstall tomi-rangginang83-breki' and check your project for any other affected packages.
Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
