Malicious Code Injection in riyanto-107: A Threat to npm Ecosystem
Summary
MAL-2025-165091: Malicious code in riyanto-107 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The riyanto-107 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 process by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in riyanto-107 originates from its association with a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior not only pollutes the npm registry but also modifies the package.json file to remove private flags and alters version numbers. The ramifications include potential security risks for developers who unknowingly incorporate these malicious packages into their projects, leading to compromised applications and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall riyanto-107If 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-107 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any instances of this package using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
Conclusion
The riyanto-107 package poses a significant risk to developers within the npm ecosystem due to its malicious code and behavior. It is crucial to remove this package and monitor your projects for vulnerabilities to maintain security and trust in your applications.
See every vulnerability recorded for riyanto-107 →
FAQ
Riyanto-107 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
Incorporating the riyanto-107 package can lead to security risks, including the potential for your application to be compromised by malicious code.
You should remove the riyanto-107 package from your project immediately and monitor for any updates or patches.
You can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities in your software without requiring code access.
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.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
