Monitoring Dark Web Sources
When to Use
Use this skill when:
- Establishing continuous monitoring for organizational domain names, executive names, and product brands on dark web forums
- Investigating a reported data breach claim found on a ransomware leak site or paste site
- Enriching an incident investigation with context about stolen credentials or planned attacks
Do not use this skill without proper operational security measures — dark web browsing without isolation exposes analyst infrastructure to adversary counter-intelligence.
Prerequisites
- Commercial dark web monitoring service (Recorded Future, Flashpoint, Intel 471, or Cybersixgill)
- Isolated operational environment: Whonix OS or Tails OS running in a VM with no persistent storage
- Keyword watchlist: organization domain, key executive names, product names, IP ranges, known credentials
- Legal guidance confirming passive monitoring is authorized in your jurisdiction
Workflow
Step 1: Establish Keyword Monitoring via Commercial Services
Configure dark web monitoring keywords in your CTI platform (e.g., Recorded Future Exposure module):
- Domain variations:
company.com, @company.com, company[dot]com
- Executive names: CEO, CISO, CFO full names
- Product/brand names
- Internal codenames or project names (if suspected breach scope is broad)
- Known email domains for credential monitoring
Most commercial services (Flashpoint, Intel 471, Cybersixgill) crawl forums like XSS, Exploit[.]in, BreachForums, and Russian-language cybercriminal communities without analyst exposure.
Step 2: Manual Investigation with Operational Security
For investigations requiring direct dark web access:
Environment setup:
- Use a dedicated physical machine or air-gapped VM (Whonix + VirtualBox)
- Connect via Tor Browser only — never via standard browser
- Use a cover identity with no links to organization
- Never log in with real credentials to any dark web site
- Document all sessions in investigation log with timestamps
Paste site monitoring (clearnet-accessible, no Tor required):
# Hunt paste sites via API
curl "https://psbdmp.ws/api/search/company.com" | jq '.data[].id'
curl "https://pastebin.com/search?q=company.com" # Rate-limited public search
Step 3: Investigate Ransomware Leak Sites
Ransomware groups maintain .onion leak sites. Monitor these through commercial services rather than direct access. When a claim appears about your organization:
- Capture screenshot evidence via commercial service (do not access directly)
- Assess legitimacy: Does the threat actor's claimed data align with any known internal systems?
- Check timestamp: Is this claim recent or historical?
- Cross-reference with any known security incidents or phishing campaigns from that timeframe
- Engage IR team if claim appears credible before public disclosure
Known active ransomware leak site operators (as of early 2025): LockBit (disrupted Feb 2024), ALPHV/BlackCat (disrupted Dec 2023), Cl0p, RansomHub, Play.
Step 4: Credential Exposure Monitoring
For leaked credential monitoring:
- Have I Been Pwned Enterprise: Domain-level notification for credential exposures in breach datasets
- SpyCloud: Commercial credential monitoring with anti-cracking and plaintext password recovery from criminal markets
- Flare Systems: Automated monitoring of paste sites and dark web markets for credential dumps
When credential exposures are confirmed:
- Force password reset for affected accounts immediately
- Check if credentials provide access to any organizational systems (SSO, VPN)
- Review access logs for the period between credential exposure and detection for unauthorized access
Step 5: Document and Escalate Findings
For each dark web finding:
- Capture evidence (commercial service screenshot, paste site archive)
- Classify severity: P1 (imminent attack threat or active data exposure), P2 (credential exposure), P3 (general mention)
- Notify appropriate stakeholders within defined SLAs
- Open investigation ticket and link to evidence artifacts
- Apply TLP:RED for any findings referencing named executives or specific attack plans
Key Concepts
| Term |
Definition |
| Dark Web |
Tor-accessible hidden services (.onion domains) not indexed by standard search engines; hosts both legitimate and criminal content |
| Paste Site |
Clearnet text-sharing sites (Pastebin, Ghostbin) frequently used to publish stolen data or malware configurations |
| Ransomware Leak Site |
.onion site operated by ransomware group to publish stolen victim data as extortion leverage |
| Operational Security (OPSEC) |
Protecting analyst identity and organizational affiliation during dark web investigation |
| Credential Stuffing |
Automated use of leaked username/password pairs against authentication systems |
| Stealer Logs |
Data packages exfiltrated by infostealer malware containing saved browser credentials, cookies, and session tokens |
Tools & Systems
- Recorded Future Dark Web Module: Automated monitoring of dark web sources with alerting on organization-specific keywords
- Flashpoint: Dark web forum monitoring with human intelligence augmentation for criminal community context
- Intel 471: Closed-source access to cybercriminal communities with structured intelligence on threat actors
- SpyCloud: Credential exposure monitoring with recaptured plaintext passwords from criminal markets
- Have I Been Pwned Enterprise: Domain-level breach notification API for credential monitoring at scale
Common Pitfalls
- Direct access without OPSEC: Accessing dark web forums without Tor and a cover identity can expose analyst IP, browser fingerprint, and organization affiliation to adversaries.
- Overreacting to unverified claims: Ransomware groups and forum posters fabricate attack claims for extortion or reputation. Verify before escalating to incident response.
- Missing clearnet sources: Most dark web intelligence programs miss Telegram channels, Discord servers, and paste sites which operate on the clearnet and host significant criminal activity.
- Inadequate legal review: Dark web monitoring must be reviewed by legal counsel — passive monitoring is generally lawful but active participation in criminal markets is not.
- No evidence preservation: Dark web content disappears rapidly. Capture timestamped evidence immediately upon discovery using commercial service exports.
1---2name: monitoring-darkweb-sources3description: 'Monitors dark web forums, marketplaces, paste sites, and ransomware4 leak sites for mentions of organizational assets, leaked credentials, threatened5 attacks, and threat actor communications to provide early warning intelligence.6 Use when establishing dark web monitoring coverage, investigating specific data7 breach claims, or enriching incident investigations with dark web context. Activates8 for requests involving dark web OSINT, leak site monitoring, credential exposure,9 Recorded Future dark web, or Tor hidden service intelligence.1011 '12domain: cybersecurity13subdomain: threat-intelligence14tags:15- dark-web16- OSINT17- credential-monitoring18- ransomware-leaks19- Recorded-Future20- SpiderFoot21- CTI22version: 1.0.023author: team-cybersecurity24license: Apache-2.025nist_ai_rmf:26- MEASURE-2.727- MAP-5.128- MANAGE-2.429atlas_techniques:30- AML.T007031- AML.T006632- AML.T008233nist_csf:34- ID.RA-0135- ID.RA-0536- DE.CM-0137- DE.AE-0238mitre_attack:39- T159140- T159241- T159342- T158943- T100344mitre_f3:45 version: '1.1'46 tactics:47 - reconnaissance48 - resource-development49 - initial-access50 techniques:51 - id: T159352 name: Search Open Websites/Domains53 tactic: reconnaissance54 source: attack55 - id: T165056 name: Acquire Access57 tactic: resource-development58 source: attack59 - id: T1555.00360 name: 'Credentials from Password Stores: Credentials from Web Browsers'61 tactic: reconnaissance62 source: attack63 - id: F102964 name: Gather Customer Information65 tactic: reconnaissance66 source: f367 - id: T1110.00468 name: 'Brute Force: Credential Stuffing'69 tactic: initial-access70 source: attack71metadata:72 source: https://skillmd.com/skills/26zl/monitoring-darkweb-sources73---7475# Monitoring Dark Web Sources7677## When to Use7879Use this skill when:80- Establishing continuous monitoring for organizational domain names, executive names, and product brands on dark web forums81- Investigating a reported data breach claim found on a ransomware leak site or paste site82- Enriching an incident investigation with context about stolen credentials or planned attacks8384**Do not use** this skill without proper operational security measures — dark web browsing without isolation exposes analyst infrastructure to adversary counter-intelligence.8586## Prerequisites8788- Commercial dark web monitoring service (Recorded Future, Flashpoint, Intel 471, or Cybersixgill)89- Isolated operational environment: Whonix OS or Tails OS running in a VM with no persistent storage90- Keyword watchlist: organization domain, key executive names, product names, IP ranges, known credentials91- Legal guidance confirming passive monitoring is authorized in your jurisdiction9293## Workflow9495### Step 1: Establish Keyword Monitoring via Commercial Services9697Configure dark web monitoring keywords in your CTI platform (e.g., Recorded Future Exposure module):98- Domain variations: `company.com`, `@company.com`, `company[dot]com`99- Executive names: CEO, CISO, CFO full names100- Product/brand names101- Internal codenames or project names (if suspected breach scope is broad)102- Known email domains for credential monitoring103104Most commercial services (Flashpoint, Intel 471, Cybersixgill) crawl forums like XSS, Exploit[.]in, BreachForums, and Russian-language cybercriminal communities without analyst exposure.105106### Step 2: Manual Investigation with Operational Security107108For investigations requiring direct dark web access:109110**Environment setup**:1111. Use a dedicated physical machine or air-gapped VM (Whonix + VirtualBox)1122. Connect via Tor Browser only — never via standard browser1133. Use a cover identity with no links to organization1144. Never log in with real credentials to any dark web site1155. Document all sessions in investigation log with timestamps116117**Paste site monitoring** (clearnet-accessible, no Tor required):118```bash119# Hunt paste sites via API120curl "https://psbdmp.ws/api/search/company.com" | jq '.data[].id'121curl "https://pastebin.com/search?q=company.com" # Rate-limited public search122```123124### Step 3: Investigate Ransomware Leak Sites125126Ransomware groups maintain .onion leak sites. Monitor these through commercial services rather than direct access. When a claim appears about your organization:1271281. Capture screenshot evidence via commercial service (do not access directly)1292. Assess legitimacy: Does the threat actor's claimed data align with any known internal systems?1303. Check timestamp: Is this claim recent or historical?1314. Cross-reference with any known security incidents or phishing campaigns from that timeframe1325. Engage IR team if claim appears credible before public disclosure133134Known active ransomware leak site operators (as of early 2025): LockBit (disrupted Feb 2024), ALPHV/BlackCat (disrupted Dec 2023), Cl0p, RansomHub, Play.135136### Step 4: Credential Exposure Monitoring137138For leaked credential monitoring:139- **Have I Been Pwned Enterprise**: Domain-level notification for credential exposures in breach datasets140- **SpyCloud**: Commercial credential monitoring with anti-cracking and plaintext password recovery from criminal markets141- **Flare Systems**: Automated monitoring of paste sites and dark web markets for credential dumps142143When credential exposures are confirmed:1441. Force password reset for affected accounts immediately1452. Check if credentials provide access to any organizational systems (SSO, VPN)1463. Review access logs for the period between credential exposure and detection for unauthorized access147148### Step 5: Document and Escalate Findings149150For each dark web finding:151- Capture evidence (commercial service screenshot, paste site archive)152- Classify severity: P1 (imminent attack threat or active data exposure), P2 (credential exposure), P3 (general mention)153- Notify appropriate stakeholders within defined SLAs154- Open investigation ticket and link to evidence artifacts155- Apply TLP:RED for any findings referencing named executives or specific attack plans156157## Key Concepts158159| Term | Definition |160|------|-----------|161| **Dark Web** | Tor-accessible hidden services (.onion domains) not indexed by standard search engines; hosts both legitimate and criminal content |162| **Paste Site** | Clearnet text-sharing sites (Pastebin, Ghostbin) frequently used to publish stolen data or malware configurations |163| **Ransomware Leak Site** | .onion site operated by ransomware group to publish stolen victim data as extortion leverage |164| **Operational Security (OPSEC)** | Protecting analyst identity and organizational affiliation during dark web investigation |165| **Credential Stuffing** | Automated use of leaked username/password pairs against authentication systems |166| **Stealer Logs** | Data packages exfiltrated by infostealer malware containing saved browser credentials, cookies, and session tokens |167168## Tools & Systems169170- **Recorded Future Dark Web Module**: Automated monitoring of dark web sources with alerting on organization-specific keywords171- **Flashpoint**: Dark web forum monitoring with human intelligence augmentation for criminal community context172- **Intel 471**: Closed-source access to cybercriminal communities with structured intelligence on threat actors173- **SpyCloud**: Credential exposure monitoring with recaptured plaintext passwords from criminal markets174- **Have I Been Pwned Enterprise**: Domain-level breach notification API for credential monitoring at scale175176## Common Pitfalls177178- **Direct access without OPSEC**: Accessing dark web forums without Tor and a cover identity can expose analyst IP, browser fingerprint, and organization affiliation to adversaries.179- **Overreacting to unverified claims**: Ransomware groups and forum posters fabricate attack claims for extortion or reputation. Verify before escalating to incident response.180- **Missing clearnet sources**: Most dark web intelligence programs miss Telegram channels, Discord servers, and paste sites which operate on the clearnet and host significant criminal activity.181- **Inadequate legal review**: Dark web monitoring must be reviewed by legal counsel — passive monitoring is generally lawful but active participation in criminal markets is not.182- **No evidence preservation**: Dark web content disappears rapidly. Capture timestamped evidence immediately upon discovery using commercial service exports.