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

riyanto-poke81 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165193: Malicious code in riyanto-poke81 (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-poke81 is part of a series of malicious npm packages linked to the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating numerous derivative packages with randomized names. This behavior not only inflates developer reputation scores but also poses a significant risk to users by polluting the npm ecosystem.

Vulnerability Detail

The vulnerability in riyanto-poke81 stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This activity can compromise the integrity of the npm registry and potentially introduce harmful dependencies into projects that rely on this package.

How To Fix

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

npm uninstall riyanto-poke81

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

Conclusion

The riyanto-poke81 package poses a significant threat to npm users due to its malicious code that manipulates package metadata and floods the npm registry. It is essential to remove this package from your projects and monitor for any vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for riyanto-poke81 →

Share this vulnerability

FAQ

Riyanto-poke81 is an npm package that has been identified as malicious, designed to manipulate the npm registry and inflate developer reputation scores.

The vulnerability can lead to the introduction of harmful dependencies, compromising the security and integrity of your project.

You should uninstall the package immediately using 'npm uninstall riyanto-poke81' and check for any dependencies that may rely on it.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected 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-poke81

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