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

riyanto-poke41 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165149: Malicious code in riyanto-poke41 (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-poke41 is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages that flood the npm registry. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in riyanto-poke41 originates from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also exposes users to potential security risks, as they may inadvertently install these malicious packages.

How To Fix

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

npm uninstall riyanto-poke41

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-poke41 package and monitor your package-lock.json file for any unauthorized changes. If you suspect that your project has been affected, consider using tools like Vulert to scan your project for vulnerabilities. You can access Vulert's playground at https://vulert.com/scanner to check if your application is impacted without any signup.

Conclusion

The riyanto-poke41 package poses a significant threat to npm users due to its malicious code designed to manipulate package integrity. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for riyanto-poke41 →

Share this vulnerability

FAQ

Riyanto-poke41 is an npm package that has been identified as malicious, part of a campaign to manipulate developer reputation scores.

The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity.

You should uninstall the package immediately using the command 'npm uninstall riyanto-poke41' and check for any other compromised packages.

Regularly audit your dependencies, keep them updated, and use tools like Vulert to monitor for vulnerabilities in real-time.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. It provides real-time alerts without requiring code access.

How To Fix

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

npm uninstall riyanto-poke41

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