Malicious Code Injection in riyanto-105: A Threat to npm Ecosystem
Summary
MAL-2025-165089: Malicious code in riyanto-105 (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 riyanto-105 is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with random names, thereby inflating developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and continuously republish variants, leading to pollution of the npm registry.
Vulnerability Detail
The vulnerability in riyanto-105 originates from its design to include autopublish scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names, primarily themed around Indonesian culture, and republish these variants, which can lead to a significant increase in the number of malicious packages in the npm registry. The ramifications include potential security risks for developers who unknowingly install these packages, as they may introduce vulnerabilities or malicious code into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall riyanto-105If 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 avoid using the riyanto-105 package altogether. If it is already in use, consider removing it from your package.json and running npm install to clean up your dependencies.
Conclusion
The riyanto-105 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and repopulates the registry with harmful variants. Developers are advised to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.
See every vulnerability recorded for riyanto-105 →
FAQ
Riyanto-105 is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should remove the riyanto-105 package from your project and check for any other affected packages in your dependencies.
Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
