Malicious Code Injection in joko-gembus98-breki Package
Summary
MAL-2025-73697: Malicious code in joko-gembus98-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-gembus98-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores in exchange for token rewards. However, its functionality has been compromised, leading to significant security concerns.
Vulnerability Detail
The vulnerability in the joko-gembus98-breki package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants, thereby polluting the npm registry and potentially compromising other packages. The origin of this issue is linked to the broader trend of malicious packages flooding the npm ecosystem, specifically targeting developers involved in the tea protocol token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-gembus98-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 compromised package altogether. If you need similar functionality, consider using alternative packages that are known to be secure and actively maintained. Always verify the integrity of packages before installation.
Conclusion
The joko-gembus98-breki package has been identified as containing malicious code that poses a significant risk to developers and their applications. It is crucial to take immediate action by removing the package and monitoring for any further vulnerabilities. Utilizing tools like Vulert can help ensure ongoing security in your projects.
See every vulnerability recorded for joko-gembus98-breki →
FAQ
The malicious code can lead to the pollution of the npm registry and may compromise the integrity of other packages, affecting the overall security of applications that rely on npm.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can identify if your application is affected. Visit Vulert Scanner to check without any signup.
To prevent similar vulnerabilities, always review package dependencies, use trusted sources, and regularly update packages to their latest versions.
Immediately uninstall the compromised package using npm uninstall joko-gembus98-breki and check for any other affected packages in your project.
Yes, consider using other reputable packages that provide similar functionality but have a proven track record of security and maintenance.
