LoFP LoFP / t1127

t1127

TitleTags
although unlikely, limited instances have been identified coming from native microsoft utilities similar to sccm.
although unlikely, some legitimate applications may exhibit this behavior, triggering a false positive.
although unlikely, some legitimate applications may use a moved copy of microsoft.workflow.compiler.exe, triggering a false positive.
although unlikely, some legitimate applications may use a moved copy of msbuild, triggering a false positive.
approved installs of windows sdk with debugging tools for windows (windbg).
direct ps command execution through sqlps.exe is uncommon, childprocess sqlps.exe spawned by sqlagent.exe is a legitimate action.
direct ps command execution through sqltoolsps.exe is uncommon, childprocess sqltoolsps.exe spawned by smss.exe is a legitimate action.
false positives should be limited as developers do not spawn msbuild via a wsh.
legitimate mwc use (unlikely in modern enterprise environments)
legitimate use
legitimate use by a software developer
legitimate use for tracing purposes
legitimate use of debugging tools
legitimate use to compile jscript by developers.
possible depending on environment. pair with other factors such as net connections, command-line args, etc.
some legitimate applications may use a moved copy of msbuild.exe, triggering a false positive. baselining of msbuild.exe usage is recommended to better understand it's path usage. visual studio runs an instance out of a path that will need to be filtered on.
the build engine is commonly used by windows developers but use by non-engineers is unusual. it is quite unusual for this program to be started by an office application like word or excel.
these programs may be used by windows developers but use by non-engineers is unusual.
unlikely