Back to catalog
Static reviewDevelopment

Skill dossier

monitoring-darkweb-sources

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

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. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/monitoring-darkweb-sources/SKILL.md:L90]
  • Step 1: Establish Keyword Monitoring via Commercial Services [Source statement; provisional, not tested. Evidence: skills/monitoring-darkweb-sources/SKILL.md:L92]
  • Step 2: Manual Investigation with Operational Security [Source statement; provisional, not tested. Evidence: skills/monitoring-darkweb-sources/SKILL.md:L103]
  • Step 3: Investigate Ransomware Leak Sites [Source statement; provisional, not tested. Evidence: skills/monitoring-darkweb-sources/SKILL.md:L121]
  • Step 4: Credential Exposure Monitoring [Source statement; provisional, not tested. Evidence: skills/monitoring-darkweb-sources/SKILL.md:L133]
  • Step 5: Document and Escalate Findings [Source statement; provisional, not tested. Evidence: skills/monitoring-darkweb-sources/SKILL.md:L145]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/monitoring-darkweb-sources/SKILL.md:L1-L71]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
27.9 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/monitoring-darkweb-sources/LICENSEOther11 KB
skills/monitoring-darkweb-sources/references/api-reference.mdReference2.2 KB
skills/monitoring-darkweb-sources/scripts/agent.pyScript6.6 KB
skills/monitoring-darkweb-sources/SKILL.mdInstruction8.1 KB

SKILL.md frontmatter

{
  "name": "monitoring-darkweb-sources",
  "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.\n",
  "domain": "cybersecurity",
  "subdomain": "threat-intelligence",
  "tags": [
    "dark-web",
    "OSINT",
    "credential-monitoring",
    "ransomware-leaks",
    "Recorded-Future",
    "SpiderFoot",
    "CTI"
  ],
  "version": "1.0.0",
  "author": "team-cybersecurity",
  "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"
  ],
  "mitre_attack": [
    "T1591",
    "T1592",
    "T1593",
    "T1589",
    "T1003"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "reconnaissance",
      "resource-development",
      "initial-access"
    ],
    "techniques": [
      {
        "id": "T1593",
        "name": "Search Open Websites/Domains",
        "tactic": "reconnaissance",
        "source": "attack"
      },
      {
        "id": "T1650",
        "name": "Acquire Access",
        "tactic": "resource-development",
        "source": "attack"
      },
      {
        "id": "T1555.003",
        "name": "Credentials from Password Stores: Credentials from Web Browsers",
        "tactic": "reconnaissance",
        "source": "attack"
      },
      {
        "id": "F1029",
        "name": "Gather Customer Information",
        "tactic": "reconnaissance",
        "source": "f3"
      },
      {
        "id": "T1110.004",
        "name": "Brute Force:  Credential Stuffing",
        "tactic": "initial-access",
        "source": "attack"
      }
    ]
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Establish Keyword Monitoring via Commercial Services

    Source-described action candidate under “Step 1: Establish Keyword Monitoring via Commercial Services”; not verified execution.

  4. 04
    Action

    Domain variations: `company.com`, `@company.com`, `company[dot]com`

    Source-described action candidate under “Step 1: Establish Keyword Monitoring via Commercial Services”; not verified execution.

  5. 05
    Action

    Executive names: CEO, CISO, CFO full names

    Source-described action candidate under “Step 1: Establish Keyword Monitoring via Commercial Services”; not verified execution.

  6. 06
    Action

    Product/brand names

    Source-described action candidate under “Step 1: Establish Keyword Monitoring via Commercial Services”; not verified execution.

Inspect all extracted workflow candidates (37 candidate steps)
  1. 07
    Decision

    Internal codenames or project names (if suspected breach scope is broad)

    Source-described decision candidate under “Step 1: Establish Keyword Monitoring via Commercial Services”; not verified execution.

  2. 08
    Action

    Known email domains for credential monitoring

    Source-described action candidate under “Step 1: Establish Keyword Monitoring via Commercial Services”; not verified execution.

  3. 09
    Action

    Step 2: Manual Investigation with Operational Security

    Source-described action candidate under “Step 2: Manual Investigation with Operational Security”; not verified execution.

  4. 10
    Action

    Use a dedicated physical machine or air-gapped VM (Whonix + VirtualBox)

    Source-described action candidate under “Step 2: Manual Investigation with Operational Security”; not verified execution.

  5. 11
    Action

    Connect via Tor Browser only — never via standard browser

    Source-described action candidate under “Step 2: Manual Investigation with Operational Security”; not verified execution.

  6. 12
    Action

    Use a cover identity with no links to organization

    Source-described action candidate under “Step 2: Manual Investigation with Operational Security”; not verified execution.

  7. 13
    Action

    Never log in with real credentials to any dark web site

    Source-described action candidate under “Step 2: Manual Investigation with Operational Security”; not verified execution.

  8. 14
    Action

    Document all sessions in investigation log with timestamps

    Source-described action candidate under “Step 2: Manual Investigation with Operational Security”; not verified execution.

  9. 15
    Action

    Step 3: Investigate Ransomware Leak Sites

    Source-described action candidate under “Step 3: Investigate Ransomware Leak Sites”; not verified execution.

  10. 16
    Action

    Capture screenshot evidence via commercial service (do not access directly)

    Source-described action candidate under “Step 3: Investigate Ransomware Leak Sites”; not verified execution.

  11. 17
    Action

    Assess legitimacy: Does the threat actor's claimed data align with any known internal systems?

    Source-described action candidate under “Step 3: Investigate Ransomware Leak Sites”; not verified execution.

  12. 18
    Action

    Check timestamp: Is this claim recent or historical?

    Source-described action candidate under “Step 3: Investigate Ransomware Leak Sites”; not verified execution.

  13. 19
    Action

    Cross-reference with any known security incidents or phishing campaigns from that timeframe

    Source-described action candidate under “Step 3: Investigate Ransomware Leak Sites”; not verified execution.

  14. 20
    Decision

    Engage IR team if claim appears credible before public disclosure

    Source-described decision candidate under “Step 3: Investigate Ransomware Leak Sites”; not verified execution.

  15. 21
    Action

    Step 4: Credential Exposure Monitoring

    Source-described action candidate under “Step 4: Credential Exposure Monitoring”; not verified execution.

  16. 22
    Action

    Have I Been Pwned Enterprise: Domain-level notification for credential exposures in breach datasets

    Source-described action candidate under “Step 4: Credential Exposure Monitoring”; not verified execution.

  17. 23
    Action

    SpyCloud: Commercial credential monitoring with anti-cracking and plaintext password recovery from criminal markets

    Source-described action candidate under “Step 4: Credential Exposure Monitoring”; not verified execution.

  18. 24
    Action

    Flare Systems: Automated monitoring of paste sites and dark web markets for credential dumps

    Source-described action candidate under “Step 4: Credential Exposure Monitoring”; not verified execution.

  19. 25
    Decision

    When credential exposures are confirmed:

    Source-described decision candidate under “Step 4: Credential Exposure Monitoring”; not verified execution.

  20. 26
    Action

    Force password reset for affected accounts immediately

    Source-described action candidate under “Step 4: Credential Exposure Monitoring”; not verified execution.

  21. 27
    Decision

    Check if credentials provide access to any organizational systems (SSO, VPN)

    Source-described decision candidate under “Step 4: Credential Exposure Monitoring”; not verified execution.

  22. 28
    Action

    Review access logs for the period between credential exposure and detection for unauthorized access

    Source-described action candidate under “Step 4: Credential Exposure Monitoring”; not verified execution.

  23. 29
    Action

    Step 5: Document and Escalate Findings

    Source-described action candidate under “Step 5: Document and Escalate Findings”; not verified execution.

  24. 30
    Action

    Capture evidence (commercial service screenshot, paste site archive)

    Source-described action candidate under “Step 5: Document and Escalate Findings”; not verified execution.

  25. 31
    Action

    Classify severity: P1 (imminent attack threat or active data exposure), P2 (credential exposure), P3 (general mention)

    Source-described action candidate under “Step 5: Document and Escalate Findings”; not verified execution.

  26. 32
    Action

    Notify appropriate stakeholders within defined SLAs

    Source-described action candidate under “Step 5: Document and Escalate Findings”; not verified execution.

  27. 33
    Action

    Open investigation ticket and link to evidence artifacts

    Source-described action candidate under “Step 5: Document and Escalate Findings”; not verified execution.

  28. 34
    Action

    Apply TLP:RED for any findings referencing named executives or specific attack plans

    Source-described action candidate under “Step 5: Document and Escalate Findings”; not verified execution.

  29. 35
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  30. 36
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  31. 37
    Action

    Common Pitfalls

    Source-described action candidate under “Common Pitfalls”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

27 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

16 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 16 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

4 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 4 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

7 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 7 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/monitoring-darkweb-sources/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/monitoring-darkweb-sources/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/monitoring-darkweb-sources
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.