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

riyanto-poke19 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165124: Malicious code in riyanto-poke19 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package riyanto-poke19 is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

This vulnerability originates from the riyanto-poke19 package, which contains scripts that remove private flags from package.json, alter version numbers, and generate random package names. The malicious payload continuously republishes these variants, leading to a significant risk of registry pollution and potential exploitation by malicious actors. The impact includes compromised developer reputation and increased difficulty in managing legitimate packages within the npm ecosystem.

How To Fix

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

npm uninstall riyanto-poke19

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-poke19 package and monitor your project for any unintended dependencies that may have been introduced. Use the following command to check for outdated packages: 'npm outdated'.

Conclusion

The riyanto-poke19 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and republish variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for riyanto-poke19 →

Share this vulnerability

FAQ

The riyanto-poke19 package is a malicious npm package that is part of a campaign to inflate developer reputation scores through automated publishing of derivative packages.

This vulnerability can lead to registry pollution, making it difficult to manage legitimate packages and potentially compromising your project's integrity.

You should uninstall the riyanto-poke19 package immediately using 'npm uninstall riyanto-poke19' and review your project's dependencies for any other malicious packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can also check your application using the Vulert playground without any signup.

Yes, tools like Vulert can help you monitor and alert for vulnerabilities in your software without requiring access to the code or installation.

How To Fix

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

npm uninstall riyanto-poke19

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