find-leaks-in-the-wild
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.
UseOSINT · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add UseOSINT/Skills --skill find-leaks-in-the-wildAbout this skill
name: find-leaks-in-the-wild description: >- 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.
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 |
| A paste that has been deleted | A historical paste corpus | Deletion is the norm; some services retain the content |
| A claimed breach of a named company | The company's own disclosure, then a regulator notification | One authoritative source beats any amount of forum chatter |
| A dataset being advertised | Structural analysis of the sample | You almost never need the full dataset to answer the question |
| A domain you're defending | Vendor monitoring plus your own canary selectors | One-off searches miss everything posted between them |
Source-by-source access model and risk: reference/source-catalogue.md.
Why paste-site search doesn't work
Pastes are unlisted by default. No index page, no directory, reachable only by URL — so there is nothing for the host to search and nothing for a crawler to follow. Where a host offers a firehose or scraping interface at all, it is typically restricted to paid accounts with IP allowlisting, because the open version got abused. Volume is enormous and retention is short.
So people find pastes four other ways, in rough order of yield: third-party
aggregators that continuously scrape paste hosts and index the content;
historical paste corpora that retain content after the original was deleted;
search-engine site: queries, which are shallow because the pages are unlinked
and short-lived but cost nothing; and curated breach services that index pastes
alongside breaches.
Run the free ones first; query shapes are in google-like-a-spy. Note that the
paste ecosystem is far wider than the obvious hosts: minimal modern paste
services, code sandboxes, gists, published-to-web documents, and
client-side-encrypted paste software whose content the server itself cannot
read, making it invisible to every aggregator that exists.
Forums: a category with a life cycle
Do not learn site names; learn the pattern. A forum accumulates users and data, becomes the recognised marketplace, attracts law enforcement, gets seized or its operator arrested — and within weeks a successor appears claiming continuity, often with the same staff and the imported user database. The names change. The category does not.
Three consequences that change how you behave:
- A forum "restored" after a seizure may be operated or monitored by law enforcement. This has happened. Registering puts your details into an evidence set.
- Registration is a durable risk. Forum databases leak, get seized, and get published. Assume any account you create becomes public eventually, with its email, IP history and posts attached.
- What an unregistered visitor can see is the marketing, not the data. Reputation tiers and paywalls gate the actual datasets, which is exactly why paying for access is where the legal exposure escalates.
Many organisations prohibit investigators from touching these sites at all and buy the intelligence from a vendor who has accepted the risk contractually. That is a legitimate answer, not a cop-out.
Telegram is the distribution layer
Structural reasons, not fashion: channels broadcast to unlimited subscribers, large files attach directly, a banned channel is recreated in minutes, and public channels are reachable without an invitation.
Read public channels in a browser through the platform's public preview. No account, no joining. Joining is an account action that exposes you, and for reading a public channel it buys you nothing. Do this first and, in most investigations, only.
Discovery is the hard part — in-app search is weak for finding channels you do not already know about. Third-party channel indexes and channel-search services are the practical route, and they additionally give you subscriber history and post archives that the channel itself will not.
Two platform specifics worth knowing. Forwarded messages carry attribution to the originating channel, so a forward chain reconstructs the distribution path and often reaches the source. And bots are used as retrieval front-ends for leak databases — querying one exposes your account and hands your selectors to its operator, so treat any such bot as an intelligence collector pointed at you.
Channels vanish and take their archive with them. Capture posts, file listings and metadata the moment you see them.
If you need an account, it must be dedicated, on a number that is not yours, with discovery and contact-sync settings locked down before first launch. `investigate-without
Read the complete source ↗