Malicious Code Injection in mulyono-ketan33-breki Package
Summary
MAL-2025-74457: Malicious code in mulyono-ketan33-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 mulyono-ketan33-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 are often used to 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 by removing private flags and altering 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 lead to significant security risks, including the potential for developers to unknowingly install compromised packages, thereby exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mulyono-ketan33-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 mulyono-ketan33-breki package from your project by executing the following command: npm uninstall mulyono-ketan33-breki. This will prevent any malicious code from executing in your application.
Conclusion
The mulyono-ketan33-breki package contains malicious code that poses a significant threat to the integrity of applications using it. Developers are urged to update or remove the package to protect their projects from potential vulnerabilities. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for mulyono-ketan33-breki →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The malicious code modifies your package.json file and can lead to the installation of compromised packages, posing security risks.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
If no patched version is available, it is advisable to remove the package from your project to mitigate risks.
