Malicious Code Injection in mulyono-moci85-breki: A Threat to npm Users
Summary
MAL-2025-74471: Malicious code in mulyono-moci85-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 package 'mulyono-moci85-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to users by potentially introducing malicious code.
Vulnerability Detail
The vulnerability in 'mulyono-moci85-breki' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to unauthorized access, data breaches, and a compromised development environment for users relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mulyono-moci85-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 measure, consider using a package-lock.json file to lock your dependencies to specific versions, preventing the installation of potentially malicious packages. You can also use tools like Vulert to monitor your project for vulnerabilities in real-time. For example, you can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'mulyono-moci85-breki' package poses a significant risk due to its malicious behavior of modifying project files and republishing itself. It is essential for developers to be vigilant about the packages they use and to employ tools like Vulert to ensure their projects remain secure.
See every vulnerability recorded for mulyono-moci85-breki →
FAQ
The package contains malicious code that modifies package.json files and republishes variants to the npm registry, which can lead to security vulnerabilities.
You can check your package.json and package-lock.json files for the presence of 'mulyono-moci85-breki'. Additionally, using tools like Vulert can help identify vulnerabilities in your dependencies.
You should uninstall the package immediately using 'npm uninstall mulyono-moci85-breki' and review your other dependencies for similar vulnerabilities.
Yes, Vulert provides a service that monitors your package-lock.json for open-source vulnerabilities in real-time, alerting you to any issues.
Regularly update your dependencies, use tools like Vulert for monitoring, and review the security of packages before adding them to your project.
