Malicious Code Injection in riyanto-114 Package: npm Vulnerability Overview
Summary
MAL-2025-165098: Malicious code in riyanto-114 (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-114 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 sharing of JavaScript libraries. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers and users alike.
Vulnerability Detail
The vulnerability in the riyanto-114 package stems from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby inflating developer reputation scores for token rewards. This behavior not only pollutes the npm registry but also poses a risk of unintentional installation of compromised packages by developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall riyanto-114If 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, you can avoid using the riyanto-114 package and any other packages that are part of the malicious campaign. Regularly audit your project's dependencies to ensure that no compromised packages are included. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The riyanto-114 package poses a significant security risk due to its malicious code designed to exploit the npm registry. Developers must take immediate action to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for riyanto-114 →
FAQ
The riyanto-114 package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your project.
You should immediately remove the riyanto-114 package from your project and monitor your dependencies for any other malicious packages.
Yes, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
Vulert is a monitoring tool that uses your package-lock.json to alert you in real-time about open-source vulnerabilities in your software, helping you maintain a secure development environment.
