conducting-phishing-incident-response

Investigates phishing emails, extracts indicators, purges malicious messages, and remediates compromised accounts.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill conducting-phishing-incident-response
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conducting-phishing-incident-response
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/incident-response/conducting-phishing-incident-response
Command: npx skills add https://github.com/xalgord/xalgorix --skill conducting-phishing-incident-response

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a phishing email reaches users, responders must quickly determine who received it, who clicked, and whose credentials were stolen, then purge the message and secure accounts before attackers exploit stolen sessions. This Skill provides a structured end-to-end workflow for triaging reported phishing emails, scoping impact, containing the threat, and remediating compromised accounts.

Core Features & Use Cases

  • Email Triage and Header Analysis: Classify reported emails using SPF, DKIM, DMARC, Return-Path, and Received header inspection to confirm phishing versus spam or false reports.
  • Impact Scoping and Containment: Search all mailboxes via Microsoft 365 Content Search or Google Workspace investigation tools, cross-reference proxy and EDR telemetry, then purge messages and block sender domains, URLs, and attachment hashes.
  • Account Remediation: Reset passwords, revoke sessions and OAuth tokens, remove malicious inbox forwarding rules, and verify MFA for users who entered credentials, including AiTM (Evilginx-style) session theft scenarios.
  • Use Case: A user reports a QR-code email claiming MFA re-enrollment is required. Follow the workflow to decode the QR URL in a sandbox, identify the AiTM credential harvester, find all 47 recipients, purge the email, revoke sessions for the 3 users who entered credentials, and produce a structured incident report.

Quick Start

Respond to the reported phishing email in the attached EML file by analyzing its headers, scoping affected mailboxes, and generating a containment and remediation plan.

Frequently Asked Questions about conducting-phishing-incident-response

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I respond to a reported phishing email?

Extract the email as an EML or MSG file, analyze headers for SPF, DKIM, and DMARC failures, and detonate URLs or attachments in a sandbox. Then scope all recipients, purge the message from mailboxes, and reset credentials with session revocation for affected users.

How to purge a phishing email from all Microsoft 365 mailboxes?

Use Content Search with precise criteria such as sender, URL, and message-ID, then perform a hard delete rather than soft delete. Confirm zero remaining copies across all mailboxes, including Sent and forwarded copies, before closing containment.

Why is password reset alone not enough after credential phishing?

Adversary-in-the-middle kits like Evilginx steal session cookies, so attackers stay logged in after a password change. You must also revoke all refresh tokens and sign-in sessions, re-verify MFA, and check for malicious inbox rules and OAuth grants.

Can this workflow handle QR code phishing and AiTM attacks?

Yes, it covers quishing by decoding QR images and detonating the extracted URL in a sandbox, since standard URL scanners cannot read QR codes. It also addresses AiTM phishing that captures session tokens despite MFA.

When should I not use this phishing response procedure?

Do not use it for business email compromise involving compromised internal accounts, which requires account takeover investigation procedures instead. It is designed for inbound phishing emails reported by users or detected by email gateways.