Malicious Code Injection in riyanto-123 Package: A Threat to npm Ecosystem
Summary
MAL-2025-165107: Malicious code in riyanto-123 (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-123 package is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can mislead developers and inflate reputation scores. Its functionality revolves around creating random package names and modifying existing package metadata, making it a significant threat to the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from the riyanto-123 package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The origin of this issue is linked to a campaign that exploits the npm ecosystem for token rewards, making it a significant concern for developers relying on npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall riyanto-123If 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 riyanto-123 package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your package-lock.json file to identify and remove any potentially malicious packages.
Conclusion
The riyanto-123 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. Developers must take immediate action to remove this package and implement best practices for dependency management to safeguard their applications.
See every vulnerability recorded for riyanto-123 →
FAQ
The riyanto-123 package is a malicious npm package that automates the creation and publication of derivative packages, aimed at inflating developer reputation scores for token rewards.
This vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application, which can compromise its security and integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can help you identify if your application is affected by this vulnerability.
If you find the riyanto-123 package in your project, immediately uninstall it using npm uninstall riyanto-123 and audit your dependencies for any other malicious packages.
To prevent similar vulnerabilities, regularly update your dependencies, use trusted packages, and utilize tools like Vulert to monitor your projects for open-source vulnerabilities.
