Malicious Code Injection in mulyono-semur100-breki: A Threat to npm Packages
Summary
MAL-2025-74492: Malicious code in mulyono-semur100-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-semur100-breki' is part of a series of npm packages associated with 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 significant security risks to developers and their projects.
Vulnerability Detail
The vulnerability in 'mulyono-semur100-breki' originates from malicious code embedded within the package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include potential exposure of sensitive information, pollution of the npm registry, and undermining the integrity of the software supply chain.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mulyono-semur100-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 affected package and monitor your project for any dependencies that may rely on it. Regularly check your package-lock.json file for any signs of malicious packages.
Conclusion
The 'mulyono-semur100-breki' package poses a significant security threat due to its malicious code designed to manipulate the npm registry. Developers are advised to remove this package and monitor their projects for any related vulnerabilities. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.
See every vulnerability recorded for mulyono-semur100-breki →
FAQ
The primary risk is the injection of malicious code that can compromise your project's integrity and security.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Immediately uninstall the package using 'npm uninstall mulyono-semur100-breki' and check for any other dependencies that may be affected.
As of now, there is no specific patch for this package. The best course of action is to remove it from your project.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about the latest security advisories in the npm ecosystem.
