- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 4
- 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 1 day
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
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
Whilst we may, at our sole discretion, offer a monetary reward or "bug bounty" to the security researcher for responsibly disclosing a valid vulnerability
- Response
-
Within 1 days
we aim to respond within 24 hours of receipt of your initial report.
- Safe harbor
-
Full
Any activities conducted in a manner consistent with these guidelines will be considered authorized conduct and we will not initiate legal action against you.
- Hall of fame
-
Yes
we will happily acknowledge and credit the researcher accordingly on confirmation of a valid report.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
4 assets you may test, 4 excluded.
Domains 4
- mid.as
- midas.network
- pentest.mid.as
- security.midas.network
Out of scope (4)
- All other *.mid.as sub domains
- Any of our customer's MIDAS systems.
- Vulnerabilities in 3rd party components or services
- *.mid.as
Rules
What the policy asks of you, and the bug types it won't reward, quoted from MIDAS's policy. "We" in these lines means the program, not this site.
While testing
-
Ensure that any testing is legal and authorized, and within the Scope set out above.
-
Respect the privacy of others, including our customers.
-
Not engage in activities which may impact our customers ability to access our services, including but not limited to DoS/DDoS-style attacks.
-
Refrain from spamming or social engineering activities.
-
Not make physical attempts against MIDAS property or data centers.
-
Make reasonable efforts to contact our security team .
-
Not demand payment or other rewards as a condition of providing information on security vulnerabilities or other such issues, or in exchange for not publishing the details or reporting them to industry regulators.
Not accepted
-
Vulnerabilities in 3rd party components or services
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
− Any of our customer's MIDAS systems
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.