Bug Bounty Platform Integrations¶
Emmu is designed to streamline the Bug Bounty lifecycle, automating the tedious process of tracking scopes, managing targets, and logging findings.
[!NOTE] The Problem: Bug bounty hunters waste hours manually copying target domains from platforms like HackerOne or Intigriti into their scanners, and then manually tracking which domains yielded findings.
The Solution: Emmu natively integrates with platform APIs. The AI can pull active program scopes, inject them into the Target Manager, and track findings per program autonomously.
1. Supported Platforms¶
Emmu currently provides native MCP-like tools for the following platforms via core/emmu/tools.py:
- HackerOne:
get_hackerone_programs,get_hackerone_program_details - Intigriti:
get_intigriti_programs,get_intigriti_program_details
These tools allow the AI to authenticate (using tokens provided in .env) and query your active, invited, or public programs.
2. The Automation Pipeline¶
By combining Platform Integrations with Emmu's Target Manager, the AI can perform End-to-End Bounty Hunting:
Step 1: Scope Extraction¶
You instruct Emmu: "Get my HackerOne programs and find the scope for Program X."
Emmu uses get_hackerone_program_details to fetch all in-scope wildcard domains and binaries.
Step 2: Target Initialization¶
The AI uses start_target_scan or start_mobile_scan to push the extracted scopes directly into the Emmu scanning pipeline. The target is tagged with the program_name and source (e.g., hackerone).
Step 3: Finding Allocation¶
When the emmu-exploit specialist confirms a vulnerability, it uses add_target_finding. Emmu's database automatically associates this finding with the specific Bug Bounty program.
You can later ask the AI: "Summarize all findings for HackerOne Program X," and it will retrieve the exact reports, ready for submission.
3. Configuration Setup¶
To enable these features, ensure your .env file is populated with your platform credentials: