bbscope

[!IMPORTANT]
This is bbscope v2!

Major changes include a new command structure and powerful new features.

Breaking Change: Subcommands have changed!

• Old: bbscope h1
• New: bbscope poll h1 (and similarly for bc, it, ywh, etc.)

New Features in v2:

• PostgreSQL Support (Optional): Store targets in a DB for persistence and querying.
• Changes Monitoring: Track new and removed targets over time (requires DB).
• AI Scope Normalization: Use LLMs to clean up messy scope strings.
• Docker Image: Ready-to-use image on GHCR.
• Centralized Polling: Poll multiple platforms in one go.
• Smart Scope Extraction: Use db get to fetch normalized targets by category (wildcards, cidrs, etc.).

bbscope is a powerful scope aggregation tool for bug bounty hunters, designed to fetch, store, and manage program scopes from HackerOne, Bugcrowd, Intigriti, YesWeHack, and Immunefi right from your command line.

Visit bbscope.com to explore an hourly-updated list of public scopes from all supported platforms, stats, and more!

Read the full documentation — installation, CLI reference, database guide, web deployment, library API, and more.

✨ Features

• Multi-Platform Support: Aggregates scopes from all major bug bounty platforms.
• PostgreSQL Database: Stores all scope data in a PostgreSQL database for reliable, concurrent access.
• Powerful Querying: Easily print targets by type (URLs, wildcards, mobile, etc.), platform, or program.
• Track Changes: Monitor scope additions and removals over time.
• LLM Cleanup (opt-in): Let GPT-style models fix messy scope strings in bulk when polling.
• Flexible Output: Get your data in plain text, JSON, or CSV.
• Report Downloads: Bulk download your HackerOne reports as Markdown files, with parallel fetching and filtering by program, state, or severity.

Installation

Ensure you have a recent version of Go installed, then run:

go install github.com/sw33tLie/bbscope/v2@latest

Docker Installation

You can also run bbscope using Docker. The Docker image is automatically built and published to GitHub Container Registry (GHCR) on every push.

Pull the latest image:

docker pull ghcr.io/sw33tlie/bbscope:latest

Run bbscope with Docker:

docker run --rm ghcr.io/sw33tlie/bbscope:latest [command] [flags]

Tip: Add --pull=always to the command if you want to automatically always use the latest bbscope version.

Important: To persist your configuration across container runs, bind-mount the config file:

# Run with config mounted
docker run --rm \
  -v ~/.bbscope.yaml:/root/.bbscope.yaml \
  ghcr.io/sw33tlie/bbscope:latest poll --db -b -p

Note: The container connects to your PostgreSQL database using the db_url configured in ~/.bbscope.yaml. Make sure your database is accessible from the container (use host.docker.internal for local databases on macOS/Windows, or your database's network address).

Configuration

bbscope requires API credentials for private programs and a PostgreSQL connection URL. After running the tool for the first time, it will create a configuration file at ~/.bbscope.yaml.

You'll need to fill in your credentials and database URL:

…

Alternatively, you can provide credentials directly via command-line flags when running a poll subcommand. Flags will always override values in the configuration file.

Authentication Flags for poll Subcommands:

Database Configuration (Optional):

To use bbscope's database features (like tracking changes or querying targets), you need a PostgreSQL database.

Option 1: Use an existing PostgreSQL instance

Add your connection string to ~/.bbscope.yaml:

db_url: "postgres://user:password@localhost:5432/bbscope?sslmode=disable"

Option 2: Quick setup with Docker

[!IMPORTANT] Replace <YOUR_SECURE_PASSWORD> with a strong, unique password.

docker run --name bbscope-db \
  -e POSTGRES_USER=bbscope \
  -e POSTGRES_PASSWORD=<YOUR_SECURE_PASSWORD> \
  -e POSTGRES_DB=bbscope \
  -p 5432:5432 \
  -d postgres:alpine

Then add to your ~/.bbscope.yaml:

db_url: "postgres://bbscope:<YOUR_SECURE_PASSWORD>@localhost:5432/bbscope?sslmode=disable"

Tables are automatically created on the first run.

️ Usage & Commands

bbscope is organized into two main commands: poll and db.

poll - Fetching Scopes

The poll command fetches scope data from the platforms. You can poll all platforms at once or specify which ones to poll.

Subcommands:

• bbscope poll: Polls all configured platforms.
• bbscope poll h1: Polls HackerOne.
• bbscope poll bc: Polls Bugcrowd.
• bbscope poll it: Polls Intigriti.
• bbscope poll ywh: Polls YesWeHack.
• bbscope poll immunefi: Polls Immunefi (no authentication required).

Flags for poll:

AI-Assisted Normalization (Experimental)

Messy scope entries from platforms can now be cleaned up in bulk with the --ai flag:

bbscope poll --db --ai

• Requires an API key in ~/.bbscope.yaml under the ai section (or the OPENAI_API_KEY environment variable).
• Entries are batched per program to minimize API calls.
• If the model fails or omits an entry, the original target is used so nothing is lost.
• When the text explicitly says "out of scope" or similar, the AI pass can flip the entry's in_scope flag for you.
• Tune throughput with max_batch (targets per request) and max_concurrency (simultaneous requests) in the ai config section.

db - Interacting with the Database

The db command lets you query and manage the data stored in your PostgreSQL database.

db print

Prints raw scope data from the database. This is best for inspecting what's currently stored or for exporting data to other formats (JSON/CSV).

Usage: bbscope db print [flags]

db get

Extracts specific types of targets from the database. This command is designed for piping into other tools (like subfinder, httpx, etc.).

Usage: bbscope db get [subcommand] [flags]

Subcommands:

• wildcards: Get all wildcard domains (e.g., *.example.com).
• domains: Get all domains (including wildcards).
• urls: Get all full URLs (http/https).
• cidrs: Get all CIDR ranges.
• ips: Get all IP addresses.

Flags for db get wildcards:

Example:

# Get all wildcards and pipe to another tool
bbscope db get wildcards --aggressive | subfinder

db stats

Shows high-level statistics about the data in the database.

Usage: bbscope db stats

db changes

Shows the most recent scope changes (additions/removals).

Usage: bbscope db changes

| --limit | Number of recent changes to show. | 50 |

db find

Search for a string in current and historical scopes.

Usage: bbscope db find [query]

db shell

Open a psql shell connected to your database.

Usage: bbscope db shell

The bbscope DB schema will also be printed to stdout for ease of reference.

db add

Add a custom target to the database manually.

Usage: bbscope db add --target <target> [flags]

Flags for db add:

reports - Downloading Reports

The reports command bulk downloads your vulnerability reports as Markdown files, organized by program.

# Download all your HackerOne reports
bbscope reports h1 --output-dir ./reports

# Preview what would be downloaded
bbscope reports h1 --output-dir ./reports --dry-run

# Filter by program, state, or severity
bbscope reports h1 --output-dir ./reports --program google --state resolved --severity critical

Reports are saved as {output-dir}/h1/{program}/{id}_{title}.md with metadata tables and full vulnerability details. 10 parallel workers handle the downloads with automatic rate-limit handling.

Examples

1. First-Time Setup: Poll all private, bounty-only programs and save to DB

This is a great first command to run to populate your database.

bbscope poll --db -b -p

**2. Get all wildcards from all platforms, aggressive extraction

bbscope db get wildcards -a

3. Get all URLs and pipe to httpx

bbscope db get urls | httpx 

4. Show the 10 most recent scope changes

bbscope db changes --limit 10

5. Get all CIDRs from all platforms

bbscope db get cidrs

6. Poll with a Proxy

# Great for debugging when a platform changes their API 
bbscope poll h1 --proxy "http://127.0.0.1:8080"

7. HackerOne Polling (with Auth)

# Using flags (overrides config file)
bbscope poll h1 --user "your_user" --token "your_token"

8. Bugcrowd Polling

# Using session token
bbscope poll bc --token "your_bugcrowd_session_cookie"

# Using credentials
bbscope poll bc --email "..." --password "..." --otp-secret "..."

9. Intigriti Polling

bbscope poll it --token "your_api_token"

10. YesWeHack Polling

bbscope poll ywh --token "your_jwt_token"

11. Immunefi Polling

bbscope poll immunefi

Documentation

Full documentation is available at sw33tlie.github.io/bbscope.

Covers:

• Getting Started — installation, configuration, quick start
• CLI Reference — all commands, flags, output formatting
• Database — setup, schema, querying, SQL examples
• Web Interface — self-hosting, Docker deployment, REST API
• Platforms — auth setup for each platform
• AI Normalization — configuration, custom endpoints, cost
• Library Usage — using pkg/polling, pkg/platforms, pkg/storage, pkg/targets in your own Go proj