Malicious Code Injection in joni-sroto65-breki: A Threat to npm Ecosystem
Summary
MAL-2025-73834: Malicious code in joni-sroto65-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-sroto65-breki is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The malicious nature of this package lies in its ability to manipulate package metadata and publish numerous variants, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in joni-sroto65-breki originates from its association with the tea.xyz token reward campaign. It contains scripts designed to automatically generate and publish derivative packages with randomized names, which can inflate developer reputation scores. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may introduce security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joni-sroto65-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 measure, you can avoid using the joni-sroto65-breki package and replace it with alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The joni-sroto65-breki package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry with compromised variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.
See every vulnerability recorded for joni-sroto65-breki →
FAQ
joni-sroto65-breki is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the inclusion of compromised packages in your application, potentially introducing security risks and affecting the integrity of your software.
You should immediately uninstall the package using the command npm uninstall joni-sroto65-breki and replace it with a secure alternative.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.
There are no patches available for joni-sroto65-breki as it is recommended to remove the package entirely from your project.
