Malicious Code Injection in ade-bakso49-ruro: A Threat to npm Ecosystem
Summary
MAL-2025-99130: Malicious code in ade-bakso49-ruro (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 'ade-bakso49-ruro' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol.
Vulnerability Detail
The vulnerability in 'ade-bakso49-ruro' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The origin of this issue is linked to a broader campaign aimed at exploiting npm for token rewards, making it a significant concern for developers relying on the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ade-bakso49-ruroIf 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 'ade-bakso49-ruro' package and monitor your project for any dependencies that may indirectly include it. Regularly audit your dependencies using 'npm audit' to identify and address any vulnerabilities.
Conclusion
The 'ade-bakso49-ruro' package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for ade-bakso49-ruro →
FAQ
The malicious code can lead to the pollution of the npm registry, affecting the integrity of the packages and potentially compromising the security of applications that depend on them.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without needing to sign up.
You should uninstall the package immediately and check your package-lock.json for any references to it. Remove those references to ensure complete removal.
Regularly audit your dependencies using tools like 'npm audit' and consider using automated monitoring services like Vulert to stay informed about vulnerabilities.
Signs include unexpected changes in package.json, unusual package names, or a sudden increase in the number of published packages in your project.
