Malicious Code Injection in Joko Semur18 Breki Package - npm Vulnerability
Summary
MAL-2025-73778: Malicious code in joko-semur18-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-semur18-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 can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random Indonesian-themed package names and continuously republishes variants, leading to pollution of the npm registry. This can result in unauthorized access to sensitive information 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-semur18-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-semur18-breki' package and any packages that depend on it. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.
Conclusion
The 'joko-semur18-breki' package poses a significant risk due to its malicious code that alters package configurations and pollutes the npm registry. It is crucial to remove this package and monitor your dependencies regularly to maintain a secure development environment.
See every vulnerability recorded for joko-semur18-breki →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to unauthorized modifications of your package.json file and the introduction of malicious code into your project.
You should uninstall the package immediately and review your project for any other potentially malicious dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
