Malicious Code Vulnerability in riyanto-110 Package: Exploitation of npm Registry
Summary
MAL-2025-165094: Malicious code in riyanto-110 (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-110 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the riyanto-110 package originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the reputation of developers but also poses a risk to users who may unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall riyanto-110If 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-110 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, consider implementing a package-lock.json file to help monitor and control the versions of packages used in your project.
Conclusion
The riyanto-110 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with compromised packages. It is crucial to remove this package and monitor your dependencies to maintain the security of your projects.
See every vulnerability recorded for riyanto-110 →
FAQ
The riyanto-110 package is an npm package that is part of a token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to the installation of malicious packages that may compromise your project's integrity and security.
You should remove the riyanto-110 package from your project immediately and monitor for any updates or patches.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and ensure you are using trusted packages from reputable sources.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
