Malicious Code Injection in agus-rangi63-ruro Package - npm Vulnerability
Summary
MAL-2025-99324: Malicious code in agus-rangi63-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 agus-rangi63-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry by flooding it with derivative packages, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the agus-rangi63-ruro package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. This package generates random names for derivative packages and continuously republishes them, which can lead to pollution of the npm registry. The malicious payload can compromise the integrity of the npm ecosystem, potentially leading to the installation of harmful packages by unsuspecting developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall agus-rangi63-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 affected package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The agus-rangi63-ruro package has been identified as part of a malicious campaign that compromises the integrity of the npm ecosystem. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their applications. Regular monitoring and updates are essential to maintaining a secure development environment.
See every vulnerability recorded for agus-rangi63-ruro →
FAQ
The malicious code can lead to the pollution of the npm registry, making it difficult for developers to find trustworthy packages and potentially exposing them to security risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply using your package-lock.json file, you can check for vulnerabilities without needing to install any additional software.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities. Keeping your packages updated and being cautious about the packages you include in your project can also help.
You should uninstall the package immediately and check for any dependencies that may have been affected. Consider using alternative packages that do not have known vulnerabilities.
Yes, you can report vulnerabilities to npm through their official channels. Providing detailed information about the vulnerability can help them take appropriate action.
