Skip to content
For authorized security research

Document exposure within your program's scope.

Find credential records associated with authorized assets and prepare a contextualized disclosure that follows the program's rules.

Create a free account to start investigating.

LeakRadarExample
Disclosure notes#001
Authorized scopeportal.example.com
Exposed accountresearch@example.com
Password••••••••
Review the context before deciding what to do next.
Hand off to the security team
Illustration with fictional data.
The data behind LeakRadar

Investigate the exposed records, with the data to act.

644,961,994,529lines across indexed leak files

File lines, not a count of unique accounts.

Updated

Plaintext passwords, with their account context

Inspect the exposed password alongside the account and, for stealer logs, its service URL. When the source includes plaintext, that detail helps your team scope password resets and investigate exposed access.

Compare plans for plaintext access and included unlock points.

  • Stealer logs

    Connect a captured login to its service URL, username and password to understand which access is exposed.

    url:user:pass
  • Combolists

    Find email/password and username/password pairs, including records without a service URL.

    email:passuser:pass
  • Raw leak files

    Search the text of leaked files, database dumps and unstructured records beyond normalized credential fields.

  • Dark web forums

    Search indexed forum posts for mentions of your organization and examine the discussion's source context.

Get notified via Email, Slack, Discord, Telegram or Webhook when new exposed credentials match your monitored domains or email addresses.

Explore our data coverage
The situation

A match is the beginning of your assessment.

An address or service in a leak can help orient your research. Its presence alone does not establish a valid vulnerability. Keep the authorized scope, source context and program policy alongside your findings.

Make the evidence understandable to the person handling your report.

Your workflow

From scope to a clear disclosure

  1. 01

    Check the program scope

    Confirm the authorized assets and the policy for leaked credentials before starting your search.

  2. 02

    Research the relevant assets

    Use domain or other available search modes to examine records associated with those assets.

  3. 03

    Prepare your disclosure

    Record the context, explain what remains uncertain and mask sensitive details for the recipient.

LeakRadar

What you can work with

Access that fits your work

Start with a free account, then choose the plan that fits your datasets, monitoring, exports and team.

Compare plans

Focused searches

Use the relevant domains and filters to keep your investigation tied to authorized assets.

Material you can revisit

Save useful queries and use available exports to organize your research notes.

A clearer handoff

Present the affected asset, source information and observation context in a report the program can assess.

Bug bounty

Before you get started

Does finding a credential guarantee a bounty?

No. Eligibility and rewards depend on the program's policy and its assessment. A leak record alone does not guarantee acceptance.

What should I include in the report?

Include the authorized asset, relevant source context and a clear account of your observation. Follow the program's rules for handling sensitive information.