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

prayoga-poke1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

prayoga-poke1 is an npm package that appears to be part of a token reward campaign associated with tea.xyz. This package is designed to facilitate the distribution of rewards through the npm ecosystem. However, it has been identified as containing malicious scripts that can compromise the integrity of the npm registry and inflate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in prayoga-poke1 stems from its inclusion in a malicious campaign that utilizes scripts (such as auto.js, autopublish.js) to automatically generate and publish numerous derivative packages with randomized names. This behavior modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been flagged by security tools like Amazon Inspector.

How To Fix

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

npm uninstall prayoga-poke1

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 prevent the installation of prayoga-poke1 by using npm's package-lock.json to monitor dependencies. You can also use the following command to uninstall the package: npm uninstall prayoga-poke1.

Conclusion

The prayoga-poke1 package poses a significant risk to npm users due to its malicious code designed to manipulate the npm registry. It is essential to take immediate action by removing the package and monitoring your project for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for prayoga-poke1 →

Share this vulnerability

FAQ

prayoga-poke1 is an npm package that is part of a token reward campaign, which has been identified as containing malicious code.

The vulnerability can lead to the automatic generation of malicious packages, compromising the integrity of your project and the npm registry.

You should uninstall the package immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall prayoga-poke1

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