Phishing Techniques Research for Hunting Development
Analysis of recent phishing campaign tradecraft, attack vectors, TTPs, and hunting development guidance
Executive Summary
Recent phishing campaigns increasingly abuse trusted identity and collaboration workflows rather than relying only on fake credential pages. The most important shift is from credential theft to session and token theft, followed by cloud API misuse for mailbox and SaaS data collection.
For hunting development, behavior-based detection should be prioritized over campaign-specific indicators. Correlated detections across email, identity, endpoint, and cloud telemetry produce higher confidence and stronger resilience against rapid attacker infrastructure rotation.
Scope and Method
This report synthesizes publicly documented campaigns from 2024 through 2026, with emphasis on:
Device code phishing
Adversary-in-the-middle phishing kits
OAuth consent and client identity abuse
QR phishing and staged redirect chains
ClickFix command-paste phishing and fake verification lures
Teams and phone social engineering with remote support abuse
Rogue RDP attachment lures
Campaign Snapshot
Campaign or Cluster
Timeframe
Primary Targets
Core Technique Pattern
Hunt Priority
Storm-2372 device code phishing
2024 to 2026
Government, NGO, IT, defense, telecom, health
User lured to legitimate device sign-in flow, token theft and mailbox access
Critical
Multi-stage code-of-conduct AiTM campaign
2026
Broad enterprise, heavy US targeting
PDF lure, CAPTCHA staging, token interception
Critical
Tycoon2FA ecosystem
2025 to 2026
Cross-sector
Phishing as a service, session cookie and token theft
Click events leading to staged redirect and suspicious sign-in
Voice Phishing
T1566.004
High
External support impersonation and rapid remote tool usage
User Execution
T1204
High
User-triggered click, code entry, or remote session acceptance
Steal Application Access Token
T1528
High
Device and OAuth token misuse patterns
Use Alternate Authentication Material
T1550
High
Session cookie and token reuse from anomalous contexts
Valid Accounts
T1078
High
Authenticated cloud activity with abnormal context
Remote Email Collection
T1114.002
High
Mail API-heavy access and export behavior
Account Manipulation
T1098
Medium to High
Inbox rules, MFA changes, persistence actions
PowerShell
T1059.001
High
ClickFix and post-phish download chains commonly invoke PowerShell
Visual Basic
T1059.005
Medium to High
ClickFix follow-on stages frequently use VBS loaders and scheduled execution
Signed Binary Proxy Execution
T1218
Medium
mshta, rundll32, msbuild, regasm, and similar LOLBins are common execution pivots
Scheduled Task
T1053.005
Medium to High
Hidden task creation appears in documented ClickFix follow-on chains
Exfiltration Over Web Service
T1567
High
API and cloud channel data export spikes
Remote Services RDP
T1021.001
High
RDP file lure to suspicious endpoint execution
Attack Flow Details
Flow A: Device Code Phishing to Cloud Data Access
Device code phishing abuses legitimate authorization flows to gain cloud access.
Flow B: AiTM Credential and Session Interception
NovaCookies delivery paths converge on a live Microsoft 365 relay and session replay.
Flow C: Email Bombing and Teams Vishing Intrusion
Email bombing creates urgency before a fake support operator requests interactive access.
Flow D: OAuth Consent Abuse to SaaS Data Exfiltration
flowchart TD
A[Phishing Lure or Trusted App Pretext] --> B[User Opens Consent Link]
B --> C[OAuth App Requests Permissions]
C --> D[User Grants Consent to Malicious or Spoofed App]
D --> E[Adversary Receives Access and Refresh Tokens]
E --> F[API Access to Mailbox or SaaS Data]
F --> G[Persistence Through Reusable App Trust]
G --> H[Search, Collection, and Export Activity]
Flow E: ClickFix Fake Verification to Endpoint Payload Execution
ClickFix coaches the victim to paste attacker-controlled code into a native interpreter.
Flow F: Rogue RDP Attachment to Remote Session
A trusted-looking RDP file causes the endpoint to initiate an attacker-directed session.
ClickFix Research Findings
ClickFix is now a distinct phishing-adjacent social engineering technique rather than a niche variation of fake CAPTCHA delivery. The defining behavior is not the lure itself, but the deliberate transfer of execution responsibility to the user. Instead of relying on a browser exploit or direct file open, the adversary manipulates the user into pasting a command into Windows Run, PowerShell, Windows Terminal, or another trusted interface.
Microsoft observed the technique growing sharply from early 2024 through 2025, with campaigns delivering DarkGate, MintsLoader, Lumma Stealer, ScreenConnect, Lampion, and other follow-on payloads. Public reporting also showed state-aligned actors adopting the pattern, which matters because it demonstrates that ClickFix is no longer limited to commodity malware operations.
ClickFix Attack Characteristics
Stage
Observed Pattern
Hunting Relevance
Arrival
Phishing email, malvertising redirect, or compromised website
Email and web telemetry both matter
Lure
Fake Cloudflare Turnstile, reCAPTCHA, browser error, Word error, or social platform verification
Browser artifacts and landing-page themes can cluster campaigns
User coercion
Clipboard copy plus step-by-step instructions to press Win+R or open Terminal
Human-driven execution leaves distinct registry and process traces
Same recipient with click event in short time window
Sign-In Anomaly
Surface credential or token misuse
New geolocation, unusual user agent, interrupted then successful sequence
Consent and App Abuse
Detect OAuth trust exploitation
New app consent, high privilege scopes, blank app naming, client ID anomalies
Post-auth Cloud Abuse
Detect data access misuse
Sudden increase in read, search, export, or report operations
User-Executed LOLBin Chain
Detect ClickFix-style execution
explorer.exe parentage, RunMRU writes, PowerShell or mshta with encoded download behavior
Endpoint Follow-on
Catch operator activity
Remote assistance tooling plus scripting process lineage
Detection Engineering Notes
Prefer time-window joins across identity, email, endpoint, and cloud telemetry instead of single-table detections
Treat campaign-specific domains, IPs, and hashes as temporary enrichment only
Model normal user device and sign-in patterns to improve anomaly precision
Score detections using weighted evidence from multiple phases rather than binary matches
Add suppression for known enterprise automations and approved third-party SaaS integrations
For ClickFix, prioritize user-initiated execution traces such as RunMRU writes, explorer.exe parentage, clipboard-driven command artifacts, and encoded LOLBin execution
Suggested Content for Hunt Playbooks
Playbook Section
Recommended Content
Trigger Condition
Multi-signal threshold crossed across delivery, identity, and cloud activity