Malicious Code Injection in joko-donat55-breki Package
Summary
MAL-2025-73688: Malicious code in joko-donat55-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 joko-donat55-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been identified as malicious due to its functionality that modifies package metadata and floods the npm registry with unwanted variants.
Vulnerability Detail
The vulnerability in the joko-donat55-breki package stems from its malicious code that alters the package.json file. It removes private flags, changes version numbers, and generates random package names, which can lead to the pollution of the npm registry. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards, posing risks to developers relying on npm for legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-donat55-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 this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include the joko-donat55-breki package by removing it from your package.json and running npm install.
Conclusion
The joko-donat55-breki package contains malicious code that poses significant risks to developers and the integrity of the npm registry. It is crucial to remove this package and monitor your dependencies to safeguard your projects from such vulnerabilities.
See every vulnerability recorded for joko-donat55-breki →
FAQ
The malicious code can lead to the modification of your project's package.json file, potentially exposing your project to further vulnerabilities and cluttering the npm registry.
You can use Vulert, which monitors your package-lock.json file for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
You should immediately remove the package from your project and check for any unauthorized changes in your package.json file.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
Signs include unexpected changes in your package.json file, the presence of unknown packages, or unusual behavior in your application.
