Files
Anthropic-Cybersecurity-Skills/skills/conducting-spearphishing-simulation-campaign/SKILL.md
T
mukul975 886658219f Add MITRE Fight Fraud Framework (F3 v1.1) mappings to fraud-relevant skills
- Add mitre_f3 frontmatter block to 94 fraud-relevant skills (phishing,
  account takeover, banking malware, BEC, identity/KYC, payment/card fraud,
  money-mule/cash-out, ransomware extortion, DFIR, threat intel)
- Map each skill to F3 v1.1 tactics + precise technique IDs, including the
  two F3-specific tactics ATT&CK lacks: Positioning (FA0001) and
  Monetization (FA0002)
- All 123 F3 v1.1 technique IDs validated against the upstream STIX bundle
  (github.com/center-for-threat-informed-defense/fight-fraud-framework):
  0 invalid IDs, 0 invalid tactics, 0 name mismatches, no placeholder IDs
- mitre_f3 kept as a separate block from mitre_attack (F3 redefines several
  ATT&CK tactics for the fraud context)
- Add docs/mitre-f3-mapping.md schema reference
- Update README: F3 as the 6th framework, dedicated F3 section + badge
2026-06-20 16:06:04 +02:00

6.3 KiB

name, description, domain, subdomain, tags, version, author, license, d3fend_techniques, nist_csf, mitre_attack, mitre_f3
name description domain subdomain tags version author license d3fend_techniques nist_csf mitre_attack mitre_f3
conducting-spearphishing-simulation-campaign Spearphishing simulation is a targeted social engineering attack vector used by red teams to gain initial access. Unlike broad phishing campaigns, spearphishing uses OSINT-derived intelligence to craf cybersecurity red-teaming
red-team
adversary-simulation
mitre-attack
exploitation
post-exploitation
spearphishing
social-engineering
1.0 mahipal Apache-2.0
File Metadata Consistency Validation
Application Protocol Command Analysis
Identifier Analysis
Content Format Conversion
Message Analysis
ID.RA-01
GV.OV-02
DE.AE-07
T1566.001
T1566.002
T1598.003
T1598.002
T1204.002
T1204.001
version tactics techniques
1.1
reconnaissance
resource-development
initial-access
id name tactic source
T1598 Phishing for Information reconnaissance attack
id name tactic source
T1660 Phishing initial-access attack
id name tactic source
T1583.001 Acquire Infrastructure: Domains resource-development attack
id name tactic source
F1020.002 Create Fake Materials: Fake Website resource-development f3
id name tactic source
T1585 Establish Accounts resource-development attack
id name tactic source
F1006.002 Account Takeover: Exposed Login Credential initial-access f3

Conducting Spearphishing Simulation Campaign

Legal Notice: This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.

Overview

Spearphishing simulation is a targeted social engineering attack vector used by red teams to gain initial access. Unlike broad phishing campaigns, spearphishing uses OSINT-derived intelligence to craft highly personalized messages targeting specific individuals. This skill covers developing pretexts, building payloads, setting up email infrastructure, executing the campaign, and tracking results.

When to Use

  • When conducting security assessments that involve conducting spearphishing simulation campaign
  • When following incident response procedures for related security events
  • When performing scheduled security testing or auditing activities
  • When validating security controls through hands-on testing

Prerequisites

  • Familiarity with red teaming concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

Objectives

  • Develop convincing pretexts tailored to specific target personnel
  • Create weaponized payloads that bypass email security controls
  • Set up email delivery infrastructure with proper SPF/DKIM/DMARC configuration
  • Execute phishing campaigns with real-time tracking and metrics
  • Document results for engagement reporting and security awareness improvement

MITRE ATT&CK Mapping

  • T1566.001 - Phishing: Spearphishing Attachment
  • T1566.002 - Phishing: Spearphishing Link
  • T1566.003 - Phishing: Spearphishing via Service
  • T1598.003 - Phishing for Information: Spearphishing Link
  • T1204.001 - User Execution: Malicious Link
  • T1204.002 - User Execution: Malicious File
  • T1608.001 - Stage Capabilities: Upload Malware
  • T1608.005 - Stage Capabilities: Link Target
  • T1583.001 - Acquire Infrastructure: Domains
  • T1585.002 - Establish Accounts: Email Accounts

Workflow

Phase 1: Pretext Development

  1. Review OSINT findings for target personnel profiles
  2. Identify current organizational events (mergers, projects, new hires)
  3. Select pretext theme (IT helpdesk, HR benefits, vendor communication, executive request)
  4. Craft email templates with appropriate urgency and authority cues
  5. Create landing pages that mirror target organization's branding

Phase 2: Payload Development

  1. Select payload type based on target security controls:
    • HTML smuggling for email gateway bypass
    • Macro-enabled documents (if macros not blocked)
    • ISO/IMG files containing LNK payloads
    • OneNote files with embedded scripts
    • QR codes linking to credential harvesting pages
  2. Test payload against target's known security stack
  3. Implement payload obfuscation techniques
  4. Configure callback to C2 infrastructure

Phase 3: Infrastructure Setup

  1. Register convincing look-alike domain
  2. Age domain and build reputation (minimum 2 weeks recommended)
  3. Configure SPF, DKIM, and DMARC records
  4. Set up SMTP relay with GoPhish or custom mail server
  5. Deploy credential harvesting pages with SSL certificates
  6. Configure tracking pixels and click tracking

Phase 4: Campaign Execution

  1. Send test emails to verify delivery and rendering
  2. Launch campaign in waves (avoid mass sending)
  3. Monitor email delivery rates and opens in real-time
  4. Track link clicks and credential submissions
  5. Deploy payloads to users who interact with phishing emails
  6. Capture screenshots and evidence for reporting

Phase 5: Post-Campaign Analysis

  1. Calculate campaign metrics (delivery rate, open rate, click rate, credential capture rate)
  2. Identify users who reported phishing to SOC
  3. Document bypass of email security controls
  4. Map successful compromises to MITRE ATT&CK
  5. Compile findings for engagement report

Tools and Resources

Tool Purpose License
GoPhish Phishing campaign management Open Source
Evilginx2 Real-time credential harvesting with MFA bypass Open Source
King Phisher Phishing campaign toolkit Open Source
SET (Social Engineering Toolkit) Multi-vector social engineering Open Source
Modlishka Reverse proxy phishing Open Source
CredSniper Credential harvesting framework Open Source
Fierce Phish Phishing framework Open Source

Validation Criteria

  • Pretext tailored to specific targets with OSINT data
  • Payload tested against email security controls
  • Infrastructure configured with proper email authentication
  • Campaign tracked with delivery and interaction metrics
  • Evidence collected for engagement report
  • Cleanup performed on infrastructure post-campaign