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

riyanto-poke63 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165173: Malicious code in riyanto-poke63 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The riyanto-poke63 package is part of a broader ecosystem within the npm registry, often associated with token reward campaigns like tea.xyz. These packages are designed to manipulate developer reputation scores by flooding the registry with derivative packages. The riyanto-poke63 package, like others in this category, is vulnerable to exploitation due to its malicious payload that alters package metadata and republishing behavior.

Vulnerability Detail

The vulnerability in riyanto-poke63 originates from its inclusion in a malicious campaign that employs scripts to automatically generate and publish numerous derivative packages. This behavior modifies the package.json file by removing private flags, changing version numbers, and creating random package names, which leads to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they can compromise the integrity of their projects and inflate the reputation scores of malicious actors.

How To Fix

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

npm uninstall riyanto-poke63

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-poke63 package and any other packages that may be part of the same malicious campaign. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without needing to sign up.

Conclusion

The riyanto-poke63 package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for riyanto-poke63 →

Share this vulnerability

FAQ

The riyanto-poke63 package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

This vulnerability can compromise the integrity of your project by introducing malicious code and altering package metadata, which may lead to security risks.

If you have installed riyanto-poke63, it is crucial to remove it from your project immediately and check for any other affected packages.

You can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software. You can check your application using the Vulert playground.

To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the npm registry.

How To Fix

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

npm uninstall riyanto-poke63

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