hacktivity-check

To check for duplicate bug bounty reports on HackerOne, provide your program name and vulnerability description. The tool scrapes disclosed hacktivity reports and analyzes historical data to detect duplicate vulnerability patterns.

The best way to avoid duplicate vulnerability submissions is to scan historical disclosed reports before filing. This process matches your finding against existing data to prevent wasted submissions and protect your reputation.

Yes, you can detect duplicate vulnerability patterns using the HackerOne API, web search, and Playwright. These integrations perform comprehensive checks against historical disclosed reports to identify matching findings.

You assess the risk level of a duplicate finding by analyzing your vulnerability description against historical disclosed reports. The analysis generates a dupe risk level of HIGH, MEDIUM, LOW, or CLEAR to guide your submission.

If a similar vulnerability is already disclosed, you should evaluate the generated recommendation to submit, not submit, or differentiate your finding. This prevents wasted submissions and potential reputation damage from duplicates.

Yes, duplicate detection for HackerOne hacktivity works when you input the specific program name and a detailed finding description, such as Stored XSS in a user profile, to accurately scan for similar disclosed reports.