ATT&CK Reference
Portfolio

TA0005 · DEFENSE EVASION

Reflective Code Loading

T1620macOS · Linux · Windowsattack.mitre.org

Adversaries may reflectively load code into a process in order to conceal the execution of malicious payloads.

Detect it with

Monitor for code artifacts associated with reflectively loading code, such as the abuse of .NET functions such as Assembly.Load() and Native API functions such as CreateThread() , memfd_create() , execve() , and/or execveat() . Monitor for artifacts of abnormal process execution.

Why it matters on shift

Reflective Code Loading is one of the concrete ways adversaries achieve defense evasion. Recognising it in telemetry lets you name the technique in your ticket and pivot to what came before and after.

What to look for next

After defense evasion, the next tactic is usually Credential Access. Search your telemetry for the transition before closing the ticket.

Kill-chain context

← beforePrivilege EscalationDefense Evasionafter →Credential Access