--- name: executing-phishing-simulation-campaign-e19e1cbbd707 description: 'Executes authorized phishing simulation campaigns to assess an organization''s susceptibility to email-based social engineering attacks. The tester designs realistic phishing scenarios, builds credential harvesting infrastructure, sends targeted phishing emails, and tracks open rates, click-through rates, and credential submission rates to measure human security awareness. Activates for requests involving phishing simulation, social engineering assessment, email security testing, or security awareness measurement. ' domain: cybersecurity subdomain: penetration-testing tags: - phishing-simulation - social-engineering - GoPhish - email-security - security-awareness version: 1.0.0 author: mahipal license: Apache-2.0 nist_csf: - ID.RA-01 - ID.RA-06 - GV.OV-02 - DE.AE-07 mitre_attack: - T1595 - T1190 - T1059 - T1078 - T1003 --- # Executing Phishing Simulation Campaign ## When to Use - Measuring employee susceptibility to phishing attacks as part of a security awareness program - Testing the effectiveness of email security controls (secure email gateway, DMARC, SPF, DKIM) - Conducting the social engineering component of a red team exercise to gain initial access - Establishing a baseline for phishing susceptibility before deploying security awareness training - Validating that incident response procedures work when employees report suspicious emails **Do not use** without explicit written authorization from the organization's leadership, for actual credential theft beyond the authorized scope, for targeting individuals personally rather than professionally, or for sending phishing emails that could cause psychological harm or legal liability. ## Prerequisites - Written authorization from executive leadership specifying the campaign scope, target groups, and escalation procedures - Coordination with the IT/security team to whitelist the sending infrastructure (or test whether it bypasses controls, depending on scope) - GoPhish or equivalent phishing platform configured with a sending domain, SMTP relay, and landing page infrastructure - Phishing domain registered and configured with SPF, DKIM, and DMARC records to maximize deliverability - Employee email list from HR, organized by department for targeted campaigns - Incident response team briefed on the campaign timeline and escalation procedures ## Workflow ### Step 1: Campaign Planning and Pretext Development Design realistic phishing scenarios based on threats relevant to the target organization: - **Pretext selection**: Choose scenarios that mirror real-world attacks: - IT support: Password expiration notice requiring immediate action - HR department: Benefits enrollment, policy acknowledgment, W-2/tax document - Executive impersonation: Urgent request from CEO/CFO to review a document - Vendor/supplier: Invoice requiring review, delivery notification - Cloud services: Microsoft 365 shared document, Google Drive access, Zoom meeting invitation - **Target segmentation**: Divide employees into groups by department, role, or access level. High-value targets (finance, IT admin, executives) may receive more sophisticated pretexts. - **Timing**: Schedule sends during business hours, preferably Tuesday-Thursday when email engagement is highest. Avoid holidays, mass layoff periods, or other sensitive times. - **Success metrics**: Define what constitutes campaign success: email open rate, link click rate, credential submission rate, report rate (employees who report the phish to IT) ### Step 2: Infrastructure Setup Configure the phishing infrastructure: - **Domain registration**: Register a domain that resembles the target organization's domain (typosquatting, homograph, or brand-adjacent). Examples: `target-corp.com`, `targetcorp-portal.com`, `targetsupport.net` - **SSL certificate**: Obtain a TLS certificate for the phishing domain (Let's Encrypt) to display the padlock icon - **GoPhish configuration**: - Set up the GoPhish server on a VPS with the phishing domain - Configure the SMTP sending profile with the phishing domain's mail server - Create the email template with tracking pixel and link to the landing page - Build the credential harvesting landing page that mirrors the target's login portal - Import the target email list and create user groups - **Email authentication**: Configure SPF, DKIM, and DMARC records for the phishing domain to pass email authentication checks and improve delivery rates - **Test delivery**: Send test emails to a controlled inbox to verify rendering, link tracking, and landing page functionality ### Step 3: Campaign Execution Launch the phishing campaign: - Send emails in batches to avoid triggering rate limits or spam filters (e.g., 50 emails per hour) - Monitor GoPhish dashboard in real-time for delivery failures, bounces, and early interactions - Track metrics as they come in: emails sent, emails opened (tracking pixel fired), links clicked, credentials submitted - If the IT security team or SOC detects the campaign (if this is part of the test), document the detection time and response actions - Maintain an emergency stop procedure: if an employee becomes distressed or the campaign creates unintended consequences, pause immediately - Run the campaign for 48-72 hours before closing the landing page, as most interactions occur within the first 24 hours ### Step 4: Credential Capture and Access Demonstration Process captured credentials to demonstrate impact (if authorized): - Review all captured credentials in GoPhish. Do not test credentials against real systems unless explicitly authorized. - If authorized for full exploitation: test captured credentials against the organization's actual login portal (VPN, OWA, SSO) - Document any accounts that were successfully compromised, what data they could access, and whether MFA was present - If MFA blocks access, document that MFA prevented the compromise and recommend maintaining MFA enforcement - Identify patterns in credential submissions: which departments, roles, or locations are most susceptible ### Step 5: Analysis and Reporting Analyze campaign results and produce the assessment report: - **Metrics analysis**: - Email delivery rate: percentage of emails that reached inboxes - Open rate: percentage of recipients who opened the email - Click rate: percentage who clicked the phishing link - Submission rate: percentage who submitted credentials - Report rate: percentage who reported the email to IT security - **Departmental comparison**: Compare susceptibility rates across departments to identify groups needing targeted training - **Email security effectiveness**: Document whether the phishing emails bypassed the secure email gateway, whether DMARC/SPF prevented delivery, and whether link scanning tools detected the phishing URL - **Recommendations**: Provide actionable recommendations including security awareness training topics, technical controls improvements, and policy changes ## Key Concepts | Term | Definition | |------|------------| | **Pretext** | The fabricated scenario and social context used to persuade the target to take a desired action such as clicking a link or entering credentials | | **Credential Harvesting** | Collecting usernames and passwords through fake login pages that mimic legitimate services | | **GoPhish** | Open-source phishing simulation platform that manages email templates, landing pages, target groups, and campaign tracking | | **Spear Phishing** | Targeted phishing directed at specific individuals using personalized information gathered through reconnaissance | | **Typosquatting** | Registering domains that are visually similar to legitimate domains through character substitution, addition, or omission | | **Security Awareness** | Training programs designed to educate employees about social engineering threats and proper reporting procedures | | **DMARC** | Domain-based Message Authentication, Reporting, and Conformance; email authentication protocol that prevents unauthorized use of a domain for sending email | ## Tools & Systems - **GoPhish**: Open-source phishing simulation framework providing campaign management, email templates, landing pages, and detailed analytics - **Evilginx2**: Advanced phishing framework capable of capturing session tokens and bypassing multi-factor authentication through reverse proxy technique - **King Phisher**: Phishing campaign toolkit with advanced features including two-factor authentication testing and geolocation tracking - **SET (Social Engineering Toolkit)**: Framework for social engineering attacks including phishing, credential harvesting, and payload delivery ## Common Scenarios ### Scenario: Enterprise Phishing Simulation for Security Awareness Baseline **Context**: A 2,000-employee company has never conducted a phishing simulation. The CISO wants to establish a baseline susceptibility rate before deploying a new security awareness training program. The campaign should test all employees using a realistic but not overly sophisticated pretext. **Approach**: 1. Develop a Microsoft 365 password expiration pretext: "Your password expires in 24 hours. Click here to update." 2. Register `m365-targetcorp.com`, set up GoPhish, and build a landing page cloning the Microsoft 365 login portal 3. Import all 2,000 employee emails and schedule sends in batches of 100 over 20 hours 4. Campaign results after 72 hours: 1,847 delivered (92.4%), 1,243 opened (67.3%), 487 clicked (26.4%), 312 submitted credentials (16.9%), 23 reported to IT (1.2%) 5. Analysis reveals Finance (28% submission) and Marketing (24% submission) have the highest susceptibility; IT department has the lowest (4%) 6. Recommend targeted training for high-susceptibility departments, phishing report button deployment, and quarterly simulation cadence **Pitfalls**: - Using overly aggressive or threatening pretexts that cause employee anxiety or legal issues - Not coordinating with HR and legal before launching the campaign, risking employee relations problems - Sending all emails simultaneously, overwhelming the email server or triggering bulk-send detection - Focusing only on click and submission rates while ignoring the critically low report rate (1.2%) ## Output Format ``` ## Phishing Simulation Campaign Report **Campaign Name**: Q4 2025 Baseline Phishing Assessment **Pretext**: Microsoft 365 Password Expiration Notice **Campaign Duration**: November 15-18, 2025 **Target Population**: 2,000 employees (all departments) ### Campaign Metrics | Metric | Count | Rate | |--------|-------|------| | Emails Sent | 2,000 | 100% | | Emails Delivered | 1,847 | 92.4% | | Emails Opened | 1,243 | 67.3% | | Links Clicked | 487 | 26.4% | | Credentials Submitted | 312 | 16.9% | | Reported to IT | 23 | 1.2% | ### Department Breakdown | Department | Employees | Clicked | Submitted | Reported | |------------|-----------|---------|-----------|----------| | Finance | 120 | 38.3% | 28.3% | 0.8% | | Marketing | 85 | 35.3% | 24.7% | 1.2% | | Engineering| 300 | 15.0% | 8.3% | 3.7% | | IT | 45 | 8.9% | 4.4% | 11.1% | ### Key Findings 1. Baseline credential submission rate of 16.9% exceeds industry average (12%) 2. Report rate of 1.2% indicates employees are not trained to report suspicious emails 3. Finance department is the highest-risk group with 28.3% credential submission rate 4. Email security gateway did not flag the phishing domain despite being registered 48 hours prior ### Recommendations 1. Deploy mandatory security awareness training with emphasis on phishing identification 2. Install a phishing report button in email clients and train all employees on its use 3. Implement DMARC enforcement (p=reject) and enhanced email filtering rules 4. Conduct targeted training for Finance and Marketing departments 5. Schedule quarterly phishing simulations to track improvement ``` --- Source attribution: 26zl Original project: https://github.com/26zl/cybersec-toolkit/blob/2ad2519d437cda1f8a822ef7adc336993601a5ac/.claude/skills/executing-phishing-simulation-campaign/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Dave AI resource metadata Creator / publisher: 26zl Original project: https://github.com/26zl/cybersec-toolkit/blob/2ad2519d437cda1f8a822ef7adc336993601a5ac/.claude/skills/executing-phishing-simulation-campaign/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Marketing, Sales Roles: Customer Success Manager, PR & Communications, Security Engineer Specialties: Specialty not specified Tools: Gophish Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 13c752193770c2d6dcd1bd7f58159b5e543503b06ea833c44af70c594ea49a3e