Back to catalog
Static reviewDevelopment

Skill dossier

conducting-spearphishing-simulation-campaign

Source declaration

Run a targeted spearphishing simulation for initial access by developing OSINT-derived pretexts, building payloads (HTML smuggling, macro docs, ISO/LNK, OneNote, QR codes), standing up look-alike-domain email infrastructure with SPF/DKIM/DMARC via GoPhish, and tracking results. Use in authorized engagements to gain initial access via personalized phishing against specific individuals, distinct from broad campaigns.

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

Run a targeted spearphishing simulation for initial access by developing OSINT-derived pretexts, building payloads (HTML smuggling, macro docs, ISO/LNK, OneNote, QR codes), standing up look-alike-domain email infrastructure with SPF/DKIM/DMARC via GoPhish, and tracking results. Use in authorized engagements to gain initial access via personalized phishing against specific individuals, distinct from broad campaigns.

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.

Run a targeted spearphishing simulation for initial access by developing OSINT-derived pretexts, building payloads (HTML smuggling, macro docs, ISO/LNK, OneNote, QR codes), standing up look-alike-domain email infrastructure with SPF/DKIM/DMARC via GoPhish, and tracking results. Use in authorized engagements to gain initial access via personalized phishing against specific individuals, distinct from broad campaigns. 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/conducting-spearphishing-simulation-campaign/SKILL.md:L111]

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/conducting-spearphishing-simulation-campaign/SKILL.md:L1-L65]

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
8
Markdown files
5
scripts
2
references
4
Size
59.5 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/conducting-spearphishing-simulation-campaign/assets/template.mdReference4.4 KB
skills/conducting-spearphishing-simulation-campaign/LICENSEOther11 KB
skills/conducting-spearphishing-simulation-campaign/references/api-reference.mdReference1.6 KB
skills/conducting-spearphishing-simulation-campaign/references/standards.mdReference2.9 KB
skills/conducting-spearphishing-simulation-campaign/references/workflows.mdReference6.6 KB
skills/conducting-spearphishing-simulation-campaign/scripts/agent.pyScript5 KB
skills/conducting-spearphishing-simulation-campaign/scripts/process.pyScript21.4 KB
skills/conducting-spearphishing-simulation-campaign/SKILL.mdInstruction6.5 KB

SKILL.md frontmatter

{
  "name": "conducting-spearphishing-simulation-campaign",
  "description": "Run a targeted spearphishing simulation for initial access by developing OSINT-derived pretexts, building payloads (HTML smuggling, macro docs, ISO/LNK, OneNote, QR codes), standing up look-alike-domain email infrastructure with SPF/DKIM/DMARC via GoPhish, and tracking results. Use in authorized engagements to gain initial access via personalized phishing against specific individuals, distinct from broad campaigns.",
  "domain": "cybersecurity",
  "subdomain": "red-teaming",
  "tags": [
    "red-team",
    "adversary-simulation",
    "mitre-attack",
    "exploitation",
    "post-exploitation",
    "spearphishing",
    "social-engineering"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "d3fend_techniques": [
    "File Metadata Consistency Validation",
    "Application Protocol Command Analysis",
    "Identifier Analysis",
    "Content Format Conversion",
    "Message Analysis"
  ],
  "nist_csf": [
    "ID.RA-01",
    "GV.OV-02",
    "DE.AE-07"
  ],
  "mitre_attack": [
    "T1566.001",
    "T1566.002",
    "T1598.003",
    "T1598.002",
    "T1204.002",
    "T1204.001"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "reconnaissance",
      "resource-development",
      "initial-access"
    ],
    "techniques": [
      {
        "id": "T1598",
        "name": "Phishing for Information",
        "tactic": "reconnaissance",
        "source": "attack"
      },
      {
        "id": "T1660",
        "name": "Phishing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1583.001",
        "name": "Acquire Infrastructure: Domains",
        "tactic": "resource-development",
        "source": "attack"
      },
      {
        "id": "F1020.002",
        "name": "Create Fake Materials: Fake Website",
        "tactic": "resource-development",
        "source": "f3"
      },
      {
        "id": "T1585",
        "name": "Establish Accounts",
        "tactic": "resource-development",
        "source": "attack"
      },
      {
        "id": "F1006.002",
        "name": "Account Takeover: Exposed Login Credential",
        "tactic": "initial-access",
        "source": "f3"
      }
    ]
  }
}

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
    Action

    Overview

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

  2. 02
    Decision

    When to Use

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

  3. 03
    Action

    Objectives

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

  4. 04
    Action

    MITRE ATT&CK Mapping

    Source-described action candidate under “MITRE ATT&CK Mapping”; not verified execution.

  5. 05
    Action

    Workflow

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

  6. 06
    Action

    Review OSINT findings for target personnel profiles

    Source-described action candidate under “Phase 1: Pretext Development”; not verified execution.

Inspect all extracted workflow candidates (33 candidate steps)
  1. 07
    Action

    Identify current organizational events (mergers, projects, new hires)

    Source-described action candidate under “Phase 1: Pretext Development”; not verified execution.

  2. 08
    Action

    Select pretext theme (IT helpdesk, HR benefits, vendor communication, executive request)

    Source-described action candidate under “Phase 1: Pretext Development”; not verified execution.

  3. 09
    Action

    Craft email templates with appropriate urgency and authority cues

    Source-described action candidate under “Phase 1: Pretext Development”; not verified execution.

  4. 10
    Action

    Create landing pages that mirror target organization's branding

    Source-described action candidate under “Phase 1: Pretext Development”; not verified execution.

  5. 11
    Action

    Select payload type based on target security controls:

    Source-described action candidate under “Phase 2: Payload Development”; not verified execution.

  6. 12
    Action

    Test payload against target's known security stack

    Source-described action candidate under “Phase 2: Payload Development”; not verified execution.

  7. 13
    Action

    Implement payload obfuscation techniques

    Source-described action candidate under “Phase 2: Payload Development”; not verified execution.

  8. 14
    Action

    Configure callback to C2 infrastructure

    Source-described action candidate under “Phase 2: Payload Development”; not verified execution.

  9. 15
    Action

    Register convincing look-alike domain

    Source-described action candidate under “Phase 3: Infrastructure Setup”; not verified execution.

  10. 16
    Action

    Age domain and build reputation (minimum 2 weeks recommended)

    Source-described action candidate under “Phase 3: Infrastructure Setup”; not verified execution.

  11. 17
    Action

    Configure SPF, DKIM, and DMARC records

    Source-described action candidate under “Phase 3: Infrastructure Setup”; not verified execution.

  12. 18
    Action

    Set up SMTP relay with GoPhish or custom mail server

    Source-described action candidate under “Phase 3: Infrastructure Setup”; not verified execution.

  13. 19
    Action

    Deploy credential harvesting pages with SSL certificates

    Source-described action candidate under “Phase 3: Infrastructure Setup”; not verified execution.

  14. 20
    Action

    Configure tracking pixels and click tracking

    Source-described action candidate under “Phase 3: Infrastructure Setup”; not verified execution.

  15. 21
    Action

    Send test emails to verify delivery and rendering

    Source-described action candidate under “Phase 4: Campaign Execution”; not verified execution.

  16. 22
    Action

    Launch campaign in waves (avoid mass sending)

    Source-described action candidate under “Phase 4: Campaign Execution”; not verified execution.

  17. 23
    Action

    Monitor email delivery rates and opens in real-time

    Source-described action candidate under “Phase 4: Campaign Execution”; not verified execution.

  18. 24
    Action

    Track link clicks and credential submissions

    Source-described action candidate under “Phase 4: Campaign Execution”; not verified execution.

  19. 25
    Action

    Deploy payloads to users who interact with phishing emails

    Source-described action candidate under “Phase 4: Campaign Execution”; not verified execution.

  20. 26
    Action

    Capture screenshots and evidence for reporting

    Source-described action candidate under “Phase 4: Campaign Execution”; not verified execution.

  21. 27
    Action

    Calculate campaign metrics (delivery rate, open rate, click rate, credential capture rate)

    Source-described action candidate under “Phase 5: Post-Campaign Analysis”; not verified execution.

  22. 28
    Action

    Identify users who reported phishing to SOC

    Source-described action candidate under “Phase 5: Post-Campaign Analysis”; not verified execution.

  23. 29
    Action

    Document bypass of email security controls

    Source-described action candidate under “Phase 5: Post-Campaign Analysis”; not verified execution.

  24. 30
    Action

    Map successful compromises to MITRE ATT&CK

    Source-described action candidate under “Phase 5: Post-Campaign Analysis”; not verified execution.

  25. 31
    Output

    Compile findings for engagement report

    Source-described output candidate under “Phase 5: Post-Campaign Analysis”; not verified execution.

  26. 32
    Action

    Tools and Resources

    Source-described action candidate under “Tools and Resources”; not verified execution.

  27. 33
    Action

    Validation Criteria

    Source-described action candidate under “Validation Criteria”; 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

52 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
Note

File modification is described or implemented

33 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 33 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

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

3 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 3 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/conducting-spearphishing-simulation-campaign/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 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/conducting-spearphishing-simulation-campaign/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/conducting-spearphishing-simulation-campaign
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.