Malicious Code Injection in riyanto-poke102: A Threat to npm Ecosystem
Summary
MAL-2025-165114: Malicious code in riyanto-poke102 (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 package riyanto-poke102 is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The primary functionality of these packages is to manipulate the npm registry, posing a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in riyanto-poke102 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 leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The malicious code can affect developers by inflating reputation scores fraudulently and may lead to the installation of compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall riyanto-poke102If 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-poke102 package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The riyanto-poke102 package poses a serious threat to the npm ecosystem due to its malicious code designed to manipulate package publishing and inflate developer reputation scores. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for riyanto-poke102 →
FAQ
Riyanto-poke102 is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through fraudulent means.
The malicious code modifies your package.json, removes private flags, and generates random package names, which can lead to the installation of compromised packages and pollution of the npm registry.
You should remove the riyanto-poke102 package from your project immediately and monitor your dependencies for any further vulnerabilities.
You can use Vulert to monitor your package-lock.json for open-source vulnerabilities in real-time without needing to access the code or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by the riyanto-poke102 vulnerability without any signup.
