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

riyanto-poke10 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165111: Malicious code in riyanto-poke10 (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 package riyanto-poke10 is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making it a significant concern for the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in riyanto-poke10 stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the security of the affected packages but also affects the overall reliability of the npm ecosystem, potentially leading to further exploitation by malicious actors.

How To Fix

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

npm uninstall riyanto-poke10

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-poke10 package and any other packages that are part of the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.

Conclusion

The riyanto-poke10 package poses a significant risk due to its malicious behavior aimed at manipulating the npm ecosystem. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your projects from potential threats.

See every vulnerability recorded for riyanto-poke10 →

Share this vulnerability

FAQ

Riyanto-poke10 is an npm package that is part of a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.

The vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package.json and floods the npm registry with unwanted packages.

You should uninstall the package immediately using 'npm uninstall riyanto-poke10' and review your project for any other potentially compromised packages.

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

Yes, tools like Vulert can help you monitor and alert you to open-source vulnerabilities in your software, ensuring that you stay informed about potential risks.

How To Fix

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

npm uninstall riyanto-poke10

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