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

WalletConnect

Bug bounty on Self-hosted walletconnect.com

Accepting reports Full safe harbor security.txt
Go to program Website
Top reward
Not published
Top severity paid
Not published
Assets in scope
6
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays cash
Amounts are not published; ask before you invest time.
Report through their form
walletconnect.network/security
Full safe harbor
Good-faith research is authorised; no legal action.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

The policy page has no reward table. Here is what it says, in its own words.

Safe harbor
Full If you have followed the instructions above, we will not take any legal action against you in regard to the report

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

6 assets you may test, 4 excluded.

Smart contracts 3

  • Smart contract vulnerabilities on Ethereum, Optimism, Base, and Solana
  • StakeWeight contract
  • token contracts

Domains 2

  • staking.walletconnect.network
  • walletconnect.network

Web 1

  • Frontend vulnerabilities on staking.walletconnect.network that could lead to wallet draining
Out of scope (4)
  • testnet deployments
  • third-party contract integrations we don't control
  • third-party Explorer links
  • https://github.com/WalletConnect/contracts/blob/main/DEPLOYMENT_ADDRESSES.md

Rules

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

While testing

  • Do not run automated scanners on our infrastructure or dashboard. If you wish to do this, contact us and we will set up a sandbox for you
  • Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data
  • Do not reveal the problem to others until it has been resolved
  • Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties
  • Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible

Not accepted

  • Gas optimizations without security impact
  • Best practices that don't demonstrate actual vulnerability
  • Issues requiring compromised private keys
  • Clickjacking on pages with no sensitive actions
  • Unauthenticated/logout/login CSRF
  • Attacks requiring MITM or physical access to a user's device
  • Any activity that could lead to the disruption of our service (DoS)
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Email spoofing
  • Missing DNSSEC, MTA-STS, CAA, CSP headers
  • Lack of Secure or HTTP only flag on non-sensitive cookies
  • Deadlinks

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 5 hours ago.

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

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.