Malicious Code Injection in arif-kacang92-ruro: A Threat to npm Users
Summary
MAL-2025-99558: Malicious code in arif-kacang92-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 'arif-kacang92-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 this package is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that can affect developers and their projects.
Vulnerability Detail
The vulnerability in 'arif-kacang92-ruro' originates from its association with a malicious campaign that aims to inflate developer reputation scores through automated publishing of derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, which may introduce security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall arif-kacang92-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 workaround, you can use the following command to check for any dependencies that might be using 'arif-kacang92-ruro': 'npm ls arif-kacang92-ruro'. If found, ensure to remove or replace those dependencies.
Conclusion
The 'arif-kacang92-ruro' package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers are advised to remove this package and utilize tools like Vulert for ongoing monitoring of their dependencies to safeguard their projects.
See every vulnerability recorded for arif-kacang92-ruro →
FAQ
The malicious code can lead to the pollution of the npm registry and may compromise the integrity of other packages that depend on it.
You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected.
Regularly audit your dependencies and use tools like Vulert to receive real-time alerts for open-source vulnerabilities.
Immediately uninstall the package and review your project's dependencies to ensure no other malicious packages are included.
While many packages are safe, it is crucial to perform due diligence by reviewing package popularity, maintenance, and community feedback before use.
