ATT&CK coverage › Technique
Trusted Developer Utilities Proxy Execution T1127
Adversaries may take advantage of trusted developer utilities to proxy execution of malicious payloads. There are many utilities used for software development related tasks that can be used to execute code in various forms to assist in development, debugging, and reverse engineering. These utilities may often be signed with legitimate certificates that allow them to execute on a system and proxy execution of malicious code through a trusted process that effectively bypasses application control solutions.
Events covered
6 catalog events are tagged with this technique by at least one rule.
Authoring guide
Patterns shared across the 22 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (11 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (106 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique.
Common exclusions (3 distinct)
Field/operator/value combinations that rules under this technique routinely exclude (top-level not() clauses). These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 19 rules
- AspNetCompiler Execution
- C# IL Code Compilation Via Ilasm.EXE
- Detection of PowerShell Execution via Sqlps.exe
- JScript Compiler Execution
- Kavremover Dropped Binary LOLBIN Usage
- Node Process Executions
- Potential Arbitrary Code Execution Via Node.EXE
- Potential Binary Proxy Execution Via Cdb.EXE
- Potential Mftrace.EXE Abuse
- Potentially Suspicious ASP.NET Compilation Via AspNetCompiler
- Remote Thread Creation Ttdinject.exe Proxy
- SQL Client Tools PowerShell Session Detection
- Suspicious Child Process of AspNetCompiler
- Suspicious File Created by ArcSOC.exe
- Suspicious Use of CSharp Interactive Console
- Use of Remote.exe
- Use of TTDInject.exe
- Use of VSIISExeLauncher.exe
- Use of Wfc.exe