Malicious Code Detected in prayoga-poke46: A Threat to npm Users

prayoga-poke46 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164545: Malicious code in prayoga-poke46 (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

prayoga-poke46 is an npm package that is part of a larger campaign aimed at exploiting the npm ecosystem for token rewards. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing numerous derivative packages with random names. Its primary functionality is to serve as a tool for developers, but it has been compromised to serve malicious purposes.

Vulnerability Detail

The vulnerability in prayoga-poke46 originates from its involvement in the tea.xyz token reward campaign. This package contains scripts that automatically modify package.json files to remove private flags, alter version numbers, and create random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may lead to security breaches and loss of reputation.

How To Fix

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

npm uninstall prayoga-poke46

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 prayoga-poke46 and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The prayoga-poke46 package has been identified as malicious, posing significant risks to developers using npm. It is essential to remove this package and monitor your projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for prayoga-poke46 →

Share this vulnerability

FAQ

prayoga-poke46 is an npm package that has been compromised to participate in a malicious campaign aimed at inflating developer reputation scores for token rewards.

The vulnerability allows malicious scripts to modify your package.json file, potentially leading to the use of compromised packages and security risks.

You should remove the prayoga-poke46 package from your project immediately and monitor for any updates or patches.

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. Visit https://vulert.com to learn more.

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 prayoga-poke46

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