Elastic Security Detection Rules

Process Injection by the Microsoft Build Engine

Last updated 6 days ago on 2025-02-25
Created 5 years ago on 2020-03-25

About

An instance of MSBuild, the Microsoft Build Engine, created a thread in another process. This technique is sometimes used to evade detection or elevate privileges.
Tags
Domain: EndpointOS: WindowsUse Case: Threat DetectionTactic: Defense EvasionTactic: Privilege EscalationData Source: SysmonLanguage: eql
Severity
low
Risk Score
21
MITRE ATT&CK™

Defense Evasion (TA0005)(opens in a new tab or window)

↳ Process Injection (T1055)(opens in a new tab or window)

↳ Trusted Developer Utilities Proxy Execution (T1127)(opens in a new tab or window)

Privilege Escalation (TA0004)(opens in a new tab or window)

↳ Process Injection (T1055)(opens in a new tab or window)

False Positive Examples
The Build Engine is commonly used by Windows developers but use by non-engineers is unusual.
License
Elastic License v2(opens in a new tab or window)

Definition

Rule Type
Event Correlation Rule
Integration Pack
Prebuilt Security Detection Rules
Index Patterns
winlogbeat-*logs-windows.sysmon_operational-*
Related Integrations

windows(opens in a new tab or window)

Query
process where host.os.type == "windows" and
  event.provider == "Microsoft-Windows-Sysmon" and
  /* CreateRemoteThread */
  event.code == "8" and process.name: "MSBuild.exe"

Install detection rules in Elastic Security

Detect Process Injection by the Microsoft Build Engine in the Elastic Security detection engine by installing this rule into your Elastic Stack.

To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(opens in a new tab or window).