[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A59SW32RE2HQF0YB22SZC7":3,"skill-same:01M7A59SW32RE2HQF0YB22SZC7":137},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":82,"commitSha":83,"skillDirectory":84,"forksCount":14,"repositoryHtmlUrl":85,"repositoryHomepageUrl":6,"ownerHtmlUrl":86,"ownerBlogUrl":6,"ownerDescription":87,"updatedAt":88,"install":89,"resources":102},"01M7A59SW32RE2HQF0YB22SZC7","conducting-social-engineering-penetration-test",null,"Design and execute a social engineering penetration test combining OSINT-driven target profiling with phishing, vishing, smishing, and physical pretexting campaigns using tools like GoPhish, the Social Engineer Toolkit (SET), and Evilginx to measure human security resilience. Use when scoping or running an authorized human-attack-surface test and reporting results to identify security awareness training gaps.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconducting-social-engineering-penetration-test\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconducting-social-engineering-penetration-test\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: conducting-social-engineering-penetration-test\ndescription: Design and execute a social engineering penetration test combining OSINT-driven target profiling with phishing, vishing, smishing, and physical pretexting campaigns using tools like GoPhish, the Social Engineer Toolkit (SET), and Evilginx to measure human security resilience. Use when scoping or running an authorized human-attack-surface test and reporting results to identify security awareness training gaps.\ndomain: cybersecurity\nsubdomain: penetration-testing\ntags:\n- social-engineering\n- phishing\n- vishing\n- pretexting\n- GoPhish\n- SET\n- OSINT\n- security-awareness\n- red-team\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\natlas_techniques:\n- AML.T0088\n- AML.T0052\nnist_ai_rmf:\n- GOVERN-6.2\n- MAP-5.2\nnist_csf:\n- ID.RA-01\n- ID.RA-06\n- GV.OV-02\n- DE.AE-07\nmitre_attack:\n- T1566\n- T1598\n- T1566.004\n- T1204.001\n- T1589\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - reconnaissance\n  - initial-access\n  - resource-development\n  techniques:\n  - id: T1598\n    name: Phishing for Information\n    tactic: reconnaissance\n    source: attack\n  - id: T1660\n    name: Phishing\n    tactic: initial-access\n    source: attack\n  - id: F1029\n    name: Gather Customer Information\n    tactic: reconnaissance\n    source: f3\n  - id: F1032\n    name: Impersonate Official\n    tactic: initial-access\n    source: f3\n  - id: T1557\n    name: Adversary-in-the-Middle\n    tactic: initial-access\n    source: attack\n  - id: F1020.002\n    name: 'Create Fake Materials: Fake Website'\n    tactic: resource-development\n    source: f3\n---\n\n# Conducting Social Engineering Penetration Test\n\n## Overview\n\nSocial engineering penetration testing assesses an organization's human attack surface through controlled simulation of real-world deception techniques. According to Verizon DBIR 2024, the human element is involved in approximately 68% of all breaches, with phishing remaining the dominant initial access vector. This skill covers phishing, vishing (voice phishing), smishing (SMS phishing), and physical pretexting campaigns using tools like GoPhish, the Social Engineer Toolkit (SET), and Evilginx.\n\n\n## When to Use\n\n- When conducting security assessments that involve conducting social engineering penetration test\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Written authorization from senior management (CISO\u002FCTO)\n- Legal review confirming compliance with local laws (CFAA, GDPR, etc.)\n- Defined scope: target employee groups, attack types, exclusions\n- GoPhish server, domain for phishing infrastructure, VPS\n- OSINT tools: Maltego, theHarvester, LinkedIn scraping tools\n- Coordination with HR and Legal for employee notification post-test\n\n## Phase 1 — OSINT and Target Profiling\n\n### Employee Reconnaissance\n\n```bash\n# Email harvesting\ntheHarvester -d targetcorp.com -b all -l 500 -f harvester_results\n\n# LinkedIn OSINT (manual + tools)\n# Gather: names, roles, departments, email format\n# Identify: new hires, IT admins, finance team, executives\n\n# Email format discovery\n# Check: first.last@, flast@, firstl@\n# Verify with: hunter.io, phonebook.cz, email-checker.net\n\n# Social media OSINT\n# Twitter\u002FX: employees posting about work tools\u002Ffrustrations\n# Facebook: corporate event photos, office layout\n# GitHub: employee repos with corporate email addresses\n\n# Domain intelligence\ndig targetcorp.com MX +short\ndig targetcorp.com TXT +short\n# Check for SPF, DKIM, DMARC records\n# Weak DMARC = easier email spoofing\n\n# Check breach databases (authorized)\n# HaveIBeenPwned API for corporate emails\n# Identify employees with compromised credentials\n```\n\n### Target Selection Matrix\n\n| Group | Count | Pretext | Attack Vector |\n|-------|-------|---------|--------------|\n| Finance | 15 | Invoice approval | Phishing (credential harvest) |\n| IT Help Desk | 8 | Password reset | Vishing |\n| Executives | 5 | Board meeting update | Spear phishing |\n| New Hires (\u003C 90 days) | 12 | HR onboarding form | Phishing (payload) |\n| All Employees | 200 | IT security update | Broad phishing |\n\n## Phase 2 — Phishing Campaign\n\n### Infrastructure Setup\n\n```bash\n# Register lookalike domain\n# targetcorp.com -> targetc0rp.com, targetcorp-secure.com, targetcorp.net\n\n# Set up GoPhish server\nsudo apt install gophish\n# Edit config.json for admin and phishing server ports\ngophish\n\n# Configure sending profile in GoPhish\n# SMTP server: mail.attackdomain.com\n# From: it-security@targetcorp-secure.com\n# Headers: proper DKIM\u002FSPF for attack domain\n\n# Create landing page (credential harvesting)\n# Clone legitimate login page (Office 365, Okta, etc.)\n# GoPhish: Import Site -> https:\u002F\u002Flogin.microsoftonline.com\n# Enable: Capture Credentials, Capture Passwords\n# Redirect to real site after capture\n\n# Set up Evilginx for MFA bypass (authorized testing only)\nevilginx2\n: config domain attackdomain.com\n: config ipv4 \u003Cserver_ip>\n: phishlets hostname o365 login.targetcorp-secure.com\n: phishlets enable o365\n: lures create o365\n: lures get-url 0\n```\n\n### GoPhish Campaign Configuration\n\n```json\n{\n  \"campaign\": {\n    \"name\": \"IT Security Update - Q1 2025\",\n    \"template\": {\n      \"name\": \"Mandatory Security Training\",\n      \"subject\": \"Action Required: Complete Security Awareness Training by Friday\",\n      \"html\": \"\u003Chtml>...[branded email with urgency]...\u003C\u002Fhtml>\",\n      \"from\": \"IT Security Team \u003Csecurity@targetcorp-secure.com>\"\n    },\n    \"landing_page\": \"Office 365 Login Clone\",\n    \"sending_profile\": \"Phishing SMTP\",\n    \"groups\": [\"All Employees - Batch 1\"],\n    \"launch_date\": \"2025-03-10T09:00:00Z\",\n    \"send_by_date\": \"2025-03-10T12:00:00Z\"\n  }\n}\n```\n\n### Phishing Email Templates by Pretext\n\n**Template 1 — IT Security Update:**\n```\nSubject: [Action Required] Mandatory Password Reset - Security Incident\nFrom: IT Security \u003Csecurity@targetcorp-secure.com>\n\nDear {FirstName},\n\nOur security team has detected unauthorized access attempts on our systems.\nAs a precautionary measure, all employees must reset their passwords immediately.\n\nPlease click below to reset your password within the next 24 hours:\n\n[Reset Password Now] -> {phishing_url}\n\nFailure to comply may result in temporary account suspension.\n\nThank you,\nIT Security Team\n```\n\n**Template 2 — Finance Invoice:**\n```\nSubject: Invoice #INV-2025-4821 - Approval Required\nFrom: Accounts Payable \u003Cap@targetcorp-secure.com>\n\nHi {FirstName},\n\nPlease review and approve the attached invoice from our vendor.\nAmount: $47,250.00 | Due: March 15, 2025\n\n[View Invoice] -> {phishing_url}\n\nBest regards,\nAccounts Payable\n```\n\n## Phase 3 — Vishing Campaign\n\n### Call Script Template\n\n```\nPretext: IT Help Desk calling about suspicious login\n\nCaller: \"Hi, this is [Name] from the IT Help Desk. Am I speaking with [Target Name]?\"\n\n[Wait for confirmation]\n\nCaller: \"We've detected some unusual login activity on your account from an\nunrecognized location. For your protection, I need to verify your identity\nbefore we can investigate further.\"\n\nCaller: \"Can you confirm your employee ID and the email address associated\nwith your account?\"\n\n[Record responses]\n\nCaller: \"Thank you. I'm going to send you a verification link to confirm\nit's really you. Can you click on it and enter your credentials so we can\nsecure your account?\"\n\n[Send phishing link via email\u002FSMS during call]\n\nCaller: \"Great, I can see you've been verified. Your account is now secured.\nIf you notice any further issues, please call the help desk at [real number].\"\n```\n\n### Vishing Metrics to Track\n\n| Metric | Description |\n|--------|-------------|\n| Call answered | Target picked up the phone |\n| Engaged | Target continued conversation past initial question |\n| Information disclosed | Target provided credentials, employee ID, or PII |\n| Link clicked | Target clicked the verification link |\n| Credentials entered | Target entered credentials on phishing page |\n| Reported | Target reported the call to security |\n\n## Phase 4 — Physical Social Engineering\n\n### Physical Pretexting Scenarios\n\n```\nScenario 1: Delivery Person\n- Arrive with package labeled for executive\n- Request access to deliver personally\n- Attempt to tailgate through secure doors\n- Drop USB drives in common areas\n\nScenario 2: IT Vendor\n- Arrive with vendor badge (printed)\n- Claim scheduled maintenance on network closet\n- Attempt to access server rooms\n- Install rogue wireless AP if access gained\n\nScenario 3: New Employee\n- Arrive claiming first day orientation\n- Request temporary badge\n- Attempt to access restricted areas\n- Photograph sensitive screens\u002Fdocuments\n\nEvidence Collection:\n- Body camera (if legally permitted and authorized)\n- Photographs of accessed areas\n- WiFi probe from rogue AP\n- Notes on which doors\u002Fcheckpoints bypassed\n```\n\n## Phase 5 — Metrics and Analysis\n\n### Campaign Results Dashboard\n\n```\nPhishing Campaign Results:\n├── Emails Sent: 200\n├── Emails Delivered: 195 (97.5%)\n├── Emails Opened: 142 (72.8%)\n├── Links Clicked: 68 (34.9%)\n├── Credentials Submitted: 31 (15.9%)\n├── MFA Bypassed: 8 (4.1%)  [Evilginx]\n├── Reported to SOC: 12 (6.2%)\n└── No Action: 53 (27.2%)\n\nVishing Campaign Results:\n├── Calls Made: 23\n├── Calls Answered: 18 (78.3%)\n├── Engaged in Conversation: 15 (65.2%)\n├── Information Disclosed: 9 (39.1%)\n├── Credentials Provided: 4 (17.4%)\n└── Reported to Security: 2 (8.7%)\n\nPhysical Assessment:\n├── Tailgating Successful: 3\u002F5 attempts\n├── USB Drives Plugged In: 2\u002F10 dropped\n├── Restricted Areas Accessed: 2\u002F4 attempted\n└── Challenged by Employee: 1 time\n```\n\n### Risk Scoring\n\n| Attack Vector | Success Rate | Risk Level | Priority |\n|--------------|-------------|------------|----------|\n| Phishing (credential harvest) | 15.9% | High | P1 |\n| Vishing (info disclosure) | 39.1% | Critical | P1 |\n| Physical tailgating | 60% | High | P2 |\n| USB drop | 20% | Medium | P3 |\n| Spear phishing (exec) | 40% | Critical | P1 |\n\n## Phase 6 — Reporting and Recommendations\n\n### Remediation Priorities\n\n| Priority | Recommendation | Timeline |\n|----------|---------------|----------|\n| P1 | Deploy phishing-resistant MFA (FIDO2\u002FWebAuthn) | 30 days |\n| P1 | Implement targeted security awareness training | 14 days |\n| P1 | Deploy email gateway with URL rewriting | 30 days |\n| P2 | Strengthen physical access controls (mantraps, visitor badges) | 60 days |\n| P2 | Implement security champion program per department | 30 days |\n| P3 | Deploy USB device control policy | 30 days |\n| P3 | Establish phishing reporting button in email client | 14 days |\n\n## Tools Reference\n\n| Tool | Purpose |\n|------|---------|\n| GoPhish | Phishing campaign management platform |\n| Evilginx2 | MFA bypass via reverse proxy phishing |\n| Social Engineer Toolkit (SET) | Social engineering attack framework |\n| Maltego | OSINT and relationship mapping |\n| theHarvester | Email and domain OSINT |\n| King Phisher | Phishing campaign tool |\n| Modlishka | Reverse proxy for credential interception |\n\n## References\n\n- GoPhish: https:\u002F\u002Fgetgophish.com\u002F\n- Evilginx2: https:\u002F\u002Fgithub.com\u002Fkgretzky\u002Fevilginx2\n- Social Engineer Toolkit: https:\u002F\u002Fgithub.com\u002Ftrustedsec\u002Fsocial-engineer-toolkit\n- Verizon DBIR: https:\u002F\u002Fwww.verizon.com\u002Fbusiness\u002Fresources\u002Freports\u002Fdbir\u002F\n- NIST SP 800-61: Computer Security Incident Handling Guide\n","# Conducting Social Engineering Penetration Test\n\n## Overview\n\nSocial engineering penetration testing assesses an organization's human attack surface through controlled simulation of real-world deception techniques. According to Verizon DBIR 2024, the human element is involved in approximately 68% of all breaches, with phishing remaining the dominant initial access vector. This skill covers phishing, vishing (voice phishing), smishing (SMS phishing), and physical pretexting campaigns using tools like GoPhish, the Social Engineer Toolkit (SET), and Evilginx.\n\n\n## When to Use\n\n- When conducting security assessments that involve conducting social engineering penetration test\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Written authorization from senior management (CISO\u002FCTO)\n- Legal review confirming compliance with local laws (CFAA, GDPR, etc.)\n- Defined scope: target employee groups, attack types, exclusions\n- GoPhish server, domain for phishing infrastructure, VPS\n- OSINT tools: Maltego, theHarvester, LinkedIn scraping tools\n- Coordination with HR and Legal for employee notification post-test\n\n## Phase 1 — OSINT and Target Profiling\n\n### Employee Reconnaissance\n\n```bash\n# Email harvesting\ntheHarvester -d targetcorp.com -b all -l 500 -f harvester_results\n\n# LinkedIn OSINT (manual + tools)\n# Gather: names, roles, departments, email format\n# Identify: new hires, IT admins, finance team, executives\n\n# Email format discovery\n# Check: first.last@, flast@, firstl@\n# Verify with: hunter.io, phonebook.cz, email-checker.net\n\n# Social media OSINT\n# Twitter\u002FX: employees posting about work tools\u002Ffrustrations\n# Facebook: corporate event photos, office layout\n# GitHub: employee repos with corporate email addresses\n\n# Domain intelligence\ndig targetcorp.com MX +short\ndig targetcorp.com TXT +short\n# Check for SPF, DKIM, DMARC records\n# Weak DMARC = easier email spoofing\n\n# Check breach databases (authorized)\n# HaveIBeenPwned API for corporate emails\n# Identify employees with compromised credentials\n```\n\n### Target Selection Matrix\n\n| Group | Count | Pretext | Attack Vector |\n|-------|-------|---------|--------------|\n| Finance | 15 | Invoice approval | Phishing (credential harvest) |\n| IT Help Desk | 8 | Password reset | Vishing |\n| Executives | 5 | Board meeting update | Spear phishing |\n| New Hires (\u003C 90 days) | 12 | HR onboarding form | Phishing (payload) |\n| All Employees | 200 | IT security update | Broad phishing |\n\n## Phase 2 — Phishing Campaign\n\n### Infrastructure Setup\n\n```bash\n# Register lookalike domain\n# targetcorp.com -> targetc0rp.com, targetcorp-secure.com, targetcorp.net\n\n# Set up GoPhish server\nsudo apt install gophish\n# Edit config.json for admin and phishing server ports\ngophish\n\n# Configure sending profile in GoPhish\n# SMTP server: mail.attackdomain.com\n# From: it-security@targetcorp-secure.com\n# Headers: proper DKIM\u002FSPF for attack domain\n\n# Create landing page (credential harvesting)\n# Clone legitimate login page (Office 365, Okta, etc.)\n# GoPhish: Import Site -> https:\u002F\u002Flogin.microsoftonline.com\n# Enable: Capture Credentials, Capture Passwords\n# Redirect to real site after capture\n\n# Set up Evilginx for MFA bypass (authorized testing only)\nevilginx2\n: config domain attackdomain.com\n: config ipv4 \u003Cserver_ip>\n: phishlets hostname o365 login.targetcorp-secure.com\n: phishlets enable o365\n: lures create o365\n: lures get-url 0\n```\n\n### GoPhish Campaign Configuration\n\n```json\n{\n  \"campaign\": {\n    \"name\": \"IT Security Update - Q1 2025\",\n    \"template\": {\n      \"name\": \"Mandatory Security Training\",\n      \"subject\": \"Action Required: Complete Security Awareness Training by Friday\",\n      \"html\": \"\u003Chtml>...[branded email with urgency]...\u003C\u002Fhtml>\",\n      \"from\": \"IT Security Team \u003Csecurity@targetcorp-secure.com>\"\n    },\n    \"landing_page\": \"Office 365 Login Clone\",\n    \"sending_profile\": \"Phishing SMTP\",\n    \"groups\": [\"All Employees - Batch 1\"],\n    \"launch_date\": \"2025-03-10T09:00:00Z\",\n    \"send_by_date\": \"2025-03-10T12:00:00Z\"\n  }\n}\n```\n\n### Phishing Email Templates by Pretext\n\n**Template 1 — IT Security Update:**\n```\nSubject: [Action Required] Mandatory Password Reset - Security Incident\nFrom: IT Security \u003Csecurity@targetcorp-secure.com>\n\nDear {FirstName},\n\nOur security team has detected unauthorized access attempts on our systems.\nAs a precautionary measure, all employees must reset their passwords immediately.\n\nPlease click below to reset your password within the next 24 hours:\n\n[Reset Password Now] -> {phishing_url}\n\nFailure to comply may result in temporary account suspension.\n\nThank you,\nIT Security Team\n```\n\n**Template 2 — Finance Invoice:**\n```\nSubject: Invoice #INV-2025-4821 - Approval Required\nFrom: Accounts Payable \u003Cap@targetcorp-secure.com>\n\nHi {FirstName},\n\nPlease review and approve the attached invoice from our vendor.\nAmount: $47,250.00 | Due: March 15, 2025\n\n[View Invoice] -> {phishing_url}\n\nBest regards,\nAccounts Payable\n```\n\n## Phase 3 — Vishing Campaign\n\n### Call Script Template\n\n```\nPretext: IT Help Desk calling about suspicious login\n\nCaller: \"Hi, this is [Name] from the IT Help Desk. Am I speaking with [Target Name]?\"\n\n[Wait for confirmation]\n\nCaller: \"We've detected some unusual login activity on your account from an\nunrecognized location. For your protection, I need to verify your identity\nbefore we can investigate further.\"\n\nCaller: \"Can you confirm your employee ID and the email address associated\nwith your account?\"\n\n[Record responses]\n\nCaller: \"Thank you. I'm going to send you a verification link to confirm\nit's really you. Can you click on it and enter your credentials so we can\nsecure your account?\"\n\n[Send phishing link via email\u002FSMS during call]\n\nCaller: \"Great, I can see you've been verified. Your account is now secured.\nIf you notice any further issues, please call the help desk at [real number].\"\n```\n\n### Vishing Metrics to Track\n\n| Metric | Description |\n|--------|-------------|\n| Call answered | Target picked up the phone |\n| Engaged | Target continued conversation past initial question |\n| Information disclosed | Target provided credentials, employee ID, or PII |\n| Link clicked | Target clicked the verification link |\n| Credentials entered | Target entered credentials on phishing page |\n| Reported | Target reported the call to security |\n\n## Phase 4 — Physical Social Engineering\n\n### Physical Pretexting Scenarios\n\n```\nScenario 1: Delivery Person\n- Arrive with package labeled for executive\n- Request access to deliver personally\n- Attempt to tailgate through secure doors\n- Drop USB drives in common areas\n\nScenario 2: IT Vendor\n- Arrive with vendor badge (printed)\n- Claim scheduled maintenance on network closet\n- Attempt to access server rooms\n- Install rogue wireless AP if access gained\n\nScenario 3: New Employee\n- Arrive claiming first day orientation\n- Request temporary badge\n- Attempt to access restricted areas\n- Photograph sensitive screens\u002Fdocuments\n\nEvidence Collection:\n- Body camera (if legally permitted and authorized)\n- Photographs of accessed areas\n- WiFi probe from rogue AP\n- Notes on which doors\u002Fcheckpoints bypassed\n```\n\n## Phase 5 — Metrics and Analysis\n\n### Campaign Results Dashboard\n\n```\nPhishing Campaign Results:\n├── Emails Sent: 200\n├── Emails Delivered: 195 (97.5%)\n├── Emails Opened: 142 (72.8%)\n├── Links Clicked: 68 (34.9%)\n├── Credentials Submitted: 31 (15.9%)\n├── MFA Bypassed: 8 (4.1%)  [Evilginx]\n├── Reported to SOC: 12 (6.2%)\n└── No Action: 53 (27.2%)\n\nVishing Campaign Results:\n├── Calls Made: 23\n├── Calls Answered: 18 (78.3%)\n├── Engaged in Conversation: 15 (65.2%)\n├── Information Disclosed: 9 (39.1%)\n├── Credentials Provided: 4 (17.4%)\n└── Reported to Security: 2 (8.7%)\n\nPhysical Assessment:\n├── Tailgating Successful: 3\u002F5 attempts\n├── USB Drives Plugged In: 2\u002F10 dropped\n├── Restricted Areas Accessed: 2\u002F4 attempted\n└── Challenged by Employee: 1 time\n```\n\n### Risk Scoring\n\n| Attack Vector | Success Rate | Risk Level | Priority |\n|--------------|-------------|------------|----------|\n| Phishing (credential harvest) | 15.9% | High | P1 |\n| Vishing (info disclosure) | 39.1% | Critical | P1 |\n| Physical tailgating | 60% | High | P2 |\n| USB drop | 20% | Medium | P3 |\n| Spear phishing (exec) | 40% | Critical | P1 |\n\n## Phase 6 — Reporting and Recommendations\n\n### Remediation Priorities\n\n| Priority | Recommendation | Timeline |\n|----------|---------------|----------|\n| P1 | Deploy phishing-resistant MFA (FIDO2\u002FWebAuthn) | 30 days |\n| P1 | Implement targeted security awareness training | 14 days |\n| P1 | Deploy email gateway with URL rewriting | 30 days |\n| P2 | Strengthen physical access controls (mantraps, visitor badges) | 60 days |\n| P2 | Implement security champion program per department | 30 days |\n| P3 | Deploy USB device control policy | 30 days |\n| P3 | Establish phishing reporting button in email client | 14 days |\n\n## Tools Reference\n\n| Tool | Purpose |\n|------|---------|\n| GoPhish | Phishing campaign management platform |\n| Evilginx2 | MFA bypass via reverse proxy phishing |\n| Social Engineer Toolkit (SET) | Social engineering attack framework |\n| Maltego | OSINT and relationship mapping |\n| theHarvester | Email and domain OSINT |\n| King Phisher | Phishing campaign tool |\n| Modlishka | Reverse proxy for credential interception |\n\n## References\n\n- GoPhish: https:\u002F\u002Fgetgophish.com\u002F\n- Evilginx2: https:\u002F\u002Fgithub.com\u002Fkgretzky\u002Fevilginx2\n- Social Engineer Toolkit: https:\u002F\u002Fgithub.com\u002Ftrustedsec\u002Fsocial-engineer-toolkit\n- Verizon DBIR: https:\u002F\u002Fwww.verizon.com\u002Fbusiness\u002Fresources\u002Freports\u002Fdbir\u002F\n- NIST SP 800-61: Computer Security Incident Handling Guide\n",{"name":5,"tags":25,"author":35,"domain":36,"license":15,"version":37,"mitre_f3":38,"nist_csf":65,"subdomain":70,"description":7,"nist_ai_rmf":71,"mitre_attack":74,"atlas_techniques":79},[26,27,28,29,30,31,32,33,34],"social-engineering","phishing","vishing","pretexting","GoPhish","SET","OSINT","security-awareness","red-team","mahipal","cybersecurity","1.0",{"tactics":39,"version":43,"techniques":44},[40,41,42],"reconnaissance","initial-access","resource-development","1.1",[45,49,52,56,59,62],{"id":46,"name":47,"source":48,"tactic":40},"T1598","Phishing for Information","attack",{"id":50,"name":51,"source":48,"tactic":41},"T1660","Phishing",{"id":53,"name":54,"source":55,"tactic":40},"F1029","Gather Customer Information","f3",{"id":57,"name":58,"source":55,"tactic":41},"F1032","Impersonate Official",{"id":60,"name":61,"source":48,"tactic":41},"T1557","Adversary-in-the-Middle",{"id":63,"name":64,"source":55,"tactic":42},"F1020.002","Create Fake Materials: Fake Website",[66,67,68,69],"ID.RA-01","ID.RA-06","GV.OV-02","DE.AE-07","penetration-testing",[72,73],"GOVERN-6.2","MAP-5.2",[75,46,76,77,78],"T1566","T1566.004","T1204.001","T1589",[80,81],"AML.T0088","AML.T0052","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fconducting-social-engineering-penetration-test","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":90,"prompt":100,"zipAvailable":101},[91,94,97],{"tool":92,"command":93},"npx","npx skills add NeelakshSaxena\u002FVayu --skill conducting-social-engineering-penetration-test",{"tool":95,"command":96},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill conducting-social-engineering-penetration-test",{"tool":98,"command":99},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill conducting-social-engineering-penetration-test","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconducting-social-engineering-penetration-test\u002FSKILL.md",true,[103,109,113,119,123,127,133],{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"assets\u002Ftemplate.md","ASSET","资产文件",1016,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconducting-social-engineering-penetration-test\u002Fassets\u002Ftemplate.md",{"path":110,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":112,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":114,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Fapi-reference.md","REFERENCE","参考文档",1498,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconducting-social-engineering-penetration-test\u002Freferences\u002Fapi-reference.md",{"path":120,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Fstandards.md",958,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconducting-social-engineering-penetration-test\u002Freferences\u002Fstandards.md",{"path":124,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":125,"sourceHtmlUrl":126},"references\u002Fworkflows.md",1147,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconducting-social-engineering-penetration-test\u002Freferences\u002Fworkflows.md",{"path":128,"resourceType":129,"resourceTypeDesc":130,"sizeBytes":131,"sourceHtmlUrl":132},"scripts\u002Fagent.py","SCRIPT","脚本",5926,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconducting-social-engineering-penetration-test\u002Fscripts\u002Fagent.py",{"path":134,"resourceType":129,"resourceTypeDesc":130,"sizeBytes":135,"sourceHtmlUrl":136},"scripts\u002Fprocess.py",7527,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconducting-social-engineering-penetration-test\u002Fscripts\u002Fprocess.py",[138,145,152,159,166,173],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]