- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 10
- 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 by email
- [email protected]
- 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
Offering fair and timely rewards for eligible submissions.
- Hall of fame
-
Yes
Hall of Fame
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
10 assets you may test.
Android apps 3
- Halodoc for Customers
- Halodoc for Doctors
- Halodoc For Partners
Domains 3
- blogs.halodoc.io
- halodoc.com
- stage.halodoc.com
iOS apps 2
- Halodoc For Customers
- Halodoc for Doctors
Wildcard domains 2
- *.halodoc.com
- *.stage.halodoc.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Halodoc's policy. "We" in these lines means the program, not this site.
While testing
-
You must be the first reporter of a valid vulnerability, known vulnerabilities or submissions by researchers leading back to the same root cause will be classified as a duplicate finding.
-
All automated scanning must include “<your name>/security_researcher” in the user agent in order to be eligible for reward.
-
Denial of service attacks are prohibited.
-
Public or private disclosure of a vulnerability is prohibited.
-
Never attempt non-technical attacks including, but not limited to, social engineering, phishing or physical attacks.
-
You are not a current or former employee of Halodoc.
-
Do not leave any system in a more vulnerable state than you found it.
-
Do not use or interact with accounts you do not own.
-
Do not brute force credentials or guess credentials to gain access to systems or accounts.
Not accepted
-
HTTP 404 codes/pages or other HTTP non-200 codes/pages.
-
Fingerprinting/banner disclosure on common/public services.
-
Disclosure of known public files or directories (e.g., robots.txt).
-
Getting OTPs is expected behaviour for countries other than Indonesia.
-
Clickjacking on pages with no sensitive actions.
-
CSRF on forms that are available to anonymous users (e.g., login or contact form).
-
Logout / Login Cross-Site Request Forgery (logout CSRF).
-
No Captcha / Weak Captcha / Captcha Bypass.
-
Login or Forgot Password page brute force and account lockout not enforced.
-
WebServer Type disclosures.
-
Social engineering of our service desk, employees, or contractors.
-
Physical attacks against Halodoc's offices and data centers.
-
Error messages with non-sensitive data.
-
Non-application layer Denial of Service or DDoS.
-
Lack of HTTP Only / SECURE flag for cookies.
-
Username / email enumeration: via Login Page error message | via Forgot Password error message.
-
Missing HTTP security headers.
-
CSV Issues.
-
AV Scanning.
-
SSL Issues.
-
Service Rate Limiting.
-
User or Org enumeration.
-
Security Image Issues.
-
No or ineffective jailbreak / root detection.
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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.