Malicious Code Injection in prayoga-poke45: A Threat to npm Ecosystem

prayoga-poke45 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

prayoga-poke45 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards through various npm packages. However, it has been identified as containing malicious code that compromises the integrity of the npm registry by generating and publishing derivative packages with altered metadata.

Vulnerability Detail

The vulnerability in prayoga-poke45 originates from its association with a malicious campaign that aims to inflate developer reputation scores for token rewards. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers and users relying on these packages.

How To Fix

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

npm uninstall prayoga-poke45

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 workaround, you can avoid using the prayoga-poke45 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your project's dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The prayoga-poke45 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your project and monitor your dependencies for vulnerabilities to maintain the security and integrity of your applications.

See every vulnerability recorded for prayoga-poke45 →

Share this vulnerability

FAQ

prayoga-poke45 is an npm package that is part of a campaign to distribute token rewards but has been identified as containing malicious code.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.

You should uninstall the package immediately using 'npm uninstall prayoga-poke45' and audit your project for other vulnerabilities.

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

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-poke45

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