IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Process Injection - Prevented - Endpoint Security Process Potentially Masquerading as WerFault »

› › ›

Process Injection by the Microsoft Build Engine

edit

Process Injection by the Microsoft Build Engine

edit

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 alerts per execution: 100

Tags:

Elastic
Host
Windows
Threat Detection
Defense Evasion

Version: 3 (version history)

Added (Elastic Stack release): 7.7.0

Last modified (Elastic Stack release): 7.10.0

Rule authors: Elastic

Rule license: Elastic License

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/

Rule version history

edit

Version 3 (7.10.0 release)

Formatting only

Version 2 (7.9.0 release)

Formatting only

« Process Injection - Prevented - Endpoint Security Process Potentially Masquerading as WerFault »