T1218 System Binary Proxy Execution

Enterprise

Adversaries may bypass process and/or signature-based defenses by proxying execution of malicious content with signed, or otherwise trusted, binaries. Binaries used in this technique are often Microsoft-signed files, indicating that they have been either downloaded from Microsoft or are already native in the operating system. Binaries signed with trusted digital certificates can typically execute on Windows systems protected by digital signature validation. Several Microsoft signed binaries that are default on Windows installations can be used to proxy execution of other files or commands. Similarly, on Linux systems adversaries may abuse trusted binaries such as <code>split</code> to proxy execution of malicious commands.

01

platforms

Platforms this applies to.

LinuxmacOSWindows
02

tactics

ATT&CK tactics this technique serves.

04

mitigations

ATT&CK mitigations that reduce this.

05

detected by (3)

Data components that detect this.

06

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.

08

known-exploited CVEs (2)

Related CVEs.

IDseverity exploitable
CVE-2021-44077UScritical9.8OT criticalKEV
Zoho ManageEngine ServiceDesk Plus before 11306, ServiceDesk Plus MSP before 10530, and SupportCenter Plus before 11014 are vulnerable to unauthenticated remote code execution. Thi…
CVE-2021-40539UScritical9.8OT criticalKEV
Zoho ManageEngine ADSelfService Plus version 6113 and prior is vulnerable to REST API authentication bypass with resultant remote code execution.
09

groups (2)

Threat groups associated with this.

10

Detected by (Sigma) (158)

Sigma detection rules related to this.

showing 20 of 158
11

source

Where this definition is published.