investigating-phishing-email-incident

Featured

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.

AI & Automation 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Investigating Phishing Email Incident ## When to Use Use this skill when: - A user reports a suspicious email via the phishing report button or helpdesk ticket - Email security gateway flags a message that bypassed initial filters - Automated detection identifies credential harvesting URLs or malicious attachments - A phishing campaign targeting the organization requires scope assessment **Do not use** for spam or marketing emails without malicious intent — route those to email administration for filter tuning. ## Prerequisites - Access to email gateway logs (Proofpoint, Mimecast, or Microsoft Defender for Office 365) - Splunk or SIEM with email log ingestion (O365 Message Trace, Exchange tracking logs) - Sandbox access (Any.Run, Joe Sandbox, or Hybrid Analysis) for URL/attachment detonation - Microsoft Graph API or Exchange Admin Center for email search and purge operations - URLScan.io and VirusTotal API keys ## Workflow ### Step 1: Extract and Analyze Email Headers Obtain the full email headers (`.eml` file) from the reported message: ```python import email from email import policy with open("phishing_sample.eml", "rb") as f: msg = email.message_from_binary_file(f, policy=policy.default) # Extract key headers print(f"From: {msg['From']}") print(f"Return-Path: {msg['Return-Path']}") print(f"Reply-To: {msg['Reply-To']}") print(f"Subject: {msg['Subject']}") print(f"Message-ID: {msg['Message-ID']}") print(f"X-Originating-IP: {msg['X-Originating-IP']}") # Pars...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

conducting-phishing-incident-response

Responds to phishing incidents by analyzing reported emails, extracting indicators, assessing credential compromise, quarantining malicious messages across the organization, and remediating affected accounts. Covers email header analysis, URL/attachment sandboxing, and mailbox-wide purge operations. Activates for requests involving phishing response, email incident, credential phishing, spear phishing investigation, or phishing remediation.

36,355 Updated 2 months ago
mukul975
Data & Documents Listed

phishing-analysis

Analyze a reported or suspicious email end to end: Received chain and SPF/DKIM/DMARC alignment, sender and Reply-To and display-name mismatches, lookalike domains, URL and redirector analysis, QR codes, HTML smuggling, attachment triage, lure classification (BEC/invoice, credential harvest, callback/TOAD, MFA push, package delivery, HR/payroll), verdict, blast radius, and response actions. Use it whenever someone pastes headers or an .eml, says "is this phishing", "a user reported this email", "check these headers", "is this sender legit", "who else got this", asks why DMARC failed, wants a phishing triage note, or forwards a suspicious invoice, voicemail, DocuSign, MFA, delivery, or payroll-change message, even if they never use the word phishing.

0 Updated 2 months ago
ftrout
AI & Automation Solid

analyzing-email-headers-for-phishing-investigation

Parse and analyze email headers to trace the origin of phishing emails, verify sender authenticity, and identify spoofing through SPF, DKIM, and DMARC validation.

100 Updated yesterday
26zl