MITRE ATT&CK T1614.001: System Language Discovery
When to use this skill
Use this skill when the task involves T1614.001, System Language Discovery, 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: T1614.001
- Technique name: System Language Discovery
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1614/001
- Tactics: discovery
- Platforms: Linux, macOS, Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may attempt to gather information about the system language of a victim in order to infer the geographical location of that host. This information may be used to shape follow-on behaviors, including whether the adversary infects the target and/or attempts specific actions. This decision may be employed by malware developers and operators to reduce their risk of attracting the attention of specific law enforcement agencies or prosecution/scrutiny from other entities.(Citation: Malware System Language Check)
There are various sources of data an adversary could use to infer system language, such as system defaults and keyboard layouts. Specific checks will vary based on the target and/or adversary, but may involve behaviors such as Query Registry and calls to Native API functions.(Citation: CrowdStrike Ryuk January 2019)
For example, on a Windows system adversaries may attempt to infer the language of a system by querying the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language or parsing the outputs of Windows API functions GetUserDefaultUILanguage, GetSystemDefaultUILanguage, GetKeyboardLayoutList and GetUserDefaultLangID.(Citation: Darkside Ransomware Cybereason)(Citation: Securelist JSWorm)(Citation: SecureList SynAck Doppelgänging May 2018)
On a macOS or Linux system, adversaries may query locale to retrieve the value of the $LANG environment variable.
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
- No ATT&CK mitigation relationships were present in the source STIX bundle.
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- Avaddon (malware)
- Bazar (malware)
- BlackByte (intrusion-set)
- BlackByte Ransomware (malware)
- Clop (malware)
- Cuba (malware)
- Cuckoo Stealer (malware)
- DEATHRANSOM (malware)
- DropBook (malware)
- Flagpro (malware)
- GlassWorm (malware)
- Gootloader (malware)
- GrimAgent (malware)
- IcedID (malware)
- Ke3chang (intrusion-set)
- LODEINFO (malware)
- LockBit 2.0 (malware)
- LockBit 3.0 (malware)
- Malteiro (intrusion-set)
- MarkiRAT (malware)
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
- Harshal Tupsamudre, Qualys
1---2name: attack-ent-t1614-001-system-language-discovery3description: "Analyze MITRE ATT&CK T1614.001 System Language Discovery in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1614.001, System Language Discovery, or enterprise ATT&CK. Adversaries may attempt to gather information about the system language of a victim in order to infer the geographical location of that host."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-t1614-001-system-language-discovery7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1614.00110 attack_stix_id: attack-pattern--c1b68a96-3c48-49ea-a6c0-9b27359f9c1911 attack_version: "1.1"12 attack_modified: "2025-10-24T17:49:20.039Z"13---1415# MITRE ATT&CK T1614.001: System Language Discovery1617## When to use this skill1819Use this skill when the task involves T1614.001, System Language Discovery, 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: T1614.00125- Technique name: System Language Discovery26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1614/00128- Tactics: discovery29- Platforms: Linux, macOS, Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may attempt to gather information about the system language of a victim in order to infer the geographical location of that host. This information may be used to shape follow-on behaviors, including whether the adversary infects the target and/or attempts specific actions. This decision may be employed by malware developers and operators to reduce their risk of attracting the attention of specific law enforcement agencies or prosecution/scrutiny from other entities.(Citation: Malware System Language Check)3738There are various sources of data an adversary could use to infer system language, such as system defaults and keyboard layouts. Specific checks will vary based on the target and/or adversary, but may involve behaviors such as [Query Registry](https://attack.mitre.org/techniques/T1012) and calls to [Native API](https://attack.mitre.org/techniques/T1106) functions.(Citation: CrowdStrike Ryuk January 2019) 3940For example, on a Windows system adversaries may attempt to infer the language of a system by querying the registry key <code>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language</code> or parsing the outputs of Windows API functions <code>GetUserDefaultUILanguage</code>, <code>GetSystemDefaultUILanguage</code>, <code>GetKeyboardLayoutList</code> and <code>GetUserDefaultLangID</code>.(Citation: Darkside Ransomware Cybereason)(Citation: Securelist JSWorm)(Citation: SecureList SynAck Doppelgänging May 2018)4142On a macOS or Linux system, adversaries may query <code>locale</code> to retrieve the value of the <code>$LANG</code> environment variable.4344## Agent workflow45461. 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.472. 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.483. 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.494. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.505. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.516. 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.5253## Bundled resources5455- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.56- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.57- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.58- `templates/detection-brief.md`: detection engineering brief template.59- `templates/hunt-plan.md`: threat hunt plan template.60- `templates/incident-response-note.md`: incident response note template.61- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.62- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.63- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6465To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6667## Detection guidance6869No ATT&CK detection guidance was present in the source STIX object.7071## Useful telemetry and data sources7273- Not specified in the STIX object.7475## Mitigations to consider7677- No ATT&CK mitigation relationships were present in the source STIX bundle.7879## Known threat context8081Use these examples only as contextual leads, not as proof that an observed event is this technique:8283- Avaddon (malware)84- Bazar (malware)85- BlackByte (intrusion-set)86- BlackByte Ransomware (malware)87- Clop (malware)88- Cuba (malware)89- Cuckoo Stealer (malware)90- DEATHRANSOM (malware)91- DropBook (malware)92- Flagpro (malware)93- GlassWorm (malware)94- Gootloader (malware)95- GrimAgent (malware)96- IcedID (malware)97- Ke3chang (intrusion-set)98- LODEINFO (malware)99- LockBit 2.0 (malware)100- LockBit 3.0 (malware)101- Malteiro (intrusion-set)102- MarkiRAT (malware)103104## Recommended output pattern105106When responding with this skill, structure the answer as:107108- Assessment: whether the evidence supports this ATT&CK mapping and why.109- Evidence: specific indicators, logs, behaviors, and assumptions.110- Detection: telemetry sources, analytic logic, and tuning considerations.111- Response: containment, eradication, recovery, and validation actions.112- Coverage gaps: missing logs, sensors, controls, or environmental details.113- References: include the ATT&CK URL and any user-provided evidence references.114115## ATT&CK contributors116117- Harshal Tupsamudre, Qualys