T1036.005 Match Legitimate Resource Name or Location

sub-techniqueEnterprise

Adversaries may match or approximate the name or location of legitimate files, Registry keys, or other resources when naming/placing them. This is done for the sake of evading defenses and observation. This may be done by placing an executable in a commonly trusted directory (ex: under System32) or giving it the name of a legitimate, trusted program (ex: `svchost.exe`). Alternatively, a Windows Registry key may be given a close approximation to a key used by a legitimate program. In containerized environments, a threat actor may create a resource in a trusted namespace or one that matches the naming convention of a container pod or cluster.

01

platforms

Platforms this applies to.

ContainersESXiLinuxmacOSWindows
02

tactics

ATT&CK tactics this technique serves.

03

sub-technique of

The broader entity this sits under.

04

mitigations

ATT&CK mitigations that reduce this.

07

NIST CSF 2.0 — areas of relevance (Protect / Detect)

NIST CSF 2.0 areas this most relates to (evidence-ranked).

Derived from MITRE CTID (Apache-2.0) and the NIST 800-53 ↔ CSF crosswalk (public domain). Indicative relevance along the Protect/Detect axis — not a compliance assessment or coverage claim.

09

known-exploited CVEs (1)

Related CVEs.

IDseverity exploitable
CVE-2023-26360US—OT criticalKEV
Adobe ColdFusion versions 2018 Update 15 (and earlier) and 2021 Update 5 (and earlier) are affected by an Improper Access Control vulnerability that could result in arbitrary code…
10

attack patterns (2)

CAPEC attack patterns that exploit this.

11

groups (66)

Threat groups associated with this.

12

software (145)

Malware and tools associated with this.

14

Detected by (Sigma) (24)

Sigma detection rules related to this.

showing 20 of 24
15

source

Where this definition is published.