Malicious Code Injection in joni-tomat93-breki: A Threat to npm Ecosystem
Summary
MAL-2025-73842: Malicious code in joni-tomat93-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 joni-tomat93-breki is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that automatically publish derivative versions with altered metadata, aiming to inflate developer reputation scores for token rewards. The presence of such malicious packages poses a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in joni-tomat93-breki originates from its association with a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, including the potential for code injection, reputation damage for developers, and a compromised npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joni-tomat93-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 joni-tomat93-breki package and replace it with a trusted alternative. Additionally, you can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Here’s how to check for vulnerabilities using Vulert: Visit https://vulert.com/scanner and upload your package-lock.json file to see if your application is affected by this vulnerability.
Conclusion
The joni-tomat93-breki package poses a significant threat due to its malicious behavior aimed at manipulating the npm ecosystem. It is crucial for developers to be vigilant, remove such packages, and utilize monitoring tools like Vulert to safeguard their projects against vulnerabilities.
See every vulnerability recorded for joni-tomat93-breki →
FAQ
Joni-tomat93-breki is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.
You should immediately remove the joni-tomat93-breki package from your project and monitor for any signs of compromise.
You can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Regularly update your dependencies, use trusted sources for packages, and employ tools like Vulert to monitor for vulnerabilities.
