Devtoolslauncher.exe Executes Specified Binary

Last updated on:

Rule name

Rule type

Log sources

MITRE ATT&CK tags

Severity

Devtoolslauncher.exe Executes Specified Binary

Standard

Windows

Defense Evasion: Indicator Removal - Clear Windows Event Logs (T1070.001),"Defense Evasion: Impair Defenses - Disable or Modify Tools (T1562.001)"

Critical

About the rule

Rule Type

Standard

Rule Description

The Devtoolslauncher.exe executes other binary

Severity

Trouble

Rule journey

Attack chain scenario

Initial access → Payload delivery → DevTools abused → Binary execution → Privilege escalation → Persistence established

Impact

  • Stealthy execution
  • Defense evasion
  • Privilege abuse
  • Malware deployment

Rule Requirement

Prerequisites

  • Using Windows event viewer:

To enable detailed audit logging, log in to a domain controller with domain admin credentials and open the Group Policy Management Console (GPMC). Create or modify a GPO linked to the relevant OU, and navigate to Detailed Tracking under Advanced Audit Policy Configuration. Enable Audit Process Creation and Audit Process Termination by checking the "Success" option in each. For enhanced visibility, enable “Include command line in process creation events” under Audit Process Creation in Administrative Templates, and ensure the relevant registry key is created under the Windows Security Auditing path.

  • Using Sysmon:

To set up Sysmon for process creation monitoring, download and install it from Microsoft Sysinternals, and run the installer with admin privileges using a configuration file that includes <ProcessCreate> event filtering. Ensure all process creation events are captured, and create the required registry key under Microsoft-Windows-Sysmon/Operational if it doesn't already exist. This setup enhances visibility into process execution for security monitoring and threat detection.

Criteria

Action1: actionname = "Process started" AND PROCESSNAME endswith "\devtoolslauncher.exe" AND COMMANDLINE contains "LaunchForDeploy" select Action1.HOSTNAME,Action1.MESSAGE,Action1.COMMANDLINE,Action1.FILE_NAME,Action1.PROCESSNAME,Action1.USERNAME,Action1.PARENTPROCESSNAME

Detection

Execution Mode

realtime

Log Sources

Windows

MITRE ATT&CK

Security Standards

Enabling this rule will help you meet the security standard's requirements listed below:

1. NIST SP 800-53 SI-4 – System Monitoring

Requires continuous monitoring of systems to detect and respond to suspicious activities.
Triggering this rule enables visibility into unusual binary executions through devtoolslauncher.exe, helping detect unauthorized or suspicious behavior.

2. NIST SP 800-53 AC-2 – Account Management

Ensures only authorized users execute programs or access systems.
Triggering this rule helps identify misuse of developer tools by validating whether the binary execution is performed by an authorized account.

3. NIST SP 800-53 CM-6 – Configuration Settings

Mandates enforcement of security configuration settings for systems.
Triggering this rule highlights deviations from expected tool usage, allowing admins to realign system behavior with baseline configurations.

4. NIST SP 800-53 AU-6 – Audit Review, Analysis, and Reporting

Calls for timely review and analysis of audit records.
Triggering this rule ensures audit logs capture devtoolslauncher activity, aiding forensic analysis and compliance review.

5. NIST SP 800-171 3.1.7 – Prevent Non-Privileged Users from Executing Code

Limits code execution to privileged users to reduce attack surface.
Triggering this rule helps detect when binaries are launched via devtoolslauncher by non-privileged or unauthorized users.

Author

Beyu Denis, oscd.community (rule), @_felamos (idea)

Future actions

Known False Positives

This rule will be triggered when devtoolslauncher.exe is legitimately executed by an authorized user.

Next Steps

When this rule is triggered, the following measures can be implemented:

  1. Identification: Identify if the flagged event is a new incident or part of an existing incident.
  2. Analysis: Analyze the impact and extent of the incident to comprehend the severity of the attack using the Incident Workbench.
  3. Response: Respond promptly by initiating an automated workflow to interrupt the network connections and cease the malicious process.
  4. Containment: Isolate the affected host from the network to prevent further execution or lateral movement of potentially malicious binaries.
  5. Eradication: Remove unauthorized or malicious binaries executed via devtoolslauncher.exe, and restore affected systems to a known good state.

Mitigation

Mitigation IDs

Mitigation name

Description

M1042

Disable or Remove Feature or Program

Several native binaries may be unnecessary in specific environments and can be safely disabled or removed to reduce the attack surface.

M1038

Execution Prevention

Consider using application control to prevent execution of binaries that are susceptible to abuse and not required for a given system or network.

M1050

Exploit Protection

Microsoft's Enhanced Mitigation Experience Toolkit (EMET) Attack Surface Reduction (ASR) feature can be used to block methods of using trusted binaries to bypass application control.

M1037

Filter Network Traffic

Use network appliances to filter ingress or egress traffic and perform protocol-based filtering. Configure software on endpoints to filter network traffic.

M1026

Privileged Account Management

Limit the execution of high-risk binaries to specific privileged accounts or groups that require access, reducing the chances of unauthorized or malicious use.

M1021

Restrict Web-Based Content

Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc.