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

riyanto-poke49 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165157: Malicious code in riyanto-poke49 (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-poke49 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms to generate and publish harmful derivatives, thereby compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability in riyanto-poke49 originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that automatically modify the package.json file to remove private flags, alter version numbers, and create random package names. The scripts continuously republish these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these compromised packages. The ramifications include loss of developer reputation, exposure to malicious code, and potential exploitation of applications relying on these packages.

How To Fix

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

npm uninstall riyanto-poke49

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-poke49 package and look for alternative packages that provide similar functionality without the associated risks. Regularly check your package-lock.json file for any dependencies that may introduce vulnerabilities.

Conclusion

The riyanto-poke49 package poses a significant threat to npm users due to its malicious code designed to manipulate package data and pollute the npm registry. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for riyanto-poke49 →

Share this vulnerability

FAQ

The riyanto-poke49 package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and functionality.

You should immediately uninstall the package using npm uninstall riyanto-poke49 and audit your project for any other vulnerable dependencies.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall riyanto-poke49

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