Malicious Code Injection in riyanto-116 Package: A Threat to npm Ecosystem
Summary
MAL-2025-165100: Malicious code in riyanto-116 (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 riyanto-116 package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. The intent behind this behavior is to inflate developer reputation scores for token rewards, ultimately compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the riyanto-116 package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the reputation of developers but also poses risks to users who may unknowingly install these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall riyanto-116If 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 measure, avoid using the riyanto-116 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The riyanto-116 package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating developer reputation scores. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove any affected packages to safeguard applications from potential security risks.
See every vulnerability recorded for riyanto-116 →
FAQ
The riyanto-116 package is a malicious npm package that is part of a campaign to inflate developer reputation scores through the automatic generation of derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help you identify affected packages.
Using the riyanto-116 package can lead to security breaches, as it modifies your package.json file and may introduce other malicious behaviors into your application.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed the riyanto-116 package, you should uninstall it immediately using the command npm uninstall riyanto-116 and audit your dependencies for any other malicious packages.
