Process Injection by the Microsoft Build Engine

IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Process Injection by the Microsoft Build Engine

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.

Rule type: query

Rule indices:

winlogbeat-*

Severity: low

Risk score: 21

Runs every: 5 minutes

Searches indices from: now-6m (Date Math format, see also Additional look-back time)

Maximum signals per execution: 100

Tags:

Elastic
Windows

Version: 1

Added (Elastic Stack release): 7.7.0

Potential false positives

edit

The Build Engine is commonly used by Windows developers but use by non-engineers is unusual.

Rule query

edit

process.name:MSBuild.exe and event.action:"CreateRemoteThread detected
(rule: CreateRemoteThread)"

Threat mapping

edit

Framework: MITRE ATT&CK^TM

Tactic:
- Name: Defense Evasion
- ID: TA0005
- Reference URL: https://attack.mitre.org/tactics/TA0005/
Technique:
- Name: Process Injection
- ID: T1055
- Reference URL: https://attack.mitre.org/techniques/T1055/
Tactic:
- Name: Privilege Escalation
- ID: TA0004
- Reference URL: https://attack.mitre.org/tactics/TA0004/
Technique:
- Name: Process Injection
- ID: T1055
- Reference URL: https://attack.mitre.org/techniques/T1055/

« Process Injection - Prevented - Elastic Endpoint Proxy Port Activity to the Internet »