conducting-spearphishing-simulation-campaign
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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-08-31
- Stars
- ★ 3.6w
- Forks
- 4.4k
01 前言 Front Matter
- name
- conducting-spearphishing-simulation-campaign
- tags
- [ "red-team", "adversary-simulation", "mitre-attack", "exploitation", "post-exploitation", "spearphishing", "social-engineering" ]
- author
- mahipal
- domain
- cybersecurity
- license
- Apache-2.0
- version
- 1.0
- mitre_f3
- { "tactics": [ "reconnaissance", "resource-development", "initial-access" ], "version": "1.1", "techniques": [ { "id": "T1598", "name": "Phishing for Information", "source": "attack", "tactic": "reconnaissance" }, { "id": "T1660", "name": "Phishing", "source": "attack", "tactic": "initial-access" }, { "id": "T1583.001", "name": "Acquire Infrastructure: Domains", "source": "attack", "tactic": "resource-development" }, { "id": "F1020.002", "name": "Create Fake Materials: Fake Website", "source": "f3", "tactic": "resource-development" }, { "id": "T1585", "name": "Establish Accounts", "source": "attack", "tactic": "resource-development" }, { "id": "F1006.002", "name": "Account Takeover: Exposed Login Credential", "source": "f3", "tactic": "initial-access" } ] }
- nist_csf
- [ "ID.RA-01", "GV.OV-02", "DE.AE-07" ]
- subdomain
- red-teaming
- 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.
- mitre_attack
- [ "T1566.001", "T1566.002", "T1598.003", "T1598.002", "T1204.002", "T1204.001" ]
- d3fend_techniques
- [ "File Metadata Consistency Validation", "Application Protocol Command Analysis", "Identifier Analysis", "Content Format Conversion", "Message Analysis" ]
02 资源文件 7
- 资产文件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
03 SKILL.md 正文
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
- Review OSINT findings for target personnel profiles
- Identify current organizational events (mergers, projects, new hires)
- Select pretext theme (IT helpdesk, HR benefits, vendor communication, executive request)
- Craft email templates with appropriate urgency and authority cues
- Create landing pages that mirror target organization's branding
Phase 2: Payload Development
- 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
- Test payload against target's known security stack
- Implement payload obfuscation techniques
- Configure callback to C2 infrastructure
Phase 3: Infrastructure Setup
- Register convincing look-alike domain
- Age domain and build reputation (minimum 2 weeks recommended)
- Configure SPF, DKIM, and DMARC records
- Set up SMTP relay with GoPhish or custom mail server
- Deploy credential harvesting pages with SSL certificates
- Configure tracking pixels and click tracking
Phase 4: Campaign Execution
- Send test emails to verify delivery and rendering
- Launch campaign in waves (avoid mass sending)
- Monitor email delivery rates and opens in real-time
- Track link clicks and credential submissions
- Deploy payloads to users who interact with phishing emails
- Capture screenshots and evidence for reporting
Phase 5: Post-Campaign Analysis
- Calculate campaign metrics (delivery rate, open rate, click rate, credential capture rate)
- Identify users who reported phishing to SOC
- Document bypass of email security controls
- Map successful compromises to MITRE ATT&CK
- 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
04 同仓库更多 Skills
verifying-build-provenance-with-slsa-sigstore
Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI/CD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.
validating-tpm-measured-boot-attestation
Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote/tpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware/kernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.
validating-backup-integrity-for-recovery
Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable/air-gapped backups for silent corruption or tampering.
triaging-windows-with-kape
Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment/triage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.
triaging-vulnerabilities-with-ssvc-framework
Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track/Track*/Attend/Act decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.
triaging-security-incident
Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM/EDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.