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

riyanto-poke70 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165181: Malicious code in riyanto-poke70 (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-poke70 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign aimed at exploiting the npm registry by flooding it with derivative packages. The malicious nature of this package lies in its ability to manipulate package metadata and publish unauthorized versions, potentially harming developers' reputations and polluting the registry.

Vulnerability Detail

The vulnerability in riyanto-poke70 originates from its association with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through automated scripts. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential 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-poke70

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-poke70 package and monitor your project for any dependencies that may have been affected by this malicious package. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The riyanto-poke70 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and flooding the registry with unauthorized versions. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for riyanto-poke70 →

Share this vulnerability

FAQ

Riyanto-poke70 is an npm package that has been identified as part of a malicious campaign to exploit the npm registry by publishing unauthorized derivative packages.

This vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

You should immediately remove the riyanto-poke70 package from your project and check for any other affected dependencies.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time, alerting you to any issues without requiring code access.

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-poke70

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