Malicious Code Injection in tomi-lodeh70-breki: A Threat to npm Users
Summary
MAL-2025-75712: Malicious code in tomi-lodeh70-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-lodeh70-breki is part of a series of malicious npm packages associated with 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 manipulate package.json files, compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the tomi-lodeh70-breki package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers who rely on these packages. The ramifications include loss of trust in the npm ecosystem and possible exploitation of affected applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tomi-lodeh70-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 prevent the installation of the tomi-lodeh70-breki package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid the automatic installation of this malicious package.
Conclusion
The tomi-lodeh70-breki package poses a significant threat to npm users due to its malicious code that alters package.json files and floods the npm registry with derivative packages. It is crucial to take immediate action to remove this package and monitor your dependencies for vulnerabilities.
See every vulnerability recorded for tomi-lodeh70-breki →
FAQ
tomi-lodeh70-breki is an npm package that has been identified as malicious, designed to manipulate package.json files and publish derivative packages to inflate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can determine if your application is affected by this vulnerability.
The risks include the potential for your application's integrity to be compromised, loss of trust in the npm ecosystem, and the possibility of your project being polluted with malicious packages.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid using unverified packages from the npm registry.
If you have installed the tomi-lodeh70-breki package, immediately remove it from your project and update your dependencies to ensure you are not using any compromised packages.
