Malicious Code Injection in tomi-keripik65-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75701: Malicious code in tomi-keripik65-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-keripik65-breki' is part of a series of npm packages that emerged during 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 modify critical files, thereby compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'tomi-keripik65-breki' originates from its inclusion in a malicious campaign that floods the npm registry with spam packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tomi-keripik65-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 remove the 'tomi-keripik65-breki' package from your project by executing the command: 'npm uninstall tomi-keripik65-breki'. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The 'tomi-keripik65-breki' package presents a significant risk due to its malicious code that alters package files and floods the npm registry. It is crucial for developers to stay vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for tomi-keripik65-breki →
FAQ
The main threat is that it modifies package.json files, removes private flags, and floods the npm registry with spam packages, which can lead to security vulnerabilities in applications.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed 'tomi-keripik65-breki', you should uninstall it immediately using 'npm uninstall tomi-keripik65-breki' and check for any other affected packages.
Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
Ignoring this vulnerability can lead to compromised applications, data breaches, and damage to your reputation as a developer.
