LoFP LoFP / t1036.003

t1036.003

TitleTags
a certain amount of false positives are likely with this detection. msi based installers often trigger for setupapl.dll and vendors will often copy system exectables to a different path for application usage.
administrators who rename binaries (should be investigated).
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.
commandlines with legitimate cyrillic text; will likely require tuning (or not be usable) in countries where these alphabets are in use.
copying files from system directories can happen for multiple admin reasons, allbeit rare without approval. apply additional filters where needed.
custom applications use renamed binaries adding slight change to binary name. typically this is easy to spot and add to whitelist
depend on scripts and administrative tools used in the monitored environment (for example an admin scripts like https://www.itexperience.net/sccm-batch-files-and-32-bits-processes-on-64-bits-os/)
false positives may be present and filtering may be required. certain utilities will run from non-standard paths based on the third-party application in use.
file names with legitimate cyrillic text. will likely require tuning (or not be usable) in countries where these alphabets are in use.
installers and updaters may set currently in use files for rename or deletion after a reboot.
legitimate powershell scripts
legitimate use of the tool by administrators or users to update metadata of a binary
no false positives have been identified at this time.
procdump illegally bundled with legitimate software.
psexec installed via windows store doesn't contain original filename field (false negative)
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.
some legitimate apps use this, but limited.
some security products seem to spawn these
this detection may require tuning based on third party applications utilizing native windows binaries in non-standard paths.
unknown
unlikely
when cmd.exe and xcopy.exe are called directly
when the command contains the keywords but not in the correct order