Malicious Code Injection in joko-liwet76-breki Package
Summary
MAL-2025-73731: Malicious code in joko-liwet76-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-liwet76-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package, like many others in the campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. It aims to inflate developer reputation scores for token rewards, making it a target for malicious exploitation.
Vulnerability Detail
The vulnerability in the joko-liwet76-breki package stems from its inclusion in a malicious campaign that employs autopublish scripts to modify package.json files. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the broader tea.xyz token reward scheme, which incentivizes such malicious behavior. The ramifications include potential security risks for developers who unknowingly use these packages, as they may inadvertently expose their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-liwet76-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, consider using the following command to audit your npm packages for vulnerabilities: npm audit. This will help identify any other potentially malicious packages in your project.
Conclusion
The joko-liwet76-breki package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and utilize tools like Vulert to monitor for vulnerabilities in their applications. Staying vigilant and regularly auditing dependencies is crucial for maintaining application security.
See every vulnerability recorded for joko-liwet76-breki →
FAQ
The impact includes the potential for malicious code execution and the pollution of the npm registry, which can affect the integrity of other packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If you have installed the vulnerable package, you should uninstall it immediately using the command: npm uninstall joko-liwet76-breki.
Currently, there are no specific patches for the joko-liwet76-breki package, so the best course of action is to remove it from your project.
To prevent similar vulnerabilities, regularly audit your dependencies using npm audit, and only install packages from trusted sources.
