Bug bounty program
EV
Equifax-vdp
Most upvoted reports7
| Report | Weakness | Disclosed | Bounty | Votes |
|---|---|---|---|---|
| Important information leaked on Github#649322 | Authentication | 2019-08-22 | – | 98 |
| reflected XSS in [www.equifax.com]#1818163 | Cross-site Scripting | 2023-04-23 | – | 47 |
| Subdomain takeover at http://test.www.midigator.com#1718371 | Access Control | 2022-11-12 | – | 32 |
| Open SonarQube instance leaking internal source code#947946 | Information Disclosure | 2020-09-03 | – | 20 |
| reflected XSS in [www.equifax.com]#1818172 | Cross-site Scripting | 2023-04-23 | – | 19 |
| Information Leak (Github)#694931 | No weakness recorded | 2020-04-09 | – | 17 |
| RXSS on https://equifax.gr8people.com on Password Reset page in the username parameter#1463638 | Cross-site Scripting | 2022-03-09 | – | 6 |
Subdomains55,670
| Name | Scope | First seen |
|---|---|---|
| api-git-status.github.comapi, git, monitoring | Not in the scope | 2026-11-14 |
| status.assets-cdn.github.commonitoring | Not in the scope | 2026-11-14 |
| metrics.classroom.github.commonitoring | Not in the scope | 2026-11-14 |
| metrics.education.github.commonitoring | Not in the scope | 2026-11-14 |
| elk.github.commonitoring | Not in the scope | 2026-11-14 |
| status.gist.github.commonitoring | Not in the scope | 2026-11-14 |
| monitoring.gitops-with-tanzu.github.commonitoring | Not in the scope | 2026-11-14 |
| grafana.github.commonitoring | Not in the scope | 2026-11-14 |
| grafana-delivery-bot.github.commonitoring | Not in the scope | 2026-11-14 |
| metrics.help.github.commonitoring | Not in the scope | 2026-11-14 |
| metrics.jobs.github.commonitoring | Not in the scope | 2026-11-14 |
| metrics.lab.github.commonitoring | Not in the scope | 2026-11-14 |
| logging.github.commonitoring | Not in the scope | 2026-11-14 |
| logs.github.commonitoring | Not in the scope | 2026-11-14 |
| metrics.github.commonitoring | Not in the scope | 2026-11-14 |
| monitor.github.commonitoring | Not in the scope | 2026-11-14 |
| www.monitor.github.commonitoring | Not in the scope | 2026-11-14 |
| monitor1.github.commonitoring | Not in the scope | 2026-11-14 |
| monitor2.github.commonitoring | Not in the scope | 2026-11-14 |
| monitor3.github.commonitoring | Not in the scope | 2026-11-14 |
| monitoring.github.commonitoring | Not in the scope | 2026-11-14 |
| www.monitoring.github.commonitoring | Not in the scope | 2026-11-14 |
| monitoring2.github.commonitoring | Not in the scope | 2026-11-14 |
| mozilla-metrics.github.commonitoring | Not in the scope | 2026-11-14 |
| oncall-status.mtougeron.github.commonitoring | Not in the scope | 2026-11-14 |
| nagios.github.commonitoring | Not in the scope | 2026-11-14 |
| nagios2.github.commonitoring | Not in the scope | 2026-11-14 |
| prometheus.github.commonitoring | Not in the scope | 2026-11-14 |
| nagios1-ext.rs.github.commonitoring | Not in the scope | 2026-11-14 |
| sentry.github.commonitoring | Not in the scope | 2026-11-14 |
| splunk.github.commonitoring | Not in the scope | 2026-11-14 |
| sentry.sr.github.commonitoring | Not in the scope | 2026-11-14 |
| clientkeys.sentry.sr.github.commonitoring | Not in the scope | 2026-11-14 |
| projects.sentry.sr.github.commonitoring | Not in the scope | 2026-11-14 |
| teams.sentry.sr.github.commonitoring | Not in the scope | 2026-11-14 |
| status.github.commonitoring | Not in the scope | 2026-11-14 |
| www.status.github.commonitoring | Not in the scope | 2026-11-14 |
| x1e.metrics.updatemetricsresponseb0z.github.commonitoring | Not in the scope | 2026-11-14 |
| zabbix.github.commonitoring | Not in the scope | 2026-11-14 |
| www.zabbix.github.commonitoring | Not in the scope | 2026-11-14 |
| zabbix2.github.commonitoring | Not in the scope | 2026-11-14 |
0 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-14.