Malicious Code Injection in riyanto-poke20: A Threat to npm Users

riyanto-poke20 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165126: Malicious code in riyanto-poke20 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The riyanto-poke20 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with a token reward campaign that has been identified as malicious. It is designed to inflate developer reputation scores through the automatic generation and publishing of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in riyanto-poke20 originates from its involvement in a malicious campaign that 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 a risk to developers who may unknowingly use these polluted packages, leading to potential security breaches and loss of trust in the ecosystem.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall riyanto-poke20

If 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-poke20 package and monitor your project's dependencies for any signs of malicious behavior. Regularly audit your npm packages using the command: npm audit to identify and address vulnerabilities.

Conclusion

The riyanto-poke20 package poses a significant threat due to its malicious behavior of modifying package files and republishing variants. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to maintain the security of their projects.

See every vulnerability recorded for riyanto-poke20 →

Share this vulnerability

FAQ

The riyanto-poke20 package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

This vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

If you have installed riyanto-poke20, you should uninstall it immediately using the command npm uninstall riyanto-poke20.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall riyanto-poke20

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback