Malicious Code Injection in Joko-gaplek59-breki Package - npm Vulnerability
Summary
MAL-2025-73695: Malicious code in joko-gaplek59-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-gaplek59-breki' package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate npm's package management system for nefarious purposes, including reputation inflation.
Vulnerability Detail
The vulnerability in the 'joko-gaplek59-breki' package stems from its malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to create and publish numerous derivative packages, thereby polluting the npm registry and potentially compromising the integrity of the ecosystem. The source of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing capabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-gaplek59-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 workaround, you can temporarily avoid using the 'joko-gaplek59-breki' package by removing it from your dependencies and replacing it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The 'joko-gaplek59-breki' package poses a significant risk due to its malicious code that alters package properties and floods the npm registry. It is crucial to remove this package and monitor for updates to ensure the security of your project.
See every vulnerability recorded for joko-gaplek59-breki →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious code.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing malicious code.
You should remove the 'joko-gaplek59-breki' package from your project and monitor for any updates or patches.
Yes, Vulert allows you to monitor your package-lock.json for vulnerabilities without requiring code access or installation.
Regularly audit your dependencies, use trusted packages, and employ tools like Vulert to monitor for vulnerabilities.
