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
What this skill does
# 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
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".