Back to catalog
Static reviewDevelopment

Skill dossier

conducting-phishing-incident-response

Source declaration

Respond to phishing incidents by analyzing reported emails, extracting indicators, sandboxing URLs/attachments, assessing credential compromise, quarantining malicious messages organization-wide, and remediating affected accounts. Use when investigating a reported phishing or credential-phishing email, a suspected spearphishing incident, or when a mailbox-wide purge and account remediation is needed.

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

Respond to phishing incidents by analyzing reported emails, extracting indicators, sandboxing URLs/attachments, assessing credential compromise, quarantining malicious messages organization-wide, and remediating affected accounts. Use when investigating a reported phishing or credential-phishing email, a suspected spearphishing incident, or when a mailbox-wide purge and account remediation is needed.

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.

Respond to phishing incidents by analyzing reported emails, extracting indicators, sandboxing URLs/attachments, assessing credential compromise, quarantining malicious messages organization-wide, and remediating affected accounts. Use when investigating a reported phishing or credential-phishing email, a suspected spearphishing incident, or when a mailbox-wide purge and account remediation is needed. 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-phishing-incident-response/SKILL.md:L82]
  • Step 1: Receive and Triage the Phishing Report [Source statement; provisional, not tested. Evidence: skills/conducting-phishing-incident-response/SKILL.md:L84]
  • Step 2: Analyze Malicious Content [Source statement; provisional, not tested. Evidence: skills/conducting-phishing-incident-response/SKILL.md:L111]
  • Step 3: Determine Scope of Impact [Source statement; provisional, not tested. Evidence: skills/conducting-phishing-incident-response/SKILL.md:L128]
  • Step 4: Contain the Threat [Source statement; provisional, not tested. Evidence: skills/conducting-phishing-incident-response/SKILL.md:L149]
  • Step 5: Eradicate and Recover [Source statement; provisional, not tested. Evidence: skills/conducting-phishing-incident-response/SKILL.md:L180]
  • Step 6: Post-Incident Actions [Source statement; provisional, not tested. Evidence: skills/conducting-phishing-incident-response/SKILL.md:L190]

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-phishing-incident-response/SKILL.md:L1-L59]

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

File inventory

PathTypeBytes
skills/conducting-phishing-incident-response/LICENSEOther11 KB
skills/conducting-phishing-incident-response/references/api-reference.mdReference2 KB
skills/conducting-phishing-incident-response/scripts/agent.pyScript7.2 KB
skills/conducting-phishing-incident-response/SKILL.mdInstruction11.6 KB

SKILL.md frontmatter

{
  "name": "conducting-phishing-incident-response",
  "description": "Respond to phishing incidents by analyzing reported emails, extracting indicators, sandboxing URLs/attachments, assessing credential compromise, quarantining malicious messages organization-wide, and remediating affected accounts. Use when investigating a reported phishing or credential-phishing email, a suspected spearphishing incident, or when a mailbox-wide purge and account remediation is needed.",
  "domain": "cybersecurity",
  "subdomain": "incident-response",
  "tags": [
    "phishing-response",
    "email-security",
    "credential-compromise",
    "email-header-analysis",
    "mailbox-remediation"
  ],
  "mitre_attack": [
    "T1566.001",
    "T1566.002",
    "T1204.002",
    "T1204.001",
    "T1114",
    "T1056.003"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "initial-access",
      "reconnaissance",
      "resource-development",
      "positioning"
    ],
    "techniques": [
      {
        "id": "T1660",
        "name": "Phishing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1598",
        "name": "Phishing for Information",
        "tactic": "reconnaissance",
        "source": "attack"
      },
      {
        "id": "F1020.002",
        "name": "Create Fake Materials: Fake Website",
        "tactic": "resource-development",
        "source": "f3"
      },
      {
        "id": "T1557",
        "name": "Adversary-in-the-Middle",
        "tactic": "positioning",
        "source": "attack"
      },
      {
        "id": "F1004",
        "name": "Access with Stolen Session Cookie",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "F1006.002",
        "name": "Account Takeover: Exposed Login Credential",
        "tactic": "initial-access",
        "source": "f3"
      }
    ]
  },
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "RS.MA-01",
    "RS.MA-02",
    "RS.AN-03",
    "RC.RP-01"
  ]
}

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
    Input

    Step 1: Receive and Triage the Phishing Report

    Source-described input candidate under “Step 1: Receive and Triage the Phishing Report”; not verified execution.

  4. 04
    Action

    Extract the email as an .EML or .MSG file (preserves headers)

    Source-described action candidate under “Step 1: Receive and Triage the Phishing Report”; not verified execution.

  5. 05
    Action

    Analyze email headers to determine the true sender, relay path, and authentication results

    Source-described action candidate under “Step 1: Receive and Triage the Phishing Report”; not verified execution.

  6. 06
    Action

    Confirmed Phishing: Malicious URL/attachment, spoofed sender, credential harvesting page

    Source-described action candidate under “Step 1: Receive and Triage the Phishing Report”; not verified execution.

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

    Suspicious: Anomalous headers but no confirmed malicious content

    Source-described action candidate under “Step 1: Receive and Triage the Phishing Report”; not verified execution.

  2. 08
    Action

    Spam/Marketing: Unwanted but not malicious

    Source-described action candidate under “Step 1: Receive and Triage the Phishing Report”; not verified execution.

  3. 09
    Output

    Legitimate: Not a phishing email (false report)

    Source-described output candidate under “Step 1: Receive and Triage the Phishing Report”; not verified execution.

  4. 10
    Action

    Step 2: Analyze Malicious Content

    Source-described action candidate under “Step 2: Analyze Malicious Content”; not verified execution.

  5. 11
    Action

    Check URL against VirusTotal, URLscan.io, and Google Safe Browsing

    Source-described action candidate under “Step 2: Analyze Malicious Content”; not verified execution.

  6. 12
    Action

    Open URL in a sandbox browser to capture the landing page

    Source-described action candidate under “Step 2: Analyze Malicious Content”; not verified execution.

  7. 13
    Decision

    Check if the URL redirects to a credential harvesting page

    Source-described decision candidate under “Step 2: Analyze Malicious Content”; not verified execution.

  8. 14
    Action

    Identify the phishing kit type (Microsoft 365 login clone, Okta clone, generic)

    Source-described action candidate under “Step 2: Analyze Malicious Content”; not verified execution.

  9. 15
    Decision

    Determine if the phishing page is still active

    Source-described decision candidate under “Step 2: Analyze Malicious Content”; not verified execution.

  10. 16
    Action

    Calculate file hash (SHA-256) and check against VirusTotal

    Source-described action candidate under “Step 2: Analyze Malicious Content”; not verified execution.

  11. 17
    Action

    Detonate in sandbox (ANY.RUN, Joe Sandbox)

    Source-described action candidate under “Step 2: Analyze Malicious Content”; not verified execution.

  12. 18
    Action

    Analyze document for macros (olevba for Office files)

    Source-described action candidate under “Step 2: Analyze Malicious Content”; not verified execution.

  13. 19
    Action

    Check for embedded exploits (CVE exploitation in document parsers)

    Source-described action candidate under “Step 2: Analyze Malicious Content”; not verified execution.

  14. 20
    Action

    Step 3: Determine Scope of Impact

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

  15. 21
    Action

    Microsoft 365: Use Threat Explorer or Content Search to find all instances of the email

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

  16. 22
    Action

    Google Workspace: Use Admin Console > Investigation tool for message search

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

  17. 23
    Action

    Proxy logs: Search for connections to the phishing URL from internal IPs

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

  18. 24
    Action

    EDR: Search for attachment file hash execution across all endpoints

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

  19. 25
    Action

    Step 4: Contain the Threat

    Source-described action candidate under “Step 4: Contain the Threat”; not verified execution.

  20. 26
    Action

    Purge the phishing email from all mailboxes using Microsoft 365 Content Search and Purge or Google Workspace Admin delete

    Source-described action candidate under “Step 4: Contain the Threat”; not verified execution.

  21. 27
    Action

    Block the sender domain at the email gateway

    Source-described action candidate under “Step 4: Contain the Threat”; not verified execution.

  22. 28
    Action

    Add the phishing URL to the web proxy blocklist

    Source-described action candidate under “Step 4: Contain the Threat”; not verified execution.

  23. 29
    Action

    Add attachment hash to email gateway and EDR blocklists

    Source-described action candidate under “Step 4: Contain the Threat”; not verified execution.

  24. 30
    Action

    Force password reset immediately

    Source-described action candidate under “Step 4: Contain the Threat”; not verified execution.

  25. 31
    Action

    Revoke all active sessions and OAuth tokens

    Source-described action candidate under “Step 4: Contain the Threat”; not verified execution.

  26. 32
    Action

    Enable or re-verify MFA enrollment

    Source-described action candidate under “Step 4: Contain the Threat”; not verified execution.

  27. 33
    Action

    Review mailbox rules for attacker-created forwarding rules

    Source-described action candidate under “Step 4: Contain the Threat”; not verified execution.

  28. 34
    Action

    Check for unauthorized OAuth application grants

    Source-described action candidate under “Step 4: Contain the Threat”; not verified execution.

  29. 35
    Action

    Review recent sign-in activity for suspicious locations

    Source-described action candidate under “Step 4: Contain the Threat”; not verified execution.

  30. 36
    Action

    Step 5: Eradicate and Recover

    Source-described action candidate under “Step 5: Eradicate and Recover”; not verified execution.

  31. 37
    Action

    Confirm email purge completed successfully across all mailboxes

    Source-described action candidate under “Step 5: Eradicate and Recover”; not verified execution.

  32. 38
    Action

    Verify compromised accounts have been secured (password changed, sessions revoked, MFA verified)

    Source-described action candidate under “Step 5: Eradicate and Recover”; not verified execution.

  33. 39
    Action

    Remove any malware installed via phishing attachments from affected endpoints

    Source-described action candidate under “Step 5: Eradicate and Recover”; not verified execution.

  34. 40
    Action

    Monitor compromised accounts for 72 hours for signs of continued unauthorized access

    Source-described action candidate under “Step 5: Eradicate and Recover”; not verified execution.

  35. 41
    Action

    Check for data exfiltration from compromised accounts during the exposure window

    Source-described action candidate under “Step 5: Eradicate and Recover”; not verified execution.

  36. 42
    Action

    Step 6: Post-Incident Actions

    Source-described action candidate under “Step 6: Post-Incident Actions”; not verified execution.

  37. 43
    Output

    Report the phishing URL to Google Safe Browsing and Microsoft SmartScreen

    Source-described output candidate under “Step 6: Post-Incident Actions”; not verified execution.

  38. 44
    Action

    Submit the phishing domain for takedown via the domain registrar abuse contact

    Source-described action candidate under “Step 6: Post-Incident Actions”; not verified execution.

  39. 45
    Action

    Update email gateway filtering rules based on observed evasion techniques

    Source-described action candidate under “Step 6: Post-Incident Actions”; not verified execution.

  40. 46
    Action

    Send targeted security awareness notification to affected users

    Source-described action candidate under “Step 6: Post-Incident Actions”; not verified execution.

  41. 47
    Action

    Update phishing simulation program to include the observed technique

    Source-described action candidate under “Step 6: Post-Incident Actions”; not verified execution.

  42. 48
    Action

    Key Concepts

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

  43. 49
    Action

    Tools & Systems

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

  44. 50
    Action

    Common Scenarios

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

  45. 51
    Action

    Scan the QR code in a sandbox to extract the URL

    Source-described action candidate under “Scenario: Microsoft 365 Credential Phishing via QR Code”; not verified execution.

  46. 52
    Action

    Analyze the phishing page: captures credentials and MFA tokens (adversary-in-the-middle attack)

    Source-described action candidate under “Scenario: Microsoft 365 Credential Phishing via QR Code”; not verified execution.

  47. 53
    Action

    Search email gateway for all recipients using message subject and sender as search criteria

    Source-described action candidate under “Scenario: Microsoft 365 Credential Phishing via QR Code”; not verified execution.

  48. 54
    Action

    Cross-reference with proxy logs to identify users who visited the phishing URL

    Source-described action candidate under “Scenario: Microsoft 365 Credential Phishing via QR Code”; not verified execution.

  49. 55
    Action

    Force password reset and revoke sessions for all users who visited the URL

    Source-described action candidate under “Scenario: Microsoft 365 Credential Phishing via QR Code”; not verified execution.

  50. 56
    Action

    Purge the email from all mailboxes and block the sender domain

    Source-described action candidate under “Scenario: Microsoft 365 Credential Phishing via QR Code”; not verified execution.

  51. 57
    Action

    Notify users about the specific campaign with visual examples of the phishing email

    Source-described action candidate under “Scenario: Microsoft 365 Credential Phishing via QR Code”; not verified execution.

  52. 58
    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

18 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 useNot observed
Medium

Network access is mentioned

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

9 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 9 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/conducting-phishing-incident-response/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/conducting-phishing-incident-response/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-phishing-incident-response
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.