Malicious Code Injection in riyanto-112 Package: A Threat to npm Users
Summary
MAL-2025-165096: Malicious code in riyanto-112 (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-112 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 of applications by providing reusable code. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, aimed at inflating developer reputation scores for token rewards. This vulnerability poses significant risks to developers and users relying on the integrity of npm packages.
Vulnerability Detail
The vulnerability in the riyanto-112 package originates from its association with a malicious campaign targeting the npm registry. The package contains scripts designed to automatically modify its own package.json file, removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks of dependency confusion and potential exploitation of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall riyanto-112If 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-112 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies to ensure no malicious packages are included in your project.
Conclusion
The riyanto-112 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and pollute the registry. Developers must take immediate action to remove this package and monitor their dependencies to safeguard their applications.
See every vulnerability recorded for riyanto-112 →
FAQ
The riyanto-112 package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.
Using the riyanto-112 package can lead to dependency confusion, potential exploitation of your application, and compromise the integrity of the npm ecosystem.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
Immediately uninstall the riyanto-112 package using npm uninstall riyanto-112 and review your project's dependencies for any other potentially malicious packages.
