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

riyanto-poke25 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165131: Malicious code in riyanto-poke25 (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 riyanto-poke25 package is part of a larger ecosystem within npm, primarily used for various JavaScript applications. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages. The vulnerability stems from its design, which allows for the automatic generation and publication of packages with altered metadata, making it susceptible to exploitation.

Vulnerability Detail

The vulnerability in riyanto-poke25 originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially affecting other developers and users by introducing untrusted code into their projects.

How To Fix

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

npm uninstall riyanto-poke25

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-poke25 package and consider alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your project's dependencies are regularly audited for vulnerabilities using tools like npm audit.

Conclusion

The riyanto-poke25 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with untrusted packages. 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-poke25 →

Share this vulnerability

FAQ

The riyanto-poke25 package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the introduction of untrusted code into your project, potentially compromising its security and integrity.

You should remove the riyanto-poke25 package from your project and monitor for any updates or patches that may address the vulnerability.

You can use tools like npm audit to check for vulnerabilities in your project's dependencies. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

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

How To Fix

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

npm uninstall riyanto-poke25

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