Malicious Code Vulnerability in prayoga-poke11: Exploitation of npm Registry

prayoga-poke11 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164507: Malicious code in prayoga-poke11 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

prayoga-poke11 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the ecosystem, but it has been compromised to include malicious code. The vulnerability allows for the automatic generation and publication of derivative packages, which can lead to reputation inflation and registry pollution.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with fake packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to significant security risks, including the potential for dependency confusion and supply chain attacks. The affected package has been identified as part of a broader trend of malicious npm packages that exploit developer trust and reputation.

How To Fix

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

npm uninstall prayoga-poke11

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 measure, you can avoid using the prayoga-poke11 package and monitor your dependencies for any unauthorized changes. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The prayoga-poke11 package has been identified as containing malicious code that exploits the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain the security of their applications. Utilizing tools like Vulert can aid in identifying and managing vulnerabilities effectively.

See every vulnerability recorded for prayoga-poke11 →

Share this vulnerability

FAQ

prayoga-poke11 is an npm package that was part of a token reward campaign but has been compromised to include malicious code.

The vulnerability can lead to the automatic generation of malicious packages, which may compromise your application's security and integrity.

You should remove the prayoga-poke11 package from your project and monitor your dependencies for any unauthorized changes.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall prayoga-poke11

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