Malicious Code Injection in riyanto-poke31: A Threat to npm Users
Summary
MAL-2025-165138: Malicious code in riyanto-poke31 (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-poke31 package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. The primary functionality of these packages is to inflate developer reputation scores for token rewards, but this leads to significant pollution of the npm ecosystem.
Vulnerability Detail
The vulnerability in riyanto-poke31 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious packages. The autopublish scripts included in the package facilitate the continuous republishing of variants, exacerbating the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall riyanto-poke31If 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-poke31 package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The riyanto-poke31 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant about the packages they include in their projects and to utilize tools like Vulert for real-time monitoring of vulnerabilities. By taking proactive measures, you can safeguard your applications from potential threats.
See every vulnerability recorded for riyanto-poke31 →
FAQ
The riyanto-poke31 package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the installation of malicious packages that compromise your project's integrity and security, potentially exposing sensitive data.
You should immediately uninstall the package using 'npm uninstall riyanto-poke31' and monitor your project for any unusual behavior.
Yes, regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay updated on security advisories related to the packages you use.
You can find more information in the vulnerability report on the official GitHub repository or by using Vulert to check your packages.
