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

prayoga-poke28 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164525: Malicious code in prayoga-poke28 (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-poke28 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm ecosystem. However, it has been identified as a malicious package that employs scripts to manipulate its own metadata and publish derivative versions, thereby compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability in prayoga-poke28 originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random names, which can lead to reputation inflation for developers and pollution of the npm registry. The ramifications include potential security risks for users who unknowingly install these compromised packages, as they may introduce vulnerabilities into their applications.

How To Fix

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

npm uninstall prayoga-poke28

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-poke28 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files to ensure no malicious packages are included.

Conclusion

The prayoga-poke28 package poses a significant threat due to its malicious code that modifies package metadata and floods the npm registry with compromised versions. It is essential to remove this package and monitor your dependencies to maintain the security of your applications.

See every vulnerability recorded for prayoga-poke28 →

Share this vulnerability

FAQ

prayoga-poke28 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your application.

You should uninstall prayoga-poke28 immediately using the command npm uninstall prayoga-poke28.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Yes, tools like Vulert can help you monitor and alert for vulnerabilities in your open-source dependencies without requiring access to your code.

How To Fix

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

npm uninstall prayoga-poke28

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