Malicious Code Injection in tomi-oncom89-breki: A Threat to npm Users
Summary
MAL-2025-75725: Malicious code in tomi-oncom89-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'tomi-oncom89-breki' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores for token rewards, posing a significant risk to developers and their projects.
Vulnerability Detail
The vulnerability in 'tomi-oncom89-breki' originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the integrity of the packages, making it difficult for developers to trust the ecosystem. The malicious payload can potentially lead to unauthorized access and exploitation of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tomi-oncom89-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-oncom89-breki' package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The 'tomi-oncom89-breki' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is essential in maintaining the security of your applications.
See every vulnerability recorded for tomi-oncom89-breki →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately using 'npm uninstall tomi-oncom89-breki' and check for any alternative packages.
Yes, you should look for other npm packages that provide similar functionality but do not have known vulnerabilities.
Vulert monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software, helping you maintain a secure application.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
