MITRE ATT&CK T1204.001: Malicious Link
When to use this skill
Use this skill when the task involves T1204.001, Malicious Link, 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: T1204.001
- Technique name: Malicious Link
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1204/001
- Tactics: execution
- Platforms: Linux, macOS, Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
An adversary may rely upon a user clicking a malicious link in order to gain execution. Users may be subjected to social engineering to get them to click on a link that will lead to code execution. This user action will typically be observed as follow-on behavior from Spearphishing Link. Clicking on a link may also lead to other execution techniques such as exploitation of a browser or application vulnerability via Exploitation for Client Execution. Links may also lead users to download files that require execution via Malicious File.
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
- Network Intrusion Prevention
- Restrict Web-Based Content
- User Training
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- APT-C-36 (intrusion-set)
- APT28 (intrusion-set)
- APT29 (intrusion-set)
- APT3 (intrusion-set)
- APT32 (intrusion-set)
- APT33 (intrusion-set)
- APT38 (intrusion-set)
- APT39 (intrusion-set)
- AppleJeus (malware)
- BackConfig (malware)
- Bazar (malware)
- BlackTech (intrusion-set)
- Bumblebee (malware)
- C0011 (campaign)
- C0021 (campaign)
- Cobalt Group (intrusion-set)
- Confucius (intrusion-set)
- Contagious Interview (intrusion-set)
- Daggerfly (intrusion-set)
- EXOTIC LILY (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-t1204-001-malicious-link3description: "Analyze MITRE ATT&CK T1204.001 Malicious Link in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1204.001, Malicious Link, or enterprise ATT&CK. An adversary may rely upon a user clicking a malicious link in order to gain execution."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-t1204-001-malicious-link7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1204.00110 attack_stix_id: attack-pattern--ef67e13e-5598-4adc-bdb2-998225874fa911 attack_version: "1.2"12 attack_modified: "2025-10-24T17:49:35.144Z"13---1415# MITRE ATT&CK T1204.001: Malicious Link1617## When to use this skill1819Use this skill when the task involves T1204.001, Malicious Link, 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: T1204.00125- Technique name: Malicious Link26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1204/00128- Tactics: execution29- Platforms: Linux, macOS, Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536An adversary may rely upon a user clicking a malicious link in order to gain execution. Users may be subjected to social engineering to get them to click on a link that will lead to code execution. This user action will typically be observed as follow-on behavior from [Spearphishing Link](https://attack.mitre.org/techniques/T1566/002). Clicking on a link may also lead to other execution techniques such as exploitation of a browser or application vulnerability via [Exploitation for Client Execution](https://attack.mitre.org/techniques/T1203). Links may also lead users to download files that require execution via [Malicious File](https://attack.mitre.org/techniques/T1204/002).3738## Agent workflow39401. 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.412. 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.423. 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.434. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.445. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.456. 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.4647## Bundled resources4849- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.50- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.51- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.52- `templates/detection-brief.md`: detection engineering brief template.53- `templates/hunt-plan.md`: threat hunt plan template.54- `templates/incident-response-note.md`: incident response note template.55- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.56- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.57- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.5859To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6061## Detection guidance6263No ATT&CK detection guidance was present in the source STIX object.6465## Useful telemetry and data sources6667- Not specified in the STIX object.6869## Mitigations to consider7071- Network Intrusion Prevention72- Restrict Web-Based Content73- User Training7475## Known threat context7677Use these examples only as contextual leads, not as proof that an observed event is this technique:7879- APT-C-36 (intrusion-set)80- APT28 (intrusion-set)81- APT29 (intrusion-set)82- APT3 (intrusion-set)83- APT32 (intrusion-set)84- APT33 (intrusion-set)85- APT38 (intrusion-set)86- APT39 (intrusion-set)87- AppleJeus (malware)88- BackConfig (malware)89- Bazar (malware)90- BlackTech (intrusion-set)91- Bumblebee (malware)92- C0011 (campaign)93- C0021 (campaign)94- Cobalt Group (intrusion-set)95- Confucius (intrusion-set)96- Contagious Interview (intrusion-set)97- Daggerfly (intrusion-set)98- EXOTIC LILY (intrusion-set)99100## Recommended output pattern101102When responding with this skill, structure the answer as:103104- Assessment: whether the evidence supports this ATT&CK mapping and why.105- Evidence: specific indicators, logs, behaviors, and assumptions.106- Detection: telemetry sources, analytic logic, and tuning considerations.107- Response: containment, eradication, recovery, and validation actions.108- Coverage gaps: missing logs, sensors, controls, or environmental details.109- References: include the ATT&CK URL and any user-provided evidence references.