Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Privy (Bounty)

By Privy Bug bounty on HackerOne privy.io

Accepting reports
Go to program Website
Top reward
$10,000
Top severity paid
Critical
Assets in scope
12
Public CVEs
0
Last change

At a glance

What to know before you start testing.

Pays up to $10,000
for critical bugs.
Report on HackerOne
Submit through the program page.
Replies within 3 days
As the policy promises.
No public write-ups
Keep findings private.

Rewards

What HackerOne lists as the payout for each severity.

Severity Reward
Critical $10,000 from $5,000
High $5,000 from $2,500
Medium $2,500 from $500
Low $500 from $100
Response
Within 3 days | First Response | 3 days |

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

12 assets you may test, 4 excluded.

Web 5

  • api.privy.io Critical
  • auth.privy.io Critical
  • dashboard.privy.io Critical
  • home.privy.io Critical
  • recovery.privy.io Critical

Source code 1

  • https://www.npmjs.com/package/@privy-io/react-auth Critical

Products and areas 6

  • https://www.npmjs.com/package/@privy-io/cross-app-connect Critical
  • https://www.npmjs.com/package/@privy-io/cross-app-provider Critical
  • https://www.npmjs.com/package/@privy-io/expo Critical
  • https://www.npmjs.com/package/@privy-io/js-sdk-core Critical
  • https://www.npmjs.com/package/@privy-io/wagmi Critical
  • @privy-io controlled namespace dependencies Critical
Out of scope (4)
  • blog.privy.io
  • demo.privy.io
  • docs.privy.io
  • privy.io

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Privy (Bounty) (via HackerOne)'s policy. "We" in these lines means the program, not this site.

While testing

  • Please provide detailed reports with reproducible steps.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Social engineering (e.g. phishing, vishing, smishing) is strictly prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Only interact with accounts you own or with explicit permission of the account holder.
  • Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
  • Any activity that could lead to the disruption of our service (DoS, DDoS) or any volumetric based exploit.
  • Social engineering of customers or end users is prohibited under any circumstance.

Not accepted

  • Race conditions used to add additional members, apps or other soft-limited features of your account
  • Bypassing adding credit card information when moving applications to production
  • Viewing publicly accessible configurations with the App ID
  • CORS headers allowing any domain
  • OAuth redirect allowing any domain
  • Adding resources that are difficult for other members of your team to remove
  • Administrative accounts being able to remove other administrators
  • Viewing Application, embedded wallet and other *public* configurations
  • Expiry of sessions (these use JWTs with a low timeout)
  • Public JWKS endpoints
  • Using third party auth to create an account (with the except of Google OAuth)
  • Bypassing PNG upload to upload an image of another type
  • Bypasses of feature gating or billing controls
  • Attacks requiring physical access to a user's device
  • Attacks requiring disabling Man In The Middle (MITM) protections.
  • Attacks only affecting obsolete browsers or operating systems.
  • Missing best practices (SSL/TLS configuration, Content Security Policies, cookie flags, tabnabbing, autocomplete attribute, email SPF/DKIM/DMARC records)
  • Clickjacking or Cross-Site Request Forgery (CSRF) on unauthenticated pages / forms with no sensitive actions.
  • Open redirects, unless a significant impact can be demonstrated.
  • Self-exploitation (self XSS, self denial-of-service, etc.)
  • Missing validation of `postMessage` origin when the app into which the SDK is installed does not have a Content Security Policy in place.
  • Missing `postMessage` origin validation in out client side SDKs
  • Content spoofing, text injection and CSV injection
  • Software version disclosure / Banner identification issues / Descriptive error messages or stack traces.
  • Issues that require unlikely user interaction by the victim.

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 31 minutes ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Scope added

    https://www.npmjs.com/package/@privy-io/cross-app-connect

  2. Scope added

    https://www.npmjs.com/package/@privy-io/cross-app-provider

  3. Scope added

    https://www.npmjs.com/package/@privy-io/expo

  4. Scope added

    https://www.npmjs.com/package/@privy-io/js-sdk-core

  5. Scope added

    https://www.npmjs.com/package/@privy-io/react-auth

  6. Scope added

    https://www.npmjs.com/package/@privy-io/wagmi

  7. Scope added

    @privy-io controlled namespace dependencies

  8. Scope added

    api.privy.io

  9. Scope added

    home.privy.io

  10. Scope added

    recovery.privy.io

  11. Scope added

    blog.privy.io (out of scope)

  12. Scope added

    demo.privy.io (out of scope)

  13. Scope added

    docs.privy.io (out of scope)

  14. Scope added

    privy.io (out of scope)

  15. Scope added

    auth.privy.io

  16. Scope added

    dashboard.privy.io

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

IMPORTANT

** To be eligible for bounties, please create your Privy account name with the string "(BBP)" (e.g., in the "Project or company name" field) so we can associate your account with any submissions to the program. **

Overview

Privy believes that working with security researchers all over the world is essential to building a secure product. If you believe you have identified a vulnerability with our product, please reach out. We will do everything to resolve the issue promptly and collaborate with you actively.

** Privy is now available in GA. You can test most flows on demo.privy.io, and you can use https://dashboard.privy.io/ to sign up and get your API keys to start. Please make sure to include HackerOne in your organization name, and use your hacker email alias ([email protected]) when signing up. Note that this is not a staging environment.**

Response Targets

Privy will work to meet the following SLAs for hackers participating in our program:

Type of Response SLA in business days
First Response 3 days
Time to Triage 7 days
Time to Bounty 15 days
Time to Resolution Depends on severity and complexity

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

  • Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
  • We may ask you for help to confirm the issue has been properly resolved.
  • Follow HackerOne's disclosure guidelines.

Program Rules

  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Social engineering (e.g. phishing, vishing, smishing) is strictly prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
  • When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug.

Digging in

Privy is a developer tool, an onboarding solution for developers working with decentralized systems. It helps developers easily onboard all of their users whether they are new to the crypto space or very familiar with it. Privy has the following core product surfaces:

  • Wallet connectors that enable crypto-native users to connect their third-party wallets to customer apps and help developers manage wallet state for their users.
  • Embedded wallets that enable developers to easily provision self-custodial wallets for users without them.
  • An authentication system underlying both above systems that authenticate users and manage user lifecycles through an app.
  • An API developers can call to access user data, as well as a console consuming the same API.
  • The latest OpenAPI specification for our public API is available here: https://dashboard.privy.io/api/v1/openapi.json

Learn more by going to https://docs.privy.io and please reach out to [email protected] with questions.

Out of scope vulnerabilities

  • The Privy blog (blog.privy.io), website (privy.io), docs (docs.privy.io), and demo (demo.privy.io) are all out of scope. Generally, *.privy.io is not in scope, only designated resources are in scope. The demo is a useful environment to test application flows just the same, demo-specific vulnerabilities will not be considered (rather than Privy vulnerabilities surfaced through the demo site).

The following issues are considered out of scope:

  • Race conditions used to add additional members, apps or other soft-limited features of your account
  • Bypassing adding credit card information when moving applications to production (unless you can also show you can move out of the free tier into enterprise!)
  • Viewing publicly accessible configurations with the App ID ( eg. https://auth.privy.io/api/v1/apps/cm5wmef9k04gwpo79ttzehvk5 )
  • CORS headers allowing any domain
  • OAuth redirect allowing any domain (unless you can show bypassing the OAuth configured domains ( https://docs.privy.io/recipes/react/allowed-domains#allowed-oauth-redirect-urls )
  • Adding resources that are difficult for other members of your team to remove (ie long names, special characters, etc)
  • Administrative accounts being able to remove other administrators
  • Viewing Application, embedded wallet and other public configurations
  • Expiry of sessions (these use JWTs with a low timeout)
  • Public JWKS endpoints
  • Using third party auth to create an account (with the except of Google OAuth), these will create separate accounts and are the expected behaviour
  • Bypassing PNG upload to upload an image of another type
  • Bypasses of feature gating or billing controls (e.g. accessing paid/enterprise features without the required subscription), as these are intentionally implemented as soft boundaries. This includes but is not limited to webhook functionality and third-party authentication features.
  • Attacks requiring physical access to a user's device, unless the device is in-scope and explicitly hardened against physical access.
  • Attacks requiring disabling Man In The Middle (MITM) protections.
  • Attacks only affecting obsolete browsers or operating systems.
  • Missing best practices (SSL/TLS configuration, Content Security Policies, cookie flags, tabnabbing, autocomplete attribute, email SPF/DKIM/DMARC records), unless a significant impact can be demonstrated.
  • Clickjacking or Cross-Site Request Forgery (CSRF) on unauthenticated pages / forms with no sensitive actions.
  • Open redirects, unless a significant impact can be demonstrated.
  • Self-exploitation (self XSS, self denial-of-service, etc.), unless a method to attack a different user can be demonstrated. This INCLUDES being able to target your own team.
  • Missing validation of postMessage origin when the app into which the SDK is installed does not have a Content Security Policy in place.
  • Missing postMessage origin validation in out client side SDKs such as cross-app-connect, cross-app-provider, react-auth, js-sdk-core etc.
  • Content spoofing, text injection and CSV injection, unless a significant impact can be demonstrated.
  • Software version disclosure / Banner identification issues / Descriptive error messages or stack traces.
  • Issues that require unlikely user interaction by the victim.
  • Perceived security weaknesses without evidence of the ability to demonstrate impact.
  • Developer slack invite

Other exclusions

  • Any activity carried out on a Privy customer site, domain or app is strictly prohibited and will not be considered as part of this program.
  • Any activity that could lead to the disruption of our service (DoS, DDoS) or any volumetric based exploit.
  • Social engineering of customers or end users is prohibited under any circumstance.
  • Social engineering of Privy employees or contractors, unless explicitly authorized.
  • Attacks against our physical facilities, unless explicitly authorized.

Thank you for helping keep Privy and our users safe -- we're excited to work with you.