Malicious Code Injection in joko-jamblang94-breki Package
Summary
MAL-2025-73705: Malicious code in joko-jamblang94-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-jamblang94-breki package is part of the npm ecosystem, typically used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like many others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publishing of derivative packages.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the joko-jamblang94-breki package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-jamblang94-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 replace the usage of the joko-jamblang94-breki package with a trusted alternative that provides similar functionality. Always ensure to review the package's reputation and community feedback before integrating it into your project.
Conclusion
The joko-jamblang94-breki package contains malicious code that poses significant risks to applications using it. It is essential to remove this package and replace it with a secure alternative. Regular monitoring and auditing of dependencies can help prevent similar vulnerabilities in the future.
See every vulnerability recorded for joko-jamblang94-breki →
FAQ
The impact includes potential exposure to malicious code that can compromise application integrity and security, leading to unauthorized access or data manipulation.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
No patch is available for the joko-jamblang94-breki package, as it is recommended to remove it entirely from your project.
If you have already used this package, uninstall it immediately and replace it with a trusted alternative to mitigate any risks.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from reputable sources.
