MITRE ATT&CK T1598.002: Spearphishing Attachment
When to use this skill
Use this skill when the task involves T1598.002, Spearphishing Attachment, 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.002
- Technique name: Spearphishing Attachment
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1598/002
- Tactics: reconnaissance
- Platforms: PRE
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may send spearphishing messages with a malicious attachment 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: Establish Accounts or Compromise Accounts) and/or sending multiple, seemingly urgent messages.
All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries attach a file to the spearphishing email. In some cases, they may rely upon the recipient populating information, then returning the file.(Citation: Sophos Attachment)(Citation: GitHub Phishery) The text of the spearphishing email usually tries to give a plausible reason why the file should be filled-in, such as a request for information from a business associate. In other cases, adversaries may leverage techniques such as HTML Smuggling to harvest user credentials via fake login portals.(Citation: Huntress HTML Smuggling 2024)
Adversaries may also use information from previous reconnaissance efforts (ex: Search Open Websites/Domains or Search Victim-Owned Websites) to craft persuasive and believable lures.
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
- Software Configuration
- User Training
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- Dragonfly (intrusion-set)
- SideCopy (intrusion-set)
- Sidewinder (intrusion-set)
- Star Blizzard (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.
ATT&CK contributors
- Philip Winther
- Sebastian Salla, McAfee
- Robert Simmons, @MalwareUtkonos
1---2name: attack-ent-t1598-002-spearphishing-attachment3description: "Analyze MITRE ATT&CK T1598.002 Spearphishing Attachment 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.002, Spearphishing Attachment, or enterprise ATT&CK. Adversaries may send spearphishing messages with a malicious attachment to elicit sensitive information that can be used during targeting."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-ent-t1598-002-spearphishing-attachment7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1598.00210 attack_stix_id: attack-pattern--8982a661-d84c-48c0-b4ec-1db29c6cf3bc11 attack_version: "1.2"12 attack_modified: "2025-10-24T17:49:04.751Z"13---1415# MITRE ATT&CK T1598.002: Spearphishing Attachment1617## When to use this skill1819Use this skill when the task involves T1598.002, Spearphishing Attachment, 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.2021## Technique context2223- ATT&CK domain: enterprise24- ATT&CK ID: T1598.00225- Technique name: Spearphishing Attachment26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1598/00228- Tactics: reconnaissance29- Platforms: PRE30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may send spearphishing messages with a malicious attachment 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: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)) and/or sending multiple, seemingly urgent messages.3738All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries attach a file to the spearphishing email. In some cases, they may rely upon the recipient populating information, then returning the file.(Citation: Sophos Attachment)(Citation: GitHub Phishery) The text of the spearphishing email usually tries to give a plausible reason why the file should be filled-in, such as a request for information from a business associate. In other cases, adversaries may leverage techniques such as [HTML Smuggling](https://attack.mitre.org/techniques/T1027/006) to harvest user credentials via fake login portals.(Citation: Huntress HTML Smuggling 2024)3940Adversaries 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 craft persuasive and believable lures.4142## Agent workflow43441. 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.452. 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.463. 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.474. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.485. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.496. 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.5051## Bundled resources5253- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.54- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.55- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.56- `templates/detection-brief.md`: detection engineering brief template.57- `templates/hunt-plan.md`: threat hunt plan template.58- `templates/incident-response-note.md`: incident response note template.59- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.60- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.61- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6263To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6465## Detection guidance6667No ATT&CK detection guidance was present in the source STIX object.6869## Useful telemetry and data sources7071- Not specified in the STIX object.7273## Mitigations to consider7475- Software Configuration76- User Training7778## Known threat context7980Use these examples only as contextual leads, not as proof that an observed event is this technique:8182- Dragonfly (intrusion-set)83- SideCopy (intrusion-set)84- Sidewinder (intrusion-set)85- Star Blizzard (intrusion-set)8687## Recommended output pattern8889When responding with this skill, structure the answer as:9091- Assessment: whether the evidence supports this ATT&CK mapping and why.92- Evidence: specific indicators, logs, behaviors, and assumptions.93- Detection: telemetry sources, analytic logic, and tuning considerations.94- Response: containment, eradication, recovery, and validation actions.95- Coverage gaps: missing logs, sensors, controls, or environmental details.96- References: include the ATT&CK URL and any user-provided evidence references.9798## ATT&CK contributors99100- Philip Winther101- Sebastian Salla, McAfee102- Robert Simmons, @MalwareUtkonos