MITRE ATT&CK T1213.005: Messaging Applications
When to use this skill
Use this skill when the task involves T1213.005, Messaging Applications, 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: T1213.005
- Technique name: Messaging Applications
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1213/005
- Tactics: collection
- Platforms: Office Suite, SaaS
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may leverage chat and messaging applications, such as Microsoft Teams, Google Chat, and Slack, to mine valuable information.
The following is a brief list of example information that may hold potential value to an adversary and may also be found on messaging applications:
- Testing / development credentials (i.e., Chat Messages)
- Source code snippets
- Links to network shares and other internal resources
- Proprietary data(Citation: Guardian Grand Theft Auto Leak 2022)
- Discussions about ongoing incident response efforts(Citation: SC Magazine Ragnar Locker 2021)(Citation: Microsoft DEV-0537)
In addition to exfiltrating data from messaging applications, adversaries may leverage data from chat messages in order to improve their targeting - for example, by learning more about an environment or evading ongoing incident response efforts.(Citation: Sentinel Labs NullBulge 2024)(Citation: Permiso Scattered Spider 2023)
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
- Audit
- Out-of-Band Communications Channel
- User Training
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- Fox Kitten (intrusion-set)
- LAPSUS$ (intrusion-set)
- Scattered Spider (intrusion-set)
- TruffleHog (tool)
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
- Menachem Goldstein
- Obsidian Security
1---2name: attack-ent-t1213-005-messaging-applications3description: "Analyze MITRE ATT&CK T1213.005 Messaging Applications in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1213.005, Messaging Applications, or enterprise ATT&CK. Adversaries may leverage chat and messaging applications, such as Microsoft Teams, Google Chat, and Slack, to mine valuable information."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-t1213-005-messaging-applications7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1213.00510 attack_stix_id: attack-pattern--fb75213f-cfb0-40bf-a02f-3bad93d6601e11 attack_version: "1.0"12 attack_modified: "2025-04-15T22:48:58.763Z"13---1415# MITRE ATT&CK T1213.005: Messaging Applications1617## When to use this skill1819Use this skill when the task involves T1213.005, Messaging Applications, 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: T1213.00525- Technique name: Messaging Applications26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1213/00528- Tactics: collection29- Platforms: Office Suite, SaaS30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may leverage chat and messaging applications, such as Microsoft Teams, Google Chat, and Slack, to mine valuable information. 3738The following is a brief list of example information that may hold potential value to an adversary and may also be found on messaging applications: 3940* Testing / development credentials (i.e., [Chat Messages](https://attack.mitre.org/techniques/T1552/008)) 41* Source code snippets 42* Links to network shares and other internal resources 43* Proprietary data(Citation: Guardian Grand Theft Auto Leak 2022)44* Discussions about ongoing incident response efforts(Citation: SC Magazine Ragnar Locker 2021)(Citation: Microsoft DEV-0537)4546In addition to exfiltrating data from messaging applications, adversaries may leverage data from chat messages in order to improve their targeting - for example, by learning more about an environment or evading ongoing incident response efforts.(Citation: Sentinel Labs NullBulge 2024)(Citation: Permiso Scattered Spider 2023)4748## Agent workflow49501. 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.512. 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.523. 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.534. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.545. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.556. 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.5657## Bundled resources5859- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.60- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.61- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.62- `templates/detection-brief.md`: detection engineering brief template.63- `templates/hunt-plan.md`: threat hunt plan template.64- `templates/incident-response-note.md`: incident response note template.65- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.66- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.67- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6869To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.7071## Detection guidance7273No ATT&CK detection guidance was present in the source STIX object.7475## Useful telemetry and data sources7677- Not specified in the STIX object.7879## Mitigations to consider8081- Audit82- Out-of-Band Communications Channel83- User Training8485## Known threat context8687Use these examples only as contextual leads, not as proof that an observed event is this technique:8889- Fox Kitten (intrusion-set)90- LAPSUS$ (intrusion-set)91- Scattered Spider (intrusion-set)92- TruffleHog (tool)9394## Recommended output pattern9596When responding with this skill, structure the answer as:9798- Assessment: whether the evidence supports this ATT&CK mapping and why.99- Evidence: specific indicators, logs, behaviors, and assumptions.100- Detection: telemetry sources, analytic logic, and tuning considerations.101- Response: containment, eradication, recovery, and validation actions.102- Coverage gaps: missing logs, sensors, controls, or environmental details.103- References: include the ATT&CK URL and any user-provided evidence references.104105## ATT&CK contributors106107- Menachem Goldstein108- Obsidian Security