Malicious Code Injection in riyanto-poke3 Package

riyanto-poke3 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165136: Malicious code in riyanto-poke3 (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-poke3 package is part of the npm ecosystem, often utilized for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages that flood the npm registry. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names.

Vulnerability Detail

The vulnerability in the riyanto-poke3 package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall riyanto-poke3

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-poke3 package until a fixed version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The riyanto-poke3 package has been identified as containing malicious code that can compromise the integrity of the npm ecosystem. It is crucial for developers to update or remove this package to protect their applications from potential security risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for riyanto-poke3 →

Share this vulnerability

FAQ

The riyanto-poke3 package is an npm package that is part of a token reward campaign, which has been found to contain malicious code.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application if you use the affected package.

You should update the package to the latest patched version or remove it from your project until a fix is available.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the 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 needing to sign up.

How To Fix

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

npm uninstall riyanto-poke3

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