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

riyanto-poke38 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165145: Malicious code in riyanto-poke38 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The riyanto-poke38 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of such packages is to manipulate developer reputation scores through automated publishing scripts, thereby compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in riyanto-poke38 originates from its design to include malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for users who install these packages, and a degradation of trust in the npm ecosystem as a whole.

How To Fix

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

npm uninstall riyanto-poke38

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, avoid using the riyanto-poke38 package and consider using alternative packages that offer similar functionality without the associated risks. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The riyanto-poke38 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package integrity. It is crucial for developers to remain vigilant, uninstall affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for riyanto-poke38 →

Share this vulnerability

FAQ

Riyanto-poke38 is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores through automated publishing.

The malicious code can alter your package.json file, leading to potential security risks and the pollution of the npm registry with unwanted packages.

You should uninstall the package immediately using 'npm uninstall riyanto-poke38' and check your project for any other affected packages.

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

Yes, consider using other reputable packages that provide similar functionality without the associated risks of malicious code.

How To Fix

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

npm uninstall riyanto-poke38

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