conducting-phishing-incident-response

Featured

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.

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

# Conducting Phishing Incident Response ## When to Use - A user reports receiving a suspicious email via the phishing report button or abuse mailbox - Email gateway detects a malicious email that bypassed initial filtering - Threat intelligence indicates an active phishing campaign targeting the organization - A user confirms they clicked a link or opened an attachment from a suspicious email - Credentials have been entered on a suspected phishing page **Do not use** for business email compromise (BEC) involving compromised internal accounts; use BEC response procedures which focus on account takeover investigation. ## Prerequisites - Email security gateway with message trace and quarantine capabilities (Microsoft Defender for Office 365, Proofpoint, Mimecast) - Microsoft 365 admin access or Google Workspace admin for mailbox search and purge - Malware sandbox for attachment and URL analysis (ANY.RUN, Joe Sandbox, Hybrid Analysis) - Email header analysis tools (MXToolbox Header Analyzer, Google Admin Toolbox) - Identity provider access for account remediation (Azure AD, Okta, Duo) - Phishing report intake process (dedicated mailbox or integrated report button) ## Workflow ### Step 1: Receive and Triage the Phishing Report Evaluate the reported email to determine if it is malicious: - Extract the email as an .EML or .MSG file (preserves headers) - Analyze email headers to determine the true sender, relay path, and authentication results ``` Email Header Analysis Chec...

Details

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

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

investigating-phishing-email-incident

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.

36,355 Updated 2 months ago
mukul975
AI & Automation Listed

detect-phishing

Detection, hunting, and hardening methodology for phishing as initial and credential access: credential-harvest and attacker-in-the-middle (AiTM) link lures, malicious attachments, spearphishing via service, and OAuth consent phishing (MITRE ATT&CK T1566, T1566.001, T1566.002, T1566.003, T1598, T1528). Signals live in Defender for Office 365 advanced-hunting tables, the Exchange Online Unified Audit Log, Entra ID SigninLogs and AuditLogs, and web-proxy and DNS logs. Gives the defender view, a hunt, framework-mapped hardening, and pointers to public and sibling consent-phishing rules. Use when triaging a reported phishing email, investigating suspected AiTM session-token theft or a post-delivery inbox rule, hunting for credential-harvest URL clicks or newly registered lookalike domains, writing or reviewing email-phishing detections, or hardening a tenant against spearphishing and illicit consent grants.

0 Updated 5 days ago
umbrasec-labs
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