Analysis
-
max time kernel
91s -
max time network
157s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
resource tags
arch:x64arch:x86image:win10v2004-20220414-enlocale:en-usos:windows10-2004-x64system -
submitted
18-07-2022 23:39
Static task
static1
Behavioral task
behavioral1
Sample
5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe
Resource
win7-20220718-en
Behavioral task
behavioral2
Sample
5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe
Resource
win10v2004-20220414-en
General
-
Target
5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe
-
Size
435KB
-
MD5
745e587c3cf97e13028cb0dea38d7e8f
-
SHA1
f046ffbc0f66c24d075100862c82c99e61958f62
-
SHA256
5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a
-
SHA512
9a339d0e9fd5dac834b80314e3390ebb4cc5dc48848a9f9fdd647d4c543de275bef010c01d34af1264fd111d8be650d388c4a3aa4efc7fb43d23c9e1ef1f19a8
Malware Config
Signatures
-
OnlyLogger
A tiny loader that uses IPLogger to get its payload.
-
OnlyLogger payload 3 IoCs
Processes:
resource yara_rule behavioral2/memory/4260-131-0x0000000000AF0000-0x0000000000B39000-memory.dmp family_onlylogger behavioral2/memory/4260-132-0x0000000000400000-0x000000000089C000-memory.dmp family_onlylogger behavioral2/memory/4260-135-0x0000000000400000-0x000000000089C000-memory.dmp family_onlylogger -
Checks computer location settings 2 TTPs 1 IoCs
Looks up country code configured in the registry, likely geofence.
Processes:
5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exedescription ioc process Key value queried \REGISTRY\USER\S-1-5-21-1809750270-3141839489-3074374771-1000\Control Panel\International\Geo\Nation 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Program crash 7 IoCs
Processes:
WerFault.exeWerFault.exeWerFault.exeWerFault.exeWerFault.exeWerFault.exeWerFault.exepid pid_target process target process 2300 4260 WerFault.exe 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe 3616 4260 WerFault.exe 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe 1056 4260 WerFault.exe 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe 4220 4260 WerFault.exe 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe 4480 4260 WerFault.exe 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe 4316 4260 WerFault.exe 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe 4784 4260 WerFault.exe 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe -
Kills process with taskkill 1 IoCs
Processes:
taskkill.exepid process 768 taskkill.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
taskkill.exedescription pid process Token: SeDebugPrivilege 768 taskkill.exe -
Suspicious use of WriteProcessMemory 6 IoCs
Processes:
5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.execmd.exedescription pid process target process PID 4260 wrote to memory of 380 4260 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe cmd.exe PID 4260 wrote to memory of 380 4260 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe cmd.exe PID 4260 wrote to memory of 380 4260 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe cmd.exe PID 380 wrote to memory of 768 380 cmd.exe taskkill.exe PID 380 wrote to memory of 768 380 cmd.exe taskkill.exe PID 380 wrote to memory of 768 380 cmd.exe taskkill.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe"C:\Users\Admin\AppData\Local\Temp\5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 6882⤵
- Program crash
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 7122⤵
- Program crash
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 9442⤵
- Program crash
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 7962⤵
- Program crash
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 7962⤵
- Program crash
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 9882⤵
- Program crash
-
C:\Windows\SysWOW64\cmd.exe"C:\Windows\System32\cmd.exe" /c taskkill /im "5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe" /f & erase "C:\Users\Admin\AppData\Local\Temp\5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe" & exit2⤵
- Suspicious use of WriteProcessMemory
-
C:\Windows\SysWOW64\taskkill.exetaskkill /im "5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe" /f3⤵
- Kills process with taskkill
- Suspicious use of AdjustPrivilegeToken
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 9442⤵
- Program crash
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 396 -p 4260 -ip 42601⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 196 -p 4260 -ip 42601⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 500 -p 4260 -ip 42601⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 552 -p 4260 -ip 42601⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 544 -p 4260 -ip 42601⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 564 -p 4260 -ip 42601⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 620 -p 4260 -ip 42601⤵
Network
MITRE ATT&CK Matrix ATT&CK v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/380-133-0x0000000000000000-mapping.dmp
-
memory/768-134-0x0000000000000000-mapping.dmp
-
memory/4260-130-0x00000000008D3000-0x00000000008FC000-memory.dmpFilesize
164KB
-
memory/4260-131-0x0000000000AF0000-0x0000000000B39000-memory.dmpFilesize
292KB
-
memory/4260-132-0x0000000000400000-0x000000000089C000-memory.dmpFilesize
4.6MB
-
memory/4260-135-0x0000000000400000-0x000000000089C000-memory.dmpFilesize
4.6MB