Menu

Individual skill

find-leaks-in-the-wild

0upvotes

Find leaked or mentioned selectors circulating in pastes, leak forums, Telegram channels and dump markets, and judge whether a claimed leak is genuine or a recycled combolist. Covers paste aggregators, site: searches over paste hosts, channel indexes and leak-search services. Use when checking whether a name, email, domain or credential is circulating, verifying a breach claim made against your organisation, or setting up ongoing leak monitoring. Applies to incident response and breach triage, threat intelligence, brand and executive protection, and extortion-claim validation. Reference at useosint.com/skills/find-leaks-in-the-wild.

skills/find-leaks-in-the-wild/SKILL.md

Read pinned source

Source commit 06243a5620b0c9c97502edd4ee9e31995a3bdccd

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
61
Repository last updated
Aug 3, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Find leaks in the wild

This is where data surfaces before anything indexes it, and where most of what
you find is a recombination of things that leaked years ago. Two mistakes cost
people most: assuming a paste host's own search will find pastes, and reporting
a combolist as a breach. The first wastes a day; the second is a factual error
in a deliverable and it will be found.

## Where to start with what you're holding

| You have | Start with | Why |
|---|---|---|
| An email or username | A curated breach service first | Cheap, attributed, and answers most questions — `what-leaked-about-you` |
| A selector you think is circulating now | `site:` sweep of paste hosts, then a paste aggregator | Engines are shallow but free; aggregators reach what was never crawled |