What it does. Plan and execute authorized vishing (voice phishing) pretext calls to Part of mukul975/Anthropic-Cybersecurity-Skills (817 security skills) (mukul975/Anthropic-Cybersecurity-Skills).

Upstream	mukul975/Anthropic-Cybersecurity-Skills
Skill file	skills/conducting-social-engineering-pretext-call/SKILL.md
License	Apache-2.0 (skill folder LICENSE)
Author	mukul975
Fetched	2026-09-10

Install

• npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill conducting-social-engineering-pretext-call, or copy the skill folder into ~/.claude/skills/conducting-social-engineering-pretext-call/.
• Raw file: curl -sL https://raw.githubusercontent.com/mukul975/Anthropic-Cybersecurity-Skills/HEAD/skills/conducting-social-engineering-pretext-call/SKILL.md

SKILL.md (verbatim)

name: conducting-social-engineering-pretext-call
description: Plan and execute authorized vishing (voice phishing) pretext calls to
  assess employee susceptibility to social engineering and evaluate security awareness
  controls.
domain: cybersecurity
subdomain: red-teaming
tags:
- social-engineering
- vishing
- pretext-call
- security-awareness
- red-team
- phishing
- human-risk
version: '1.0'
author: mahipal
license: Apache-2.0
atlas_techniques:
- AML.T0088
- AML.T0052
nist_ai_rmf:
- GOVERN-6.2
- MAP-5.2
d3fend_techniques:
- File Metadata Consistency Validation
- Application Protocol Command Analysis
- Identifier Analysis
- Content Format Conversion
- Message Analysis
nist_csf:
- ID.RA-01
- GV.OV-02
- DE.AE-07
mitre_attack:
- T1598.004
- T1566.004
- T1589
- T1591
- T1598
mitre_f3:
  version: '1.1'
  tactics:
  - reconnaissance
  - initial-access
  - stealth
  techniques:
  - id: T1598
    name: Phishing for Information
    tactic: reconnaissance
    source: attack
  - id: F1034
    name: Interactive Voice Response Mapping
    tactic: reconnaissance
    source: f3
  - id: F1029
    name: Gather Customer Information
    tactic: reconnaissance
    source: f3
  - id: F1032
    name: Impersonate Official
    tactic: initial-access
    source: f3
  - id: F1040
    name: Phone Number Spoofing
    tactic: stealth
    source: f3
  - id: F1040.002
    name: 'Phone Number Spoofing: Official Phone Number Spoofing'
    tactic: stealth
    source: f3

Conducting Social Engineering Pretext Call

Overview

A pretext call (vishing) is a social engineering technique where an attacker impersonates a trusted authority figure over the phone to manipulate targets into divulging sensitive information, performing actions, or granting access. In red team engagements, pretext calls test the human element of security controls, measuring employee adherence to verification procedures and security awareness training effectiveness. MITRE ATT&CK maps this to T1566.004 (Phishing for Information: Voice) and T1598 (Phishing for Information).

When to Use

• When conducting security assessments that involve conducting social engineering pretext call
• 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

• Written authorization specifying social engineering scope and boundaries
• List of approved target employees (usually provided by client)
• OSINT research on targets and organization
• Spoofed caller ID capability (authorized for testing)
• Call recording equipment (with legal consent as required)
• Pretext scenarios approved by client

MITRE ATT&CK Mapping

Technique ID	Name	Tactic
T1566.004	Phishing: Voice	Initial Access
T1598	Phishing for Information	Reconnaissance
T1598.003	Phishing for Information: Spearphishing Voice	Reconnaissance
T1589	Gather Victim Identity Information	Reconnaissance
T1591	Gather Victim Org Information	Reconnaissance

Phase 1: OSINT and Target Research

# LinkedIn employee enumeration
theHarvester -d targetcorp.com -b linkedin -l 200

# Company org chart and employee roles
# Review LinkedIn, corporate website "About Us" / "Team" pages

# Technology stack identification
# Check job postings for technology references (VPN vendor, email, helpdesk tool)

# Phone system identification
# Call main line, note IVR options, department names, extension patterns

Key intelligence to gather:

• Internal helpdesk phone number and procedures
• IT department names and staff
• VPN/remote access vendor (Cisco AnyConnect, Fortinet, Pulse Secure)
• Corporate email format (first.last, flast, etc.)
• Recent events (mergers, office moves, system upgrades)
• Employee names, titles, departments

Phase 2: Pretext Development

Common Pretext Scenarios

IT Helpdesk Impersonation (Most Effective):

"Hi, this is [name] from the IT Service Desk. We're migrating everyone to the new VPN client this week, and I see your account hasn't been updated yet. I need to verify your current credentials to ensure the migration goes smoothly. Can you confirm your username and current password?"

Vendor/Contractor:

"Hi, I'm [name] from [known vendor]. We're doing an emergency patch deployment for [product] and I need remote access to your system. Could you help me connect via TeamViewer?"

Executive Assistant (Authority):

"This is [name] calling on behalf of [CFO name]. [He/She] needs an urgent wire transfer processed for a deal that's closing today. I'll email you the details, but we need this done in the next hour."

Building/Facilities:

"Hi, this is [name] from facilities management. We're updating the badge access system this weekend. I need to confirm your employee ID and current badge number so your access isn't interrupted."

Pretext Checklist

• Is the pretext believable for this organization?
• Does it create appropriate urgency without being threatening?
• Does it align with OSINT findings (real dept names, real systems)?
• Does it have a plausible reason for requesting information?
• Is there a fallback if the target pushes back?
• Has the client approved this specific pretext?

Phase 3: Call Execution

Call Structure

1. Introduction (10 seconds): State name, department, reason for calling
2. Building rapport (30 seconds): Reference something real (recent event, shared context)
3. Authority establishment (20 seconds): Reference manager name, ticket number, urgency
4. Information request (30 seconds): Ask for the target information naturally
5. Handling objections: If challenged, respond calmly with prepared answers
6. Closing (10 seconds): Thank them, leave no suspicion

Objection Handling

Objection	Response
"Can I call you back?"	"Of course, call the main helpdesk line and ask for [name]. But this needs to be done by EOD."
"I need to verify this"	"Absolutely, I appreciate your diligence. You can check with [manager name]."
"I was told never to give passwords"	"You're right, and normally we wouldn't ask. This is a special case because [reason]. I can have my manager call you."
"What's your employee ID?"	Pivot: "It's [made-up ID]. Listen, I have 50 more people to call today. Can we just get this done?"
"I'll email IT instead"	"Sure, but the system migration happens tonight. If it's not done by then..."

Phase 4: Data Collection and Metrics

Track the following for each call:

Metric	Description
Target Name	Employee called
Department	Target's department
Date/Time	When call was made
Duration	Length of call
Pretext Used	Which scenario
Information Obtained	What was disclosed
Credential Disclosed	Yes/No (and type)
Verification Attempted	Did target try to verify caller?
Reported to Security	Did target report the call?
Social Engineering Score	1-5 susceptibility rating

Phase 5: Reporting

Success Metrics

Metric	Target	Result
Credential Disclosure Rate	<10%	XX%
Sensitive Info Disclosure Rate	<20%	XX%
Verification Rate	>80%	XX%
Security Reporting Rate	>50%	XX%

Ethical and Legal Considerations

1. Always obtain written authorization before conducting vishing tests
2. Never use threatening language or create genuine fear
3. Document consent and legal requirements for call recording
4. Protect disclosed credentials - immediately report to client
5. Debrief targets after the engagement if client approves
6. Never publicly identify specific employees who failed
7. Comply with telecommunications laws in your jurisdiction

References

• Verizon DBIR 2025: 74% of breaches involve human element
• MITRE ATT&CK T1598: https://attack.mitre.org/techniques/T1598/
• Social Engineering Penetration Testing by Gavin Watson (Syngress)
• The Art of Deception by Kevin Mitnick (Wiley)
• NIST SP 800-50: Building an Information Technology Security Awareness and Training Program

Other files in this skill

• LICENSE
• assets/template.md
• references/api-reference.md
• references/standards.md
• references/workflows.md
• scripts/agent.py
• scripts/process.py

assets/template.md (verbatim)

Vishing Assessment Report Template

Engagement Details

Field	Value
Campaign ID	VISH-YYYY-XXX
Client	[Organization]
Period	YYYY-MM-DD to YYYY-MM-DD
Total Targets	XX employees
Pretext(s) Used	[List of pretexts]
Assessor	[Name]

Executive Summary

[Organization] engaged [Company] to conduct a vishing assessment targeting XX employees across XX departments. The assessment measured employee susceptibility to social engineering pretext calls, specifically testing credential disclosure, verification procedures, and incident reporting behaviors.

Results Summary

Metric	Result	Benchmark	Status
Credential Disclosure Rate	XX%	<10%	Pass/Fail
Sensitive Info Disclosure Rate	XX%	<20%	Pass/Fail
Caller Verification Rate	XX%	>80%	Pass/Fail
Security Reporting Rate	XX%	>50%	Pass/Fail

Call Log

#	Target	Dept	Pretext	Cred Disclosed	Verified	Reported
1	[Name]	[Dept]	[Pretext]	Yes/No	Yes/No	Yes/No
2	[Name]	[Dept]	[Pretext]	Yes/No	Yes/No	Yes/No

Department Risk Scores

Department	Targets	Disclosure Rate	Risk Level
Finance	XX	XX%	Critical/High/Medium/Low
HR	XX	XX%	Critical/High/Medium/Low
IT	XX	XX%	Critical/High/Medium/Low

Recommendations

Immediate (0-30 days)

1. Implement mandatory callback verification for credential requests
2. Issue security bulletin about vishing threats

Short-Term (30-90 days)

1. Deploy role-based security awareness training
2. Establish easy suspicious-call reporting mechanism
3. Conduct targeted training for high-risk departments

Long-Term (90+ days)

1. Implement quarterly vishing simulations
2. Integrate vishing metrics into security KPIs
3. Develop department-specific verification procedures

references/api-reference.md (verbatim)

Social Engineering Pretext Call — API Reference

Libraries

Library	Install	Purpose
requests	pip install requests	API integration with tracking platforms
twilio	pip install twilio	Programmatic phone call management
jinja2	pip install Jinja2	Pretext script template rendering

Pretext Call Phases

Phase	Description
Reconnaissance	Research target name, role, department, reporting chain
Pretext Development	Create believable scenario and script
Call Execution	Make the call, follow script, adapt to responses
Documentation	Record outcome, information obtained, duration
Analysis	Calculate success rates, identify vulnerable departments

Success Criteria Categories

Category	Description
Full Success	Target provided credentials, access, or completed action
Partial Success	Target revealed organizational info but not credentials
Failed	Target refused or became suspicious
Reported	Target reported the call to security team

Key Metrics

Metric	Formula
Success Rate	successful_calls / total_calls x 100
Report Rate	calls_reported_to_security / total_calls x 100
Avg Call Duration	total_duration / total_calls
Dept Vulnerability	dept_successes / dept_total x 100

Legal Considerations

Requirement	Description
Written Authorization	Signed Rules of Engagement from client
Recording Consent	Follow state/jurisdiction recording laws
Scope Boundaries	Only call authorized targets
Data Handling	Securely store any obtained credentials, delete after report

External References

• Social Engineering Framework
• PTES Pre-engagement Guidelines
• Twilio Voice API

references/standards.md (verbatim)

Standards and References: Social Engineering Pretext Call

MITRE ATT&CK Techniques

• T1566.004 - Phishing: Voice (Vishing)
• T1598 - Phishing for Information
• T1598.003 - Phishing for Information: Spearphishing Voice
• T1589 - Gather Victim Identity Information
• T1589.001 - Gather Victim Identity Information: Credentials
• T1589.002 - Gather Victim Identity Information: Email Addresses
• T1591 - Gather Victim Org Information
• T1591.004 - Gather Victim Org Information: Identify Roles
• T1593 - Search Open Websites/Domains

NIST References

• NIST SP 800-50 - Building an IT Security Awareness and Training Program
• NIST SP 800-53 Rev. 5 - AT-2: Literacy Training and Awareness
• NIST SP 800-53 Rev. 5 - AT-3: Role-Based Training
• NIST SP 800-115 - Section 3.3: Social Engineering

Legal Frameworks

• Computer Fraud and Abuse Act (CFAA) - Authorization requirements
• GDPR Article 6 - Lawful basis for processing (if recording EU citizens)
• State wiretapping laws - One-party vs two-party consent states
• Telecommunications Act - Caller ID spoofing regulations (47 U.S.C. 227)

Industry Standards

• PTES - Social Engineering section
• OSSTMM - Human Security Testing module
• CREST - Social Engineering guidelines
• SE Code of Ethics - Social engineering testing ethical standards

references/workflows.md (verbatim)

Workflows: Social Engineering Pretext Call

Vishing Campaign Workflow

┌─────────────────────────────────────────────────────────────────┐
│              VISHING CAMPAIGN WORKFLOW                            │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│  1. AUTHORIZATION & SCOPING                                      │
│     ├── Obtain written authorization                             │
│     ├── Define target list (departments, roles)                  │
│     ├── Define boundaries (no C-suite, no threats)               │
│     ├── Agree on pretext scenarios                               │
│     ├── Confirm call recording legality                          │
│     └── Establish deconfliction process                          │
│                                                                  │
│  2. OSINT RECONNAISSANCE                                         │
│     ├── Employee enumeration (LinkedIn, website)                 │
│     ├── Organizational structure mapping                         │
│     ├── Technology stack identification                          │
│     ├── Internal terminology and process research                │
│     └── Target prioritization                                    │
│                                                                  │
│  3. PRETEXT DEVELOPMENT                                          │
│     ├── Select scenario(s) per target role                       │
│     ├── Draft call scripts with key phrases                      │
│     ├── Prepare objection handling responses                     │
│     ├── Set up caller ID spoofing (authorized)                   │
│     └── Rehearse delivery                                        │
│                                                                  │
│  4. CALL EXECUTION                                               │
│     ├── Execute calls according to schedule                      │
│     ├── Record calls (with legal authorization)                  │
│     ├── Document responses and disclosures                       │
│     ├── Note verification attempts by targets                    │
│     └── Track time-to-disclosure metrics                         │
│                                                                  │
│  5. ANALYSIS & REPORTING                                         │
│     ├── Calculate disclosure rates by department                 │
│     ├── Identify patterns (role, tenure, training)               │
│     ├── Compare against industry benchmarks                      │
│     ├── Generate remediation recommendations                     │
│     └── Present findings to stakeholders                         │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

Pretext Selection Decision Tree

Select Pretext Based on Target Role
│
├── IT/Technical Staff
│   ├── Vendor support call (patch emergency)
│   ├── Cloud provider security alert
│   └── Penetration test notification (meta-pretext)
│
├── Finance/Accounting
│   ├── Wire transfer verification (CEO fraud)
│   ├── Vendor payment update
│   └── Audit compliance request
│
├── HR/Recruiting
│   ├── Benefits enrollment verification
│   ├── Background check follow-up
│   └── Payroll system update
│
├── Executive Assistants
│   ├── Executive impersonation (travel issue)
│   ├── Board meeting preparation
│   └── Urgent document request
│
├── General Employees
│   ├── IT Helpdesk (password reset/VPN update)
│   ├── Facilities (badge system update)
│   └── Survey/research call
│
└── Front Desk/Reception
    ├── Delivery/courier pretext
    ├── Visitor registration
    └── Employee directory request

Back to mukul975/Anthropic-Cybersecurity-Skills (817 security skills) or Agent skills.