T1127 CrowdStrike LogScale · LogScale

Detect Trusted Developer Utilities Proxy Execution in CrowdStrike LogScale

Adversaries may take advantage of trusted developer utilities to proxy execution of malicious payloads. Utilities used for software development tasks such as MSBuild, csc.exe, vbc.exe, WinDbg, cdb.exe, tracker.exe, dnx.exe, and rcsi.exe are typically signed with legitimate Microsoft certificates, allowing them to execute code and bypass application control solutions. These utilities can compile and execute inline C#, VB.NET, or native shellcode embedded in project files, scripts, or command-line arguments, effectively masquerading malicious execution as legitimate developer activity. Adversaries also leverage these tools to bypass Smart App Control by abusing the OS trust model for signed binaries that support arbitrary code execution.

MITRE ATT&CK

Tactic
Defense Evasion
Technique
T1127 Trusted Developer Utilities Proxy Execution
Canonical reference
https://attack.mitre.org/techniques/T1127/

LogScale Detection Query

CrowdStrike LogScale (LogScale)
cql
#event_simpleName=ProcessRollup2
| FileName = /(?i)^(msbuild|csc|vbc|jsc|dnx|rcsi|tracker|cdb|windbg|kd|ntsd|msdeploy|xwizard|mshta)\.exe$/
| SuspiciousParent := if(ParentBaseFileName = /(?i)^(winword|excel|powerpnt|outlook|msedge|chrome|firefox|iexplore|wscript|cscript|mshta|cmd|powershell|pwsh)\.exe$/, 1, 0)
| TempPathArg := if(CommandLine = /(?i)(\\temp\\|\\appdata\\local\\temp\\|\\appdata\\roaming\\|\\programdata\\|\\users\\public\\|\\downloads\\)/, 1, 0)
| MSBuildInlineTask := if(FileName = /(?i)^msbuild\.exe$/ and CommandLine = /(?i)(\x2ecsproj|\x2eproj|\x2exml|\x2etargets|\x2etasks)/, 1, 0)
| CompilerFromTemp := if(FileName = /(?i)^(csc|vbc|jsc)\.exe$/ and CommandLine = /(?i)(\\temp\\|\\appdata\\|\\programdata\\|\\users\\public\\)/, 1, 0)
| DebuggerShellcode := if(FileName = /(?i)^(cdb|windbg|ntsd|kd)\.exe$/ and CommandLine = /(-pd|-pv|-cf|-c )/, 1, 0)
| TrackerExec := if(FileName = /(?i)^tracker\.exe$/ and CommandLine = /(?i)(\/d3|\/dumpstartuplogging|\.dll|\.exe)/, 1, 0)
| RareUtility := if(FileName = /(?i)^(dnx|rcsi)\.exe$/, 1, 0)
| SuspicionScore := SuspiciousParent + TempPathArg + MSBuildInlineTask + CompilerFromTemp + DebuggerShellcode + TrackerExec + RareUtility
| SuspicionScore > 0
| table([timestamp, ComputerName, UserName, FileName, CommandLine, ParentBaseFileName, ParentCommandLine, SuspiciousParent, TempPathArg, MSBuildInlineTask, CompilerFromTemp, DebuggerShellcode, TrackerExec, RareUtility, SuspicionScore])
| sort(SuspicionScore, order=desc)
high severity high confidence

CrowdStrike LogScale (Falcon) detection for T1127 - Trusted Developer Utilities Proxy Execution. Uses ProcessRollup2 events to identify MSBuild, csc.exe, debuggers, and other developer utilities executing under suspicious conditions. Scores each event across multiple indicators: suspicious parent process, temp path arguments, inline task file types, compiler abuse from temp paths, debugger shellcode flags, tracker.exe misuse, and rare utilities.

Data Sources

CrowdStrike Falcon EDRFalcon ProcessRollup2 events

Required Tables

ProcessRollup2

False Positives & Tuning

  • Developer workstations with Visual Studio or Rider IDEs where MSBuild is frequently invoked with .csproj files from user profile paths during local builds
  • Security researchers using cdb.exe or WinDbg with debugging arguments (-pd, -c) as part of legitimate malware analysis or reverse engineering work on approved systems
  • Enterprise application packaging workflows (InstallShield, WiX, Advanced Installer) that call csc.exe or msbuild.exe from staging directories under ProgramData
Download portable Sigma rule (.yml)

Other platforms for T1127


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1MSBuild Inline Task Execution via Malicious Project File

    Expected signal: Sysmon Event ID 1: Process Create for MSBuild.exe with CommandLine referencing %TEMP%\malicious.csproj. Sysmon Event ID 11: File Create for %TEMP%\malicious.csproj. Sysmon Event ID 1 child: cmd.exe spawned by MSBuild.exe with /c whoami argument. Sysmon Event ID 11: File Create for %TEMP%\msbuild-test.txt. Security Event ID 4688 for both MSBuild.exe and cmd.exe if command line auditing is enabled.

  2. Test 2On-the-Fly C# Compilation and Execution via csc.exe

    Expected signal: Sysmon Event ID 11: File Create for %TEMP%\df00tech_test.cs. Sysmon Event ID 1: Process Create for csc.exe with CommandLine referencing %TEMP% source and output paths. Sysmon Event ID 11: File Create for %TEMP%\df00tech_test.exe and %TEMP%\df00tech_test.pdb. Sysmon Event ID 1: Process Create for %TEMP%\df00tech_test.exe (unsigned binary from temp path). AmCache will record the new executable's first execution.

  3. Test 3Shellcode Execution via CDB.exe Debugger with Command Script Flag

    Expected signal: Sysmon Event ID 1: Process Create for cdb.exe with CommandLine containing -c, -pv, and -pd flags. Sysmon Event ID 1: Process Create for notepad.exe spawned by cdb.exe. Security Event ID 4688 for cdb.exe if command line auditing enabled. The -c flag content (.echo) will appear in the command line.

  4. Test 4Tracker.exe Proxy Execution via /d3 Logging Flag

    Expected signal: Sysmon Event ID 1: Process Create for Tracker.exe with CommandLine containing /d3 and referencing a DLL. Sysmon Event ID 7: Image Load events for shell32.dll under the Tracker.exe process context. Sysmon Event ID 1: Process Create for whoami.exe as a child of Tracker.exe. Security Event ID 4688 for Tracker.exe and whoami.exe.

Unlock Pro Content

Get the full detection package for T1127 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections