Skip to content
cccskills
FreePublished on GitHub

conducting-spearphishing-simulation-campaign

Plan authorized spearphishing simulations, personalized phishing tests aimed at specific people. Prepare scenarios and email infrastructure, track delivery and participant responses, and document findings to assess email security controls and improve security awareness.

OriginalShow the original description

Run a targeted spearphishing simulation for initial access by developing OSINT-derived pretexts, building payloads (HTML smuggling, macro docs, ISO/LNK, OneNote, QR codes), standing up look-alike-domain email infrastructure with SPF/DKIM/DMARC via GoPhish, and tracking results. Use in authorized engagements to gain initial access via personalized phishing against specific individuals, distinct from broad campaigns.

Run score Not tested

See how to install

Good for

  • Designing authorized phishing simulations for specific personnel
  • Preparing test email delivery infrastructure
  • Measuring delivery, opens, clicks, and reporting behavior
  • Reporting security control findings and awareness training needs

Files included (8)

  • SKILL.md6.5 KB
  • assets/template.md4.4 KB
  • LICENSE11.0 KB
  • references/api-reference.md1.6 KB
  • references/standards.md2.9 KB
  • references/workflows.md6.6 KB
  • scripts/agent.py5.0 KB
  • scripts/process.py21.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

ToolPurposeLicense
GoPhishPhishing campaign managementOpen Source
Evilginx2Real-time credential harvesting with MFA bypassOpen Source
King PhisherPhishing campaign toolkitOpen Source
SET (Social Engineering Toolkit)Multi-vector social engineeringOpen Source
ModlishkaReverse proxy phishingOpen Source
CredSniperCredential harvesting frameworkOpen Source
Fierce PhishPhishing frameworkOpen 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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Assess exposure of Windows secrets protected by DPAPI, the operating system’s data protection service, during authorized security tests. Guide examination and decryption of saved credentials and browser data using available user sessions, credentials, or backup keys.

  • Assessing saved credential exposure in authorized tests
  • Examining collected DPAPI files offline
  • Reviewing protected browser and RDP credentials
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Assess Shadow Credentials account takeover during authorized Active Directory testing. Examine permissions that allow public key registration, validate authentication without a password reset, and document credential cleanup, detection opportunities, and access control changes needed for remediation.

  • Assessing risky permissions identified in BloodHound
  • Validating account takeover without resetting a password
  • Generating directory change records during security exercises
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Prepare for CMMC Level 2, a cybersecurity certification for defense contractors. Define the systems handling controlled information, review security requirements, calculate the SPRS assessment score, and organize remediation plans and evidence into a readiness report.

  • Define the assessment scope for systems handling controlled information
  • Calculate an SPRS score and prioritize unmet security requirements
  • Prepare security plans, remediation milestones, and assessment evidence
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Create disk images for investigations using dd or dcfldd on Linux. The workflow covers write protection, bit-for-bit copying, hash checks to verify integrity, and documentation of the acquisition process.

  • Preserving a suspect drive before investigation
  • Creating evidence copies of USB devices or memory cards
  • Verifying that a disk image matches its source
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Review Active Directory permissions with ldap3, a Python library for directory queries. Identify excessive access granted to non-administrative accounts, explain potential privilege escalation paths, and produce a JSON report with affected objects and remediation recommendations.

  • Auditing excessive Active Directory permissions
  • Investigating privilege escalation paths from ordinary accounts
  • Reporting affected objects and permission remediation recommendations
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Inspect suspicious Android APK files without running them. Analyze permissions, app components, suspicious code patterns, and network indicators, then produce a JSON risk report to support malware triage and detection rule development.

  • Triage suspicious APK files without running them
  • Inspect dangerous permission combinations and suspicious API calls
  • Extract network indicators for malware detection rules
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

See all skills by mukul975

Report a problem with this skill