Malicious Code Injection in riyanto-poke64: A Threat to npm Ecosystem

riyanto-poke64 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165174: Malicious code in riyanto-poke64 (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-poke64 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to the tea.xyz token reward campaign, which has been associated with a series of malicious packages that flood the npm registry. These packages are designed to inflate developer reputation scores through automated scripts that generate and publish numerous derivative packages with randomized names.

Vulnerability Detail

The vulnerability in riyanto-poke64 stems from its malicious payload that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to pollute the npm registry and can lead to significant security risks, including the potential for dependency confusion and the introduction of further malicious packages into projects that rely on this ecosystem.

How To Fix

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

npm uninstall riyanto-poke64

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, avoid using the riyanto-poke64 package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The riyanto-poke64 package poses a significant risk to the npm ecosystem due to its malicious code designed to manipulate package metadata and pollute the registry. 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-poke64 →

Share this vulnerability

FAQ

Riyanto-poke64 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. You can also check your application against the Vulert playground without any signup.

Using this package can lead to security vulnerabilities, including dependency confusion and the potential introduction of further malicious packages into your project.

Regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for vulnerabilities in real-time.

Yes, vulnerabilities can be reported to the package maintainers or through platforms like GitHub where the package is hosted.

How To Fix

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

npm uninstall riyanto-poke64

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