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
7 signatures
150 seconds
Behavioral task
behavioral2
Sample
5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe
Resource
win10v2004-20220414-en
8 signatures
150 seconds
General
- Target 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe
- Size 435KB
- Sample220718-3nfy7sdaa2
- SHA256 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a
- MD5 745e587c3cf97e13028cb0dea38d7e8f
- SHA1 f046ffbc0f66c24d075100862c82c99e61958f62
- SHA512 9a339d0e9fd5dac834b80314e3390ebb4cc5dc48848a9f9fdd647d4c543de275bef010c01d34af1264fd111d8be650d388c4a3aa4efc7fb43d23c9e1ef1f19a8
- MD5 SHA1 SHA512
Score
10/10
Malware Config
Signatures
- OnlyLogger
A tiny loader that uses IPLogger to get its payload.
- OnlyLogger payload 3 IoCs
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.
description 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
pid pid_target Process procid_target 2300 4260 WerFault.exe 80 3616 4260 WerFault.exe 80 1056 4260 WerFault.exe 80 4220 4260 WerFault.exe 80 4480 4260 WerFault.exe 80 4316 4260 WerFault.exe 80 4784 4260 WerFault.exe 80 - Kills process with taskkill 1 IoCs
pid Process 768 taskkill.exe - Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 768 taskkill.exe - Suspicious use of WriteProcessMemory 6 IoCs
description pid Process procid_target PID 4260 wrote to memory of 380 4260 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe 93 PID 4260 wrote to memory of 380 4260 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe 93 PID 4260 wrote to memory of 380 4260 5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe 93 PID 380 wrote to memory of 768 380 cmd.exe 97 PID 380 wrote to memory of 768 380 cmd.exe 97 PID 380 wrote to memory of 768 380 cmd.exe 97
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
PID:4260 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 6882⤵
- Program crash
PID:2300
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 7122⤵
- Program crash
PID:3616
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 9442⤵
- Program crash
PID:1056
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 7962⤵
- Program crash
PID:4220
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 7962⤵
- Program crash
PID:4480
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 9882⤵
- Program crash
PID:4316
-
-
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
PID:380 -
C:\Windows\SysWOW64\taskkill.exetaskkill /im "5083a072f5be065e151d3116ac3f78b0a9322897f9c2fe9e18d0c477b943540a.exe" /f3⤵
- Kills process with taskkill
- Suspicious use of AdjustPrivilegeToken
PID:768
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 9442⤵
- Program crash
PID:4784
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 396 -p 4260 -ip 42601⤵PID:804
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 196 -p 4260 -ip 42601⤵PID:4896
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 500 -p 4260 -ip 42601⤵PID:5088
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 552 -p 4260 -ip 42601⤵PID:4144
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 544 -p 4260 -ip 42601⤵PID:4324
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 564 -p 4260 -ip 42601⤵PID:4104
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 620 -p 4260 -ip 42601⤵PID:2264