Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Unrestricted access to Eureka server on ██████Analysed#304240 | Valid | Access Control | Medium | 2018-02-06 | $500 | 17 |
| Unrestricted access to https://██████.█████myteksi.net/Analysed#304386 | Valid | Access Control | Medium | 2018-02-12 | $250 | 23 |
| [growth.grab.com] Reflected XSS via Base64-encoded "q" param on "my.html" Valentine's micrositeAnalysed#320679 | Valid | Cross-site Scripting | Medium | 2018-03-02 | – | 29 |
| Registration enabled on ███grab.comAnalysed#318099 | Valid | Information Disclosure | Medium | 2018-02-28 | – | 32 |
| Leak ██████████ information in real time through API requestAnalysed#307050 | Valid | Authentication | High | 2018-02-03 | $3,000 | 103 |
| Leaking sensitive information on Github lead full access to all Grab Slack channelsAnalysed#397527 | Valid | Information Disclosure | Critical | 2018-09-11 | – | 145 |
Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report, where there is one, which can be wrong. Data as of 2026-11-15.