Malicious Code Injection in riyanto-poke36: A Threat to npm Packages

riyanto-poke36 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165143: Malicious code in riyanto-poke36 (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 Penetration testing for web, API and mobile 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-poke36 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. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in riyanto-poke36 stems from its inclusion in a campaign that generates and publishes derivative packages with randomized names. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants to pollute the npm registry. This can lead to a compromised development environment, where developers may unknowingly use malicious packages, risking their applications and data.

How To Fix

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

npm uninstall riyanto-poke36

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-poke36 package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The riyanto-poke36 package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for riyanto-poke36 →

Share this vulnerability

FAQ

The riyanto-poke36 package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

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

You should uninstall the riyanto-poke36 package immediately using the command npm uninstall riyanto-poke36 and review your project for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation. You can also check your application against known vulnerabilities using the Vulert playground.

Yes, consider using well-established and trusted packages that provide similar functionalities without the risks associated with riyanto-poke36.

How To Fix

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

npm uninstall riyanto-poke36

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