Skip to content

Bug bounty program

Platform
HackerOne
Bounties
Pays
Assets in scope
32
Disclosed reports
20
Subdomains
22,831

Most upvoted reports20

All reports
Most upvoted reports of Grab
ReportWeaknessDisclosedBountyVotes
[Grab Android/iOS] Insecure deeplink leads to sensitive information disclosureAnalysed#401793Cross-site Scripting2019-03-15–552
www.drivegrab.com SQL injectionAnalysed#273946SQL Injection2017-11-17$4,500205
Leaking sensitive information on Github lead full access to all Grab Slack channelsAnalysed#397527Information Disclosure2018-09-11–145
Subdomain Takeover Via Insecure CloudFront Distribution cdn.grab.comAnalysed#352869Memory Corruption2021-02-24$1,000142
Leak ██████████ information in real time through API requestAnalysed#307050Authentication2018-02-03$3,000103
Access Grab_Road BigData Database via Open Presto coordinatorAnalysed#266766Information Disclosure2017-11-30$5,00097
Authorization bypass using login by phone option+horizontal escalation possible on Grab Android AppAnalysed#205000Authentication2017-09-14–68
Blind stored xss [parcel.grab.com] > name parameterAnalysed#251224Cross-site Scripting2017-09-14$75050
Two-factor authentication bypass on Grab Android AppAnalysed#202425Authentication2017-09-12–46
Git repository foundAnalysed#248693Information Disclosure2017-08-13–43

Subdomains22,831

Subdomains of Grab
NameScopeFirst seen
campaigns.myteksi.comIn scope2026-11-14
cashier.myteksi.comIn scope2026-11-14
cashier-staging.myteksi.comstagingIn scope2026-11-14
dotino.myteksi.comIn scope2026-11-14
gamma.myteksi.comIn scope2026-11-14
jiangchengzuqiuwangkaitouqu.myteksi.comIn scope2026-11-14
newsletter.myteksi.comIn scope2026-11-14
o1.newsletter.myteksi.comIn scope2026-11-14
sendy.myteksi.comIn scope2026-11-14
web.myteksi.comIn scope2026-11-14
www.myteksi.comIn scope2026-11-14
zendesk1.myteksi.comIn scope2026-11-14
zendesk2.myteksi.comIn scope2026-11-14
zendesk3.myteksi.comIn scope2026-11-14
zendesk4.myteksi.comIn scope2026-11-14

2,567 names are covered by the program's own scope; 0 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.

A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-15.