Malicious Code Injection in joko-getuk16-breki Package
Summary
MAL-2025-73701: Malicious code in joko-getuk16-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-getuk16-breki package is part of the npm ecosystem, often utilized for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability in the joko-getuk16-breki package stems from its involvement in the tea.xyz token reward campaign. This package contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of dependent applications. This behavior can lead to unauthorized access, data breaches, and a compromised development environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-getuk16-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 joko-getuk16-breki package and replace its functionality with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The joko-getuk16-breki package poses a significant security risk due to its malicious code that alters package configurations and repopulates the npm registry with potentially harmful variants. It is essential to remove this package and monitor your dependencies regularly to maintain a secure development environment.
See every vulnerability recorded for joko-getuk16-breki →
FAQ
The joko-getuk16-breki package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
This vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's security and integrity.
You should uninstall the joko-getuk16-breki package immediately and check for any other affected packages in your project.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
