t1036 | LoFP

t1036

Title	Tags
administrative activity	t1003 t1016 t1021 t1021.001 t1027 t1036 t1053 t1053.005 t1059 t1059.001 t1059.005 t1071 t1071.001 t1087 t1087.001 t1087.002 t1098 t1105 t1133 t1134 t1136 t1136.001 t1137 t1222 t1222.001 t1505 t1505.004 t1552 t1552.006 t1555 t1555.004 t1562 t1562.001 t1572 t1615 windows linux sigma
administrative activity (adjust code pages according to your organization's region)	t1036 windows sigma
administrators may allow creation of script or exe in the paths specified. filter as needed.	t1036 t1091 endpoint splunk
administrators who rename binaries (should be investigated)	t1036 t1036.003 windows sigma
although unlikely, some legitimate applications may use a moved copy of microsoft.workflow.compiler.exe, triggering a false positive.	t1036 t1036.003 t1127 endpoint splunk
although unlikely, some legitimate applications may use a moved copy of msbuild, triggering a false positive.	t1036 t1036.003 t1127 t1127.001 endpoint splunk
although unlikely, some legitimate applications may use a moved copy of rundll32, triggering a false positive.	t1036 t1036.003 t1218 t1218.011 endpoint splunk
another tool that uses command line flags similar to procdump	t1003 t1003.001 t1036 windows sigma
another tool that uses the command line switches of xordump	t1003 t1003.001 t1036 windows sigma
because the recycle bin is a hidden folder in modern versions of windows, it would be unusual for a process other than explorer.exe to write to it. incidents should be investigated as appropriate.	t1036 windows splunk
citrix	t1036 windows sigma
command lines that use the same flags	t1003 t1003.001 t1036 windows sigma
commandlines that contains scriptures such as arabic or hebrew might make use of this character	t1036 t1036.002 windows sigma
commandlines with legitimate cyrillic text; will likely require tuning (or not be usable) in countries where these alphabets are in use.	t1036 t1036.003 windows sigma
custom applications use renamed binaries adding slight change to binary name. typically this is easy to spot and add to whitelist	t1036 t1036.003 windows sigma
custom windows error reporting debugger or applications restarted by werfault after a crash.	t1036 t1546 windows elastic
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/)	t1036 t1036.003 windows sigma
every user may do this event but very un-ussual.	t1036 t1036.003 endpoint splunk
exotic software	t1036 windows sigma
false positives are expected in cases in which procdump just gets copied to a different directory without any renaming	t1003 t1003.001 t1036 windows sigma
false positives depend on scripts and administrative tools used in the monitored environment	t1036 t1059 t1059.007 t1082 t1087 t1105 t1140 t1218 t1218.005 t1218.007 t1218.011 windows sigma
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.	t1036 t1036.003 t1218 T1218.004 endpoint splunk
file names with legitimate cyrillic text. will likely require tuning (or not be usable) in countries where these alphabets are in use.	t1036 t1036.003 windows sigma
google drive	t1036 windows sigma
implementation in regions that use right to left in native language.	t1036 t1036.002 endpoint splunk
installers and updaters may set currently in use files for rename after a reboot.	t1036 t1036.003 windows sigma
it is possible that other utilities or system processes may legitimately write to this folder. investigate and modify the search to include exceptions as appropriate.	t1036 windows splunk
legit application crash with rare werfault commandline value	t1036 windows elastic
legitimate powershell scripts	t1003 t1003.003 t1003.006 t1033 t1036 t1036.003 t1057 t1070 t1070.003 t1083 t1201 t1546 t1546.015 t1553 t1553.005 t1562 t1562.001 t1564 t1564.006 t1615 windows sigma
legitimate software that uses these patterns	t1036 t1059 t1059.004 t1140 linux sigma
legitimate use of procdump by a developer or administrator	t1003 t1003.001 t1036 windows sigma
legitimate use of the tool by administrators or users to update metadata of a binary	t1027 t1027.005 t1036 t1036.003 windows sigma
legitimate used of encrypted zip files	t1027 t1036 t1105 t1566 t1566.001 windows sigma
mistyped commands or legitimate binaries named to match the pattern	t1036 t1036.006 macos sigma
procdump illegaly bundled with legitimate software	t1036 t1036.003 windows sigma
psexec installed via windows store doesn't contain original filename field (false negative)	t1036 t1036.003 windows sigma
russian speaking people changing the codepage	t1036 windows sigma
some administrator activity can be potentially triggered, please add those users to the filter macro.	t1003 t1036 t1036.005 t1595 endpoint splunk
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.	t1036 t1036.003 t1127 t1127.001 endpoint splunk
some legitimate apps use this, but limited.	t1036 t1036.003 t1197 windows sigma
some security products seem to spawn these	t1036 t1036.003 t1036.005 windows sigma
some tuning is required for other general purpose directories of third party apps	t1036 t1036.007 windows sigma
system components such as daemon-set-controller and kube-scheduler also create pods in the kube-system namespace	t1036 t1036.005 kubernetes sigma
system processes copied outside their default folders for testing purposes	t1036 t1036.005 windows sigma
third party software naming their software with the same names as the processes mentioned here	t1036 t1036.005 windows sigma
this detection may require tuning based on third party applications utilizing native windows binaries in non-standard paths.	t1036 t1036.003 endpoint splunk
this is meant to run only on datasources using elastic agent 7.14+ since versions prior to that will be missing the necessary field, resulting in false positives.	t1036 cross-platform elastic
unknown flash download locations	t1036 t1036.005 t1189 t1204 t1204.002 sigma
unlikely	t1003 t1003.001 t1003.002 t1003.004 t1003.005 t1003.006 t1005 t1007 t1008 t1012 t1014 t1016 t1018 t1021 t1021.002 t1021.003 t1021.006 t1027 t1027.005 t1033 t1036 t1036.003 t1036.007 t1041 t1046 t1047 t1048 t1048.001 t1053 t1053.003 t1053.005 t1055 t1055.001 t1056 t1057 t1059 t1059.001 t1059.002 t1059.003 t1068 t1070 t1071 t1071.001 t1071.004 t1078 t1082 t1083 t1087 t1090 t1090.001 t1090.003 t1105 t1106 t1112 t1115 t1123 t1127 t1132 t1132.001 t1133 t1134 t1134.001 t1134.002 t1134.004 t1136 t1136.001 t1136.002 t1137 t1137.002 t1140 t1190 t1203 t1204 t1210 t1213 t1213.003 t1216 t1218 t1218.008 t1218.010 t1218.011 t1218.013 t1219 t1486 t1489 t1490 t1496 t1498 t1499 t1499.001 t1505 t1505.003 t1526 t1528 t1543 t1543.003 t1546 t1546.008 t1548 t1548.003 t1550 t1550.003 t1552 t1553 t1553.004 t1555 t1556 t1557 t1557.001 t1558 t1558.003 t1562 t1562.001 t1562.002 t1562.010 t1564 t1564.004 t1566 t1569 t1569.002 t1570 t1574 t1574.001 t1574.002 t1586 t1587 t1587.001 t1588 t1588.002 t1590 t1590.001 t1590.002 t1620 t1649 bitbucket azure m365 okta macos windows linux opencanary sigma
unlikely, because no one should dump an lsass process memory	t1003 t1003.001 t1036 windows sigma
when cmd.exe and xcopy.exe are called directly	t1036 t1036.003 windows sigma
when the command contains the keywords but not in the correct order	t1036 t1036.003 windows sigma