Demo Center Home  >  Source Catalog Demo

DATA AND INTELLIGENCE · SOURCE CATALOG

Source Catalog

Explore the full range of recaptured identity data behind SpyCloud’s platform, organized by source type and recency.
Walk through the catalog from breach to infostealer log to phished record and see how each source reaches your stack.

Source Catalog Demo by SpyCloud

What You'll See

The data behind every SpyCloud product

The Source Catalog shows the full range of identity data SpyCloud recaptures from the criminal underground: session cookies, authentication tokens, MFA codes, and credentials drawn from third-party breaches, infostealer malware logs, phishing kits, and combolists.

This demo walks through how that data is organized by source type and recency, so you can judge coverage for the exposures your team actually has to act on. SpyCloud recaptures this data close to its source rather than scraping public paste sites, which is why an exposure often appears in the catalog before anyone uses it.

Browse
the catalog organized by source type, from breach to malware to phishing to combolist
Inspect
what each source contains and which identity assets it yields
Filter
by recency to see how fresh the data behind a given exposure actually is
Trace
a source through to the products that consume it and the exposures it surfaces
Gauge
coverage for the credentials, cookies, and tokens most relevant to your environment

How it Works

Infiltrate, recapture, parse, deliver

SpyCloud's recaptured dataset is built by getting inside the criminal ecosystems that trade identity data, then structuring what comes out so it can be matched to real people. SpyCloud draws from more than 100,000 data sources and tracks over 105 malware families, and the demo shows how that breadth turns into confirmed exposures inside every product.

STEP 1

Infiltrate

SpyCloud Labs maintains access to the criminal communities and infrastructure where stolen identity data changes hands.

STEP 2

Recapture

SpyCloud pulls session cookies, authentication tokens, MFA codes, and credentials from those sources at scale.

STEP 3

Parse

SpyCloud normalizes raw logs and dumps into structured records with source, date, and exposed field detail.

STEP 4

Deliver

Every SpyCloud product and the API read from the same parsed dataset, so coverage is consistent everywhere.

See what SpyCloud recaptures from the criminal underground and how it reaches your stack.

Explore the data

Outcomes of
recaptured identity data

100K+

data sources feeding the recaptured dataset

105+

malware families tracked

70B+

cookie records recaptured

Data provenance

Scraped, monitored, recaptured

Most vendors index what is already public.

SpyCloud obtains data from inside the criminal ecosystems that produce it, which is why the timing is different and the fields are richer.

Scraped

Pulled from public paste sites and forums after the data has already circulated. Late, partial, and often already reset.

YIELDS

Credentials only

Monitored

Watched passively from the outside. Tells you a credential appeared somewhere, not what else was taken or who it belongs to.

YIELDS

A signal, not a scope

Recaptured

Obtained close to the source inside criminal ecosystems, early enough to remediate before the data is used.

YIELDS

Session cookies, authentication tokens, MFA codes, and credentials

Takeaway: Coverage decides whether you get an alert or a confirmed, remediable exposure.

Check Your Exposure

See which of your identities already appear in recaptured criminal underground data. Check Your Exposure for a fast read.

Source Catalog Demo FAQs

The demo shows the full range of data SpyCloud recaptures, organized by source type such as third-party breaches, infostealer malware, phishing kits, and combolists, along with the recency of each source and how it maps to the exposures surfaced across SpyCloud products.

Recaptured data is obtained from the criminal underground itself rather than scraped from public paste sites or passively monitored from the outside. Because SpyCloud recaptures data close to its source, exposures often appear before they are widely used, which gives defenders time to remediate rather than time to respond.

A stolen credential is dangerous while it is still valid, and a stolen session is dangerous until it is revoked. Fresh recaptured data lets teams remediate before attackers act, while stale data usually reflects credentials that have already been used or changed.

The catalog contains session cookies, authentication tokens, MFA codes, and credentials, along with the supporting identity data that ties them to a person, such as email addresses, usernames, IP addresses, and device details from malware logs.

A reset invalidates the password but does not end an active session. If the source also yielded a valid session cookie or authentication token, an attacker can replay that session after the reset and bypass multifactor authentication. This is why the catalog surfaces session artifacts as first-class data rather than treating credentials as the whole exposure.