- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 21
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 5 days
- As the policy promises.
- No public write-ups
- Keep findings private.
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.
- Pays cash
-
Yes
If you're the first to report and it leads to a fix, we'll pay you a reward based on the criticality of the bug.
- Response
-
Within 5 days
The Swiggy security team will review the submission and revert back within 5 working days.
- Hall of fame
-
Yes
Swiggy would like to thank and show our gratitude to the following Security Researchers for contributing to making Swiggy Applications and Infrastructure more secure by responsibly disclosing security issues to us.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
21 assets you may test, 8 excluded.
Domains 17
- analytics.swiggy.com
- api.swiggy.com
- app.swiggy.com
- chkout.swiggy.com
- dash.swiggy.com
- disc.swiggy.com
- go.swiggy.com
- maps.swiggy.com
- picker.swiggy.com
- pos.swiggy.com
- profile.swiggy.com
- rms.swiggy.com
- spns.swiggy.com
- stores.swiggy.com
- swiggy.com
- swiggy.in
- www.swiggy.com
Android apps 2
- Android App
- https://play.google.com/store/apps/details?id=in.swiggy.android
iOS apps 2
- https://apps.apple.com/in/app/swiggy-food-instamart-dineout/id989540920
- iOS App
Out of scope (8)
- 3rd Party Applications
- Attacks using other users' accounts
- Automated tools or scripts
- Delivery App Endpoints
- DoS and DDoS testing (strictly prohibited)
- Physical security testing
- Social Engineering attacks
- Vendor Endpoints
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Swiggy's policy. "We" in these lines means the program, not this site.
While testing
-
The identified bug shall have to be reported to our security team by sending us a mail from your registered email address to [email protected] with subject prefix "Bug Bounty".
-
Bugs found on out-of-scope assets are ineligible for rewards.
-
DoS and DDoS testing (strictly prohibited)
-
Automated tools or scripts
-
Attacks using other users' accounts
-
Social Engineering attacks
-
Physical security testing
-
For a period of 5 years , the participant shall not publish, disseminate, or disclose any Confidential Information.
-
The participant shall use the information only in connection with the bug bounty program.
-
The participant shall not independently develop products or systems that compete with or are similar to those described in the Confidential Information.
Not accepted
-
IDOR for objects you have permission to
-
Duplicate / known issues
-
Rate limiting (non-severe)
-
Multiple reports for same vuln type
-
Clickjacking
-
Session cookies without http/secure flags
-
Social engineering attacks
-
Patches released within 30 days
-
Networking issues / industry standards
-
Password complexity
-
SPF or DMARC records
-
Gmail dot trick
-
Email bombs
-
Unsubscribing from marketing emails
-
Descriptive error messages (stack traces)
-
HTTP 404 / non-200 codes
-
Fingerprinting / banner disclosure
-
Known public files (robots.txt)
-
Cacheable SSL pages
-
SSL/TLS best practices
-
CSRF on anonymous forms (login, sign-up)
-
Logout CSRF
-
Weak CSRF in APIs
-
Forgot password brute force / no lockout
-
Lack of CAPTCHA
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.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope
− swiggy.com, − Android App, − iOS App
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.