Has initiated voice calls with victims posing as IT support to prompt users to download and execute scripts and other tools for initial access.123
- Tactic
- Initial Access
- Platforms
- Linux, macOS, Windows, Identity Provider
- Version
- 1.2
- Created
- 07 September 2023
- Last modified
- 12 May 2026
Adversaries may use voice communications to ultimately gain access to victim systems. Spearphishing voice is a specific variant of spearphishing. It is different from other forms of spearphishing in that it employs the use of manipulating a user into providing access to systems through a phone call or other forms of voice communications. Spearphishing frequently involves social engineering techniques, such as posing as a trusted source (ex: Impersonation) and/or creating a sense of urgency or alarm for the recipient.
Spearphishing Voice MITRE reference T1566.004
1 group has been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
All 1 groups for this technique
1 campaign has been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During C0027, Scattered Spider impersonated legitimate IT personnel in phone calls to direct victims to download a remote monitoring and management (RMM) tool that would allow the adversary to remotely control their system.1
All 1 campaigns for this technique
Offense vs defense T1566.004
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
Spearphishing Voice detection strategy DET0245
MITRE names one behaviour worth catching for this technique and breaks it into 4 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection Strategy for Spearphishing Voice across OS platforms
AN0683 · Windows
Monitor call log records from corporate devices for unusual or unauthorized numbers, especially repeated calls to/from known malicious phone numbers. Correlate with subsequent system events (e.g., browser navigation, remote management tool execution).
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Application Log ContentDC0038 | ApplicationLog:CallRecords | Outbound or inbound calls to high-risk or blocklisted numbers |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| PhoneNumberBlocklist | List of known malicious or suspicious phone numbers; must be tuned per environment |
| TimeWindow | Threshold for correlating call events with subsequent suspicious system activity |
AN0684 · Linux
Audit VoIP/SIP logs for suspicious outbound calls or call setup messages to unusual endpoints. Correlate with user activity such as browser execution or package installation following the call.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Application Log ContentDC0038 | networkdevice:syslog | SIP REGISTER, INVITE, or unusual call destination metadata |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| CallDestinationPatterns | Regular expressions or rules for spotting abnormal call destinations |
| UserContext | Expected users who initiate VoIP traffic vs. anomalous accounts |
AN0685 · macOS
Monitor Facetime, iMessage, or SIP client logs for anomalous voice call attempts. Link to subsequent user execution events (downloads, RMM installs) triggered post-call.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Application Log ContentDC0038 | macos:unifiedlog | Outgoing or incoming calls with non-standard caller IDs or unusual metadata |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| CallerIDPatterns | Patterns of spoofed caller IDs that must be tuned based on region and telecom provider |
| PayloadCorrelation | Define what follow-on events (browser downloads, execution) to correlate with call logs |
AN0686 · Identity Provider
Correlate MFA push fatigue or unusual consent grant attempts with call activity where adversaries may have socially engineered the user over voice.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Application Log ContentDC0038 | m365:unified | Unusual MFA requests or OAuth consent events temporally aligned with user-reported vishing call |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| MFARequestThreshold | Number of MFA push requests within a timeframe aligned to a suspicious call |
| ConsentGrantPatterns | Unusual OAuth consent URLs or delegated scopes |
Users can be trained to identify and report social engineering techniques and spearphishing attempts, while also being suspicious of and verifying the identify of callers.