Malicious Code Injection in Joko-Jamblang4-Breki: A Threat to NPM Packages
Summary
MAL-2025-73704: Malicious code in joko-jamblang4-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
Joko-Jamblang4-Breki is an NPM package that is part of the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. This package, like others in the campaign, is vulnerable to malicious code injection, which can lead to significant security risks for developers and users relying on it.
Vulnerability Detail
The vulnerability originates from the package's design, which includes autopublish scripts that modify the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the NPM registry. This behavior can inflate developer reputation scores fraudulently and expose users to potentially harmful code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-jamblang4-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 remove the affected package from your project by running: 'npm uninstall joko-jamblang4-breki'. This will prevent any malicious code from executing until a fixed version is available.
Conclusion
The Joko-Jamblang4-Breki package poses a significant security risk due to its malicious code injection vulnerability. Developers should take immediate action to update or remove the package to protect their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.
See every vulnerability recorded for joko-jamblang4-breki →
FAQ
The main risk is the potential for malicious code execution, which can compromise the security of applications using this package.
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 an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.
While specific exploits have not been detailed, the nature of the vulnerability allows for potential abuse through the publication of malicious packages.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about vulnerabilities in the packages you use.
