MITRE ATT&CK T1598.004: Spearphishing Voice
When to use this skill
Use this skill when the task involves T1598.004, Spearphishing Voice, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique.
Technique context
- ATT&CK domain: enterprise
- ATT&CK ID: T1598.004
- Technique name: Spearphishing Voice
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1598/004
- Tactics: reconnaissance
- Platforms: PRE
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may use voice communications to elicit sensitive information that can be used during targeting. Spearphishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Spearphishing for information frequently involves social engineering techniques, such as posing as a source with a reason to collect information (ex: Impersonation) and/or creating a sense of urgency or alarm for the recipient.
All forms of phishing are electronically delivered social engineering. In this scenario, adversaries use phone calls to elicit sensitive information from victims. Known as voice phishing (or "vishing"), these communications can be manually executed by adversaries, hired call centers, or even automated via robocalls. Voice phishers may spoof their phone number while also posing as a trusted entity, such as a business partner or technical support staff.(Citation: BOA Telephone Scams)
Victims may also receive phishing messages that direct them to call a phone number ("callback phishing") where the adversary attempts to collect confidential information.(Citation: Avertium callback phishing)
Adversaries may also use information from previous reconnaissance efforts (ex: Search Open Websites/Domains or Search Victim-Owned Websites) to tailor pretexts to be even more persuasive and believable for the victim.
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.references/known-threat-context.md: ATT&CK relationship context with attribution cautions.templates/detection-brief.md: detection engineering brief template.templates/hunt-plan.md: threat hunt plan template.templates/incident-response-note.md: incident response note template.templates/coverage-assessment.md: ATT&CK coverage assessment template.scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- C0027 (campaign)
- LAPSUS$ (intrusion-set)
- Salesforce Data Exfiltration (campaign)
- Scattered Spider (intrusion-set)
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
1---2name: attack-ent-t1598-004-spearphishing-voice3description: Analyze MITRE ATT&CK T1598.004 Spearphishing Voice in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1598.004, Spearphishing Voice, or enterprise ATT&CK. Adversaries may use voice communications to elicit sensitive information that can be used during targeting.4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See h5---67# MITRE ATT&CK T1598.004: Spearphishing Voice89## When to use this skill1011Use this skill when the task involves T1598.004, Spearphishing Voice, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique.1213## Technique context1415- ATT&CK domain: enterprise16- ATT&CK ID: T1598.00417- Technique name: Spearphishing Voice18- Type: sub-technique19- ATT&CK URL: https://attack.mitre.org/techniques/T1598/00420- Tactics: reconnaissance21- Platforms: PRE22- Required permissions: Not specified23- Effective permissions: Not specified24- Defenses bypassed: Not specified2526## ATT&CK description2728Adversaries may use voice communications to elicit sensitive information that can be used during targeting. Spearphishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Spearphishing for information frequently involves social engineering techniques, such as posing as a source with a reason to collect information (ex: [Impersonation](https://attack.mitre.org/techniques/T1684/001)) and/or creating a sense of urgency or alarm for the recipient.2930All forms of phishing are electronically delivered social engineering. In this scenario, adversaries use phone calls to elicit sensitive information from victims. Known as voice phishing (or "vishing"), these communications can be manually executed by adversaries, hired call centers, or even automated via robocalls. Voice phishers may spoof their phone number while also posing as a trusted entity, such as a business partner or technical support staff.(Citation: BOA Telephone Scams)3132Victims may also receive phishing messages that direct them to call a phone number ("callback phishing") where the adversary attempts to collect confidential information.(Citation: Avertium callback phishing)3334Adversaries may also use information from previous reconnaissance efforts (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)) to tailor pretexts to be even more persuasive and believable for the victim.3536## Agent workflow37381. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.392. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.403. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.414. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.425. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.436. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.4445## Bundled resources4647- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.48- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.49- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.50- `templates/detection-brief.md`: detection engineering brief template.51- `templates/hunt-plan.md`: threat hunt plan template.52- `templates/incident-response-note.md`: incident response note template.53- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.54- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.55- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.5657To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.5859## Detection guidance6061No ATT&CK detection guidance was present in the source STIX object.6263## Useful telemetry and data sources6465- Not specified in the STIX object.6667## Mitigations to consider6869- User Training7071## Known threat context7273Use these examples only as contextual leads, not as proof that an observed event is this technique:7475- C0027 (campaign)76- LAPSUS$ (intrusion-set)77- Salesforce Data Exfiltration (campaign)78- Scattered Spider (intrusion-set)7980## Recommended output pattern8182When responding with this skill, structure the answer as:8384- Assessment: whether the evidence supports this ATT&CK mapping and why.85- Evidence: specific indicators, logs, behaviors, and assumptions.86- Detection: telemetry sources, analytic logic, and tuning considerations.87- Response: containment, eradication, recovery, and validation actions.88- Coverage gaps: missing logs, sensors, controls, or environmental details.89- References: include the ATT&CK URL and any user-provided evidence references.
santosomar