--- name: monitoring-darkweb-sources-282b928ebc39 description: 'Monitors dark web forums, marketplaces, paste sites, and ransomware leak sites for mentions of organizational assets, leaked credentials, threatened attacks, and threat actor communications to provide early warning intelligence. Use when establishing dark web monitoring coverage, investigating specific data breach claims, or enriching incident investigations with dark web context. Activates for requests involving dark web OSINT, leak site monitoring, credential exposure, Recorded Future dark web, or Tor hidden service intelligence. ' domain: cybersecurity subdomain: threat-intelligence tags: - dark-web - OSINT - credential-monitoring - ransomware-leaks - Recorded-Future - SpiderFoot - CTI version: 1.0.0 author: Krishna Kumar (xalgord) license: Apache-2.0 nist_ai_rmf: - MEASURE-2.7 - MAP-5.1 - MANAGE-2.4 atlas_techniques: - AML.T0070 - AML.T0066 - AML.T0082 nist_csf: - ID.RA-01 - ID.RA-05 - DE.CM-01 - DE.AE-02 --- # 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. ## Detection Gaps & Validation - **Clearnet sources missed (the #1 gap):** most programs over-focus on .onion and skip Telegram channels, Discord servers, and paste sites (Pastebin, psbdmp) where much criminal activity actually lives. Cover clearnet explicitly. - **Keyword brittleness:** monitoring only `company.com` misses obfuscated variants (`company[.]com`, `@company.com`, typosquats, internal codenames). Validate the watchlist catches deliberate evasions. - **Unverified leak claims:** ransomware groups fabricate or recycle old breach data for extortion. Confirm a claim by matching sample data to known internal systems and checking timestamps before escalating - do not over-react. - **Language and access coverage:** Russian- and Chinese-language forums (XSS, Exploit.in) require native-language and vetted-access collection that most tools lack. Confirm your commercial source actually reaches them. - **Stealer-log blind spot:** credential monitoring keyed to breach dumps misses infostealer logs (cookies, session tokens) sold separately. Cover both. - **How to validate:** corroborate each finding across two sources, capture timestamped evidence immediately (content disappears fast), classify P1/P2/P3, and confirm exposed credentials actually grant access via auth-log review before declaring impact. ## 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**: 1. Use a dedicated physical machine or air-gapped VM (Whonix + VirtualBox) 2. Connect via Tor Browser only — never via standard browser 3. Use a cover identity with no links to organization 4. Never log in with real credentials to any dark web site 5. Document all sessions in investigation log with timestamps **Paste site monitoring** (clearnet-accessible, no Tor required): ```bash # 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: 1. Capture screenshot evidence via commercial service (do not access directly) 2. Assess legitimacy: Does the threat actor's claimed data align with any known internal systems? 3. Check timestamp: Is this claim recent or historical? 4. Cross-reference with any known security incidents or phishing campaigns from that timeframe 5. 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: 1. Force password reset for affected accounts immediately 2. Check if credentials provide access to any organizational systems (SSO, VPN) 3. 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. --- Source attribution: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/threat-intelligence/monitoring-darkweb-sources/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2026 xalgord Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/threat-intelligence/monitoring-darkweb-sources/SKILL.md Attribution basis: Source repository record Fields of work: Data & Analytics, Marketing Roles: Data Analyst, Marketing Analyst Specialties: Specialty not specified Tools: Recorded Future, Spiderfoot Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: abe18b63049e2c693d7abd199577b13c7718b4e5aa2cd0dd34eefa196f12d6cc