Malicious Code Injection in prayoga-poke50: A Threat to npm Users

prayoga-poke50 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164550: Malicious code in prayoga-poke50 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

prayoga-poke50 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm ecosystem, but it has been compromised to include malicious code. The vulnerability arises from the package's involvement in autopublishing scripts that generate and publish derivative packages with altered names and metadata, ultimately leading to the pollution of the npm registry.

Vulnerability Detail

The vulnerability in prayoga-poke50 originates from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants, which can inflate developer reputation scores fraudulently. This not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these tainted packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall prayoga-poke50

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 remove the prayoga-poke50 package from your project by executing the command: npm uninstall prayoga-poke50. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The prayoga-poke50 package poses a significant risk due to its malicious code injection vulnerability. It is essential for developers to take immediate action by updating or removing the package and to utilize monitoring tools like Vulert to safeguard their applications against future vulnerabilities.

See every vulnerability recorded for prayoga-poke50 →

Share this vulnerability

FAQ

prayoga-poke50 is an npm package that has been compromised to include malicious code as part of a token reward campaign.

The vulnerability can lead to the injection of malicious code, which may compromise the security of your application and the integrity of the npm registry.

You should uninstall the package immediately and monitor for any updates or patches that address the vulnerability.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for any 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 prayoga-poke50

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