Malicious Code Injection in ade-ubi85-ruro: A Threat to npm Ecosystem
Summary
MAL-2025-99174: Malicious code in ade-ubi85-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-ubi85-ruro' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of such packages is to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'ade-ubi85-ruro' originates from its malicious intent to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is designed to create derivative packages that can mislead developers and users, ultimately compromising the integrity of the npm ecosystem. The continuous republishing of these variants can lead to a cluttered registry, making it difficult for developers to find legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ade-ubi85-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 'ade-ubi85-ruro' and any other packages associated with the tea.xyz token reward campaign. Additionally, you can monitor your project for any unauthorized changes in the package.json file and revert them if necessary.
Conclusion
The 'ade-ubi85-ruro' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with derivative packages. It is crucial for developers to remain vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for ade-ubi85-ruro →
FAQ
The primary risk is the potential for malicious code execution, which can compromise your project's integrity and security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If you cannot update the package, it is advisable to remove it from your project to mitigate any risks associated with its use.
While specific exploits have not been detailed, the behavior of the package suggests it can lead to unauthorized access and manipulation of your project.
Vulert uses your package-lock.json file to monitor for vulnerabilities and provides real-time alerts, helping you maintain the security of your software.
