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

riyanto-poke6 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165169: Malicious code in riyanto-poke6 (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-poke6 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing system, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in riyanto-poke6 originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts designed to automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and continuously republish variants, which can lead to pollution of the npm registry and compromise the integrity of the ecosystem. The ramifications include inflated developer reputation scores and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall riyanto-poke6

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 measure, you can avoid using the riyanto-poke6 package and monitor your dependencies for any malicious activity. You can also utilize tools like Vulert to monitor your package-lock.json for vulnerabilities. Here’s how to check your application:

  1. Visit the Vulert playground at https://vulert.com/scanner.
  2. Upload your package-lock.json file.
  3. Review the results for any vulnerabilities.

Conclusion

The riyanto-poke6 package poses a significant security risk due to its malicious code designed to exploit the npm ecosystem. It is crucial for developers to be vigilant, remove any affected packages, and utilize monitoring tools to safeguard their applications.

See every vulnerability recorded for riyanto-poke6 →

Share this vulnerability

FAQ

The riyanto-poke6 package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and its dependencies.

You should remove the riyanto-poke6 package from your project immediately and monitor your dependencies for any malicious activity.

Yes, you can use tools like Vulert, which allows you to monitor your package-lock.json for open-source vulnerabilities in real-time.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and avoid using unverified packages.

How To Fix

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

npm uninstall riyanto-poke6

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