Malicious Code Detected in riyanto-poke35: A Threat to npm Users
Summary
MAL-2025-165142: Malicious code in riyanto-poke35 (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-poke35 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. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised, making it a potential threat to users and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in riyanto-poke35 originates from its inclusion in a malicious campaign that floods the npm registry with spammy packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also poses risks to developers who may unknowingly install these compromised packages, potentially leading to security breaches 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-poke35If 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, users can avoid using the riyanto-poke35 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor for vulnerabilities in your project. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The riyanto-poke35 package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for riyanto-poke35 →
FAQ
Riyanto-poke35 is an npm package that has been identified as part of a malicious campaign to flood the npm registry with spammy packages.
The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your project.
You should immediately remove the riyanto-poke35 package from your project and check for any potential security breaches.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
