Back to catalog
Static reviewDevelopment

Skill dossier

investigating-phishing-email-incident

Source declaration

Investigates phishing email incidents from initial user report through header analysis, URL/attachment detonation, impacted user identification, and containment actions using SOC tools like Splunk, Microsoft Defender, and sandbox analysis platforms. Use when a reported phishing email requires full incident investigation to determine scope and impact.

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

Investigates phishing email incidents from initial user report through header analysis, URL/attachment detonation, impacted user identification, and containment actions using SOC tools like Splunk, Microsoft Defender, and sandbox analysis platforms. Use when a reported phishing email requires full incident investigation to determine scope and impact.

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.

Investigates phishing email incidents from initial user report through header analysis, URL/attachment detonation, impacted user identification, and containment actions using SOC tools like Splunk, Microsoft Defender, and sandbox analysis platforms. Use when a reported phishing email requires full incident investigation to determine scope and impact. 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/investigating-phishing-email-incident/SKILL.md:L88]
  • Step 1: Extract and Analyze Email Headers [Source statement; provisional, not tested. Evidence: skills/investigating-phishing-email-incident/SKILL.md:L90]
  • Step 2: Analyze URLs and Attachments [Source statement; provisional, not tested. Evidence: skills/investigating-phishing-email-incident/SKILL.md:L123]
  • Step 3: Determine Campaign Scope [Source statement; provisional, not tested. Evidence: skills/investigating-phishing-email-incident/SKILL.md:L173]
  • Step 4: Identify Impacted Users (Who Clicked) [Source statement; provisional, not tested. Evidence: skills/investigating-phishing-email-incident/SKILL.md:L206]
  • Step 5: Containment Actions [Source statement; provisional, not tested. Evidence: skills/investigating-phishing-email-incident/SKILL.md:L226]
  • Step 6: Document and Report [Source statement; provisional, not tested. Evidence: skills/investigating-phishing-email-incident/SKILL.md:L259]

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/investigating-phishing-email-incident/SKILL.md:L1-L67]

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
32.2 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/investigating-phishing-email-incident/LICENSEOther11 KB
skills/investigating-phishing-email-incident/references/api-reference.mdReference2.5 KB
skills/investigating-phishing-email-incident/scripts/agent.pyScript7.5 KB
skills/investigating-phishing-email-incident/SKILL.mdInstruction11.2 KB

SKILL.md frontmatter

{
  "name": "investigating-phishing-email-incident",
  "description": "Investigates phishing email incidents from initial user report through header analysis, URL/attachment detonation, impacted user identification, and containment actions using SOC tools like Splunk, Microsoft Defender, and sandbox analysis platforms. Use when a reported phishing email requires full incident investigation to determine scope and impact.\n",
  "domain": "cybersecurity",
  "subdomain": "soc-operations",
  "tags": [
    "soc",
    "phishing",
    "incident-response",
    "email-security",
    "splunk",
    "defender",
    "sandbox"
  ],
  "mitre_attack": [
    "T1078",
    "T1685.002",
    "T1685.005",
    "T1566",
    "T1598"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "reconnaissance",
      "resource-development",
      "initial-access",
      "stealth",
      "positioning"
    ],
    "techniques": [
      {
        "id": "T1598",
        "name": "Phishing for Information",
        "tactic": "reconnaissance",
        "source": "attack"
      },
      {
        "id": "T1660",
        "name": "Phishing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1672",
        "name": "Email Spoofing",
        "tactic": "stealth",
        "source": "attack"
      },
      {
        "id": "F1020.002",
        "name": "Create Fake Materials: Fake Website",
        "tactic": "resource-development",
        "source": "f3"
      },
      {
        "id": "T1539",
        "name": "Steal Web Session Cookie",
        "tactic": "positioning",
        "source": "attack"
      },
      {
        "id": "F1006.002",
        "name": "Account Takeover: Exposed Login Credential",
        "tactic": "initial-access",
        "source": "f3"
      }
    ]
  },
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "DE.CM-01",
    "DE.AE-02",
    "RS.MA-01",
    "DE.AE-06"
  ]
}

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: Extract and Analyze Email Headers

    Source-described action candidate under “Step 1: Extract and Analyze Email Headers”; not verified execution.

  4. 04
    Output

    SPF: Does `Return-Path` domain match sending IP? Look for `spf=pass` or `spf=fail`

    Source-described output candidate under “Step 1: Extract and Analyze Email Headers”; not verified execution.

  5. 05
    Action

    DKIM: Is the signature valid? `dkim=pass` confirms the email was not modified in transit

    Source-described action candidate under “Step 1: Extract and Analyze Email Headers”; not verified execution.

  6. 06
    Action

    DMARC: Does the `From` domain align with SPF/DKIM domains? `dmarc=fail` indicates spoofing

    Source-described action candidate under “Step 1: Extract and Analyze Email Headers”; not verified execution.

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

    Step 2: Analyze URLs and Attachments

    Source-described action candidate under “Step 2: Analyze URLs and Attachments”; not verified execution.

  2. 08
    Action

    Step 3: Determine Campaign Scope

    Source-described action candidate under “Step 3: Determine Campaign Scope”; not verified execution.

  3. 09
    Action

    Step 4: Identify Impacted Users (Who Clicked)

    Source-described action candidate under “Step 4: Identify Impacted Users (Who Clicked)”; not verified execution.

  4. 10
    Action

    Check proxy/web logs for users who visited the phishing URL:

    Source-described action candidate under “Step 4: Identify Impacted Users (Who Clicked)”; not verified execution.

  5. 11
    Decision

    Check if credentials were submitted (POST requests to phishing domain):

    Source-described decision candidate under “Step 4: Identify Impacted Users (Who Clicked)”; not verified execution.

  6. 12
    Action

    Step 5: Containment Actions

    Source-described action candidate under “Step 5: Containment Actions”; not verified execution.

  7. 13
    Action

    Add sender domain to email gateway block list

    Source-described action candidate under “Step 5: Containment Actions”; not verified execution.

  8. 14
    Action

    Add phishing URL domain to web proxy block list

    Source-described action candidate under “Step 5: Containment Actions”; not verified execution.

  9. 15
    Action

    Add attachment hash to endpoint detection block list

    Source-described action candidate under “Step 5: Containment Actions”; not verified execution.

  10. 16
    Action

    Create DNS sinkhole entry for phishing domain

    Source-described action candidate under “Step 5: Containment Actions”; not verified execution.

  11. 17
    Output

    Step 6: Document and Report

    Source-described output candidate under “Step 6: Document and Report”; not verified execution.

  12. 18
    Output

    Create incident report with full timeline, IOCs, impacted users, and remediation actions taken.

    Source-described output candidate under “Step 6: Document and Report”; not verified execution.

  13. 19
    Action

    Key Concepts

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

  14. 20
    Action

    Tools & Systems

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

  15. 21
    Action

    Common Scenarios

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

  16. 22
    Output

    Output Format

    Source-described output candidate under “Output Format”; 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

42 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

23 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 23 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

13 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 13 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

5 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 5 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

File deletion is described or implemented

Deletion syntax occurs in this line, including possible documentation. Review its exact target, recursive scope, and safeguards. The analyzer did not execute it. This rule matched 1 location(s) in the collected text; 1 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/investigating-phishing-email-incident/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/investigating-phishing-email-incident/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/investigating-phishing-email-incident
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.