Polygon Technology
By Polygon Labs Bug bounty on HackerOne polygon.technology
- Top reward
- $20,000
- Top severity paid
- Critical
- Assets in scope
- 8
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $20,000
- for critical bugs.
- Report on HackerOne
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 2 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$20,000 |
| High |
|
$5,000 |
| Medium |
|
$2,000 |
| Low |
|
$250 |
- Response
-
Within 2 days
| First Response | 2 days |
- Safe harbor
-
Full
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
8 assets you may test, 6 excluded.
APIs 4
- api-gateway.polygon.technology Critical
- api-polygon-tokens.polygon.technology High
- faucet-api.polygon.technology High
- gasstation.polygon.technology High
Web 4
- faucet.polygon.technology Critical
- portal.polygon.technology Critical
- staking-api.polygon.technology Critical
- staking.polygon.technology Critical
Out of scope (6)
- https://github.com/0xPolygon/heimdall-v2
- https://github.com/maticnetwork/bor
- https://github.com/maticnetwork/contracts
- https://github.com/maticnetwork/heimdall
- https://github.com/maticnetwork/matic-cli
- *.matic.network
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Polygon Technology (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
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 prohibited.
-
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
-
Ask the program team before submitting vulnerabilities on unscoped subdomains.
-
Only interact with accounts you own or with the explicit permission of the account holder.
Not accepted
-
Any issues already reported publicly on GitHub.
-
Previously known vulnerable libraries without a working Proof of Concept.
-
Sections of the code intended to be used for testing purposes.
-
Clickjacking on pages with no sensitive actions.
-
Attacks requiring MITM or physical access to a user's device.
-
Missing best practices in SSL/TLS configuration.
-
Any activity that could lead to the disruption of our service (DoS).
-
Issues that require unlikely user interaction.
-
Privacy-related vulnerabilities (e.g., leaking your address to other peers on the network).
-
Open redirect - unless an additional security impact can be demonstrated.
-
Rate limiting or bruteforce issues on non-authentication endpoints.
-
Missing best practices in Content Security Policy.
-
Missing HttpOnly or Secure flags on cookies.
-
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.).
-
Vulnerabilities that depend solely on third-party services that we utilize and might be subject to their bug bounty program.
-
Broken social media links not directly related to Polygon Labs
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 1 hour 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.
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.
Polygon Labs Bug Bounty Program
Polygon Labs looks forward to working with the security community to find security vulnerabilities to keep users safe.
Response Targets
Polygon Labs will make a best effort to meet the following response targets for hackers participating in our program:
| Type of Response | SLA in Business Days |
|---|---|
| First Response | 2 days |
| Time to Triage | 2 days |
| Time to Bounty | 14 days |
| Time to Resolution | Depends on severity and complexity |
Disclosure Policy
As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization. Follow HackerOne's disclosure guidelines.
Program Rules
- 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 prohibited.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
- Ask the program team before submitting vulnerabilities on unscoped subdomains.
- Only interact with accounts you own or with the explicit permission of the account holder.
Rewards
Our rewards are based on severity per CVSS (the Common Vulnerability Scoring Standard). Please note these are general guidelines, and reward decisions are up to the discretion of Polygon Labs.
Out-of-Scope Vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
- Any issues already reported publicly on GitHub.
- Previously known vulnerable libraries without a working Proof of Concept.
- Sections of the code intended to be used for testing purposes.
- Clickjacking on pages with no sensitive actions.
- Attacks requiring MITM or physical access to a user's device.
- Previously known vulnerable libraries without a working Proof of Concept.
- Missing best practices in SSL/TLS configuration.
- Any activity that could lead to the disruption of our service (DoS).
- Issues that require unlikely user interaction.
- Privacy-related vulnerabilities (e.g., leaking your address to other peers on the network).
- Open redirect - unless an additional security impact can be demonstrated.
- Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case-by-case basis.
- Rate limiting or bruteforce issues on non-authentication endpoints.
- Missing best practices in Content Security Policy.
- Missing HttpOnly or Secure flags on cookies.
- Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.).
- Vulnerabilities that depend solely on third-party services that we utilize and might be subject to their bug bounty program.
- Broken social media links not directly related to Polygon Labs (f.e solution providers listed on ecosystem.polygon.technology are considered as OUT of scope)
Safe Harbor
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will, within our sole discretion, endeavor to make it known that your actions were conducted in compliance with this policy.
Program Changes
We reserve the right to modify the Bug Bounty Program or cancel the Bug Bounty Program at any time.
Thank you for helping keep users safe!