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

prayoga-poke35 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164533: Malicious code in prayoga-poke35 (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-poke35 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-poke35 originates from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The potential ramifications include the risk of developers unknowingly using compromised packages, leading to 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-poke35

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-poke35 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.

Conclusion

The prayoga-poke35 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with compromised packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for prayoga-poke35 →

Share this vulnerability

FAQ

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

The malicious code modifies package metadata and can lead to the installation of compromised packages, posing security risks to your application.

You can use Vulert, which monitors vulnerabilities in open-source packages. Visit Vulert Scanner to check your application without needing to sign up.

You should uninstall the package immediately using 'npm uninstall prayoga-poke35' and check for any other affected packages.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages.

How To Fix

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

npm uninstall prayoga-poke35

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