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, t
Detected risks:
Find Leaks in the Wild is an OSINT tradecraft skill for determining whether a selector (name, email, domain, or credential) is circulating in pastes, leak forums, Telegram channels, and dump markets, and for judging whether a claimed leak is a genuine breach or a recycled combolist. It solves two costly mistakes: relying on a paste host's own search (which cannot find unlisted pastes) and misreporting a recombined combolist as a real breach. The guidance is oriented toward defensive and investigative work such as incident response, breach triage, threat intelligence, and validating extortion claims.
The skill is prose guidance rather than tooling. It provides a triage table mapping what you hold to where to start, explains why paste-site search fails and the four practical routes to find pastes (aggregators, historical corpora, site: queries, curated breach services), and describes the life-cycle pattern of leak forums along with the operational-security and legal risks of registering on or paying for access to them. It covers reading public Telegram channels through public previews without joining, the risks of leak-retrieval bots, and a structural checklist for distinguishing a genuine source dump from a combolist. Throughout, it emphasizes minimizing exposure, buying vendor intelligence to avoid legal risk, and the reality that some organizations prohibit touching these sites directly.
Because it deals with credential-leak ecosystems and underground markets, it is dual-use OSINT: written and framed for defenders and investigators, but the same knowledge maps the space attackers operate in. It targets incident responders, threat-intel analysts, and brand/executive-protection teams.
No. It is written guidance for finding and triaging leaked data, aimed at defensive use cases like incident response, breach triage, threat intelligence, and validating breach or extortion claims. It contains no exploit code.
Pastes are unlisted by default with no index or directory, so there is nothing for the host or a crawler to search. The skill recommends third-party aggregators, historical corpora, site: queries, and curated breach services instead.
It looks first for external confirmation (the victim's own disclosure or a regulator/CERT notice) and then for structural signals of a genuine source dump, such as consistent schema, coherent internal identifiers, realistic timestamps, and service-specific fields absent from a two-column deduped combolist.
Registering on leak forums is a durable exposure that can enter law-enforcement evidence sets and public dumps, leak-retrieval bots hand your selectors to their operators, and paying for dataset access is where legal exposure escalates. It advises minimizing footprint and often buying vendor intelligence instead.
No. It advises reading public Telegram channels via public browser previews without an account, and notes many organizations prohibit investigators from touching leak sites at all.
Quick Setup:
.claude/skills/Repository
useosint/osint-skills