Malicious Code Injection in prayoga-poke49: A Threat to npm Packages

prayoga-poke49 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164548: Malicious code in prayoga-poke49 (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-poke49 is an npm package that is part of the tea.xyz token reward campaign. This package, like others in the campaign, is designed to generate and publish derivative packages with randomized names. It aims to inflate developer reputation scores for token rewards, but it also introduces significant security risks.

Vulnerability Detail

The vulnerability in prayoga-poke49 originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also compromises the integrity of the packages, potentially allowing for further exploitation by malicious actors.

How To Fix

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

npm uninstall prayoga-poke49

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-poke49 by adding it to your npm ignore list or by using a package manager that allows you to lock down dependencies more strictly.

Conclusion

The prayoga-poke49 package poses a significant security risk due to its malicious code that modifies package.json and republishing behavior. It is crucial to uninstall this package and monitor your project for vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for prayoga-poke49 →

Share this vulnerability

FAQ

prayoga-poke49 is an npm package involved in a token reward campaign that generates derivative packages to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies, potentially allowing for further exploitation.

You should uninstall the prayoga-poke49 package immediately and check your package-lock.json for any references to it.

Currently, there is no patched version available for prayoga-poke49. The best course of action is to uninstall the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. You can also check your application for vulnerabilities using the Vulert playground at Vulert Scanner.

How To Fix

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

npm uninstall prayoga-poke49

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