Analysis
-
max time kernel
69s -
max time network
91s -
platform
windows10-2004_x64 -
resource
win10v2004-20220715-en -
resource tags
arch:x64arch:x86image:win10v2004-20220715-enlocale:en-usos:windows10-2004-x64system -
submitted
17-07-2022 00:32
Static task
static1
Behavioral task
behavioral1
Sample
533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe
Resource
win7-20220715-en
Behavioral task
behavioral2
Sample
533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe
Resource
win10v2004-20220715-en
General
-
Target
533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe
-
Size
435KB
-
MD5
fe7a8129af968c9075a7b59d1f590135
-
SHA1
d818dfbd8de817570319bb767489e4822cee1f83
-
SHA256
533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983
-
SHA512
fbd8df5e8213976a710d8ae4ba245a2d6baef37805afb298bbe4e033b13252e46ad7e53b493fd9a9a98bb85bf1ab08b271b0535bd757006281852786583bedea
Malware Config
Signatures
-
OnlyLogger
A tiny loader that uses IPLogger to get its payload.
-
OnlyLogger payload 4 IoCs
Processes:
resource yara_rule behavioral2/memory/4344-132-0x00000000009A0000-0x00000000009E9000-memory.dmp family_onlylogger behavioral2/memory/4344-133-0x0000000000400000-0x000000000089D000-memory.dmp family_onlylogger behavioral2/memory/4344-135-0x00000000009A0000-0x00000000009E9000-memory.dmp family_onlylogger behavioral2/memory/4344-138-0x0000000000400000-0x000000000089D000-memory.dmp family_onlylogger -
Checks computer location settings 2 TTPs 1 IoCs
Looks up country code configured in the registry, likely geofence.
Processes:
533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exedescription ioc process Key value queried \REGISTRY\USER\S-1-5-21-2280897447-3291712302-3137480060-1000\Control Panel\International\Geo\Nation 533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.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 4556 4344 WerFault.exe 533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe 2904 4344 WerFault.exe 533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe 3084 4344 WerFault.exe 533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe 768 4344 WerFault.exe 533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe 3344 4344 WerFault.exe 533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe 64 4344 WerFault.exe 533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe 4868 4344 WerFault.exe 533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe -
Kills process with taskkill 1 IoCs
Processes:
taskkill.exepid process 4088 taskkill.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
taskkill.exedescription pid process Token: SeDebugPrivilege 4088 taskkill.exe -
Suspicious use of WriteProcessMemory 6 IoCs
Processes:
533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.execmd.exedescription pid process target process PID 4344 wrote to memory of 1568 4344 533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe cmd.exe PID 4344 wrote to memory of 1568 4344 533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe cmd.exe PID 4344 wrote to memory of 1568 4344 533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe cmd.exe PID 1568 wrote to memory of 4088 1568 cmd.exe taskkill.exe PID 1568 wrote to memory of 4088 1568 cmd.exe taskkill.exe PID 1568 wrote to memory of 4088 1568 cmd.exe taskkill.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe"C:\Users\Admin\AppData\Local\Temp\533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:4344 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4344 -s 6962⤵
- Program crash
PID:4556
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4344 -s 7922⤵
- Program crash
PID:2904
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4344 -s 9202⤵
- Program crash
PID:3084
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4344 -s 9322⤵
- Program crash
PID:768
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4344 -s 9322⤵
- Program crash
PID:3344
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4344 -s 9682⤵
- Program crash
PID:64
-
-
C:\Windows\SysWOW64\cmd.exe"C:\Windows\System32\cmd.exe" /c taskkill /im "533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe" /f & erase "C:\Users\Admin\AppData\Local\Temp\533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe" & exit2⤵
- Suspicious use of WriteProcessMemory
PID:1568 -
C:\Windows\SysWOW64\taskkill.exetaskkill /im "533ab0f4560b3c599c44d1c7bfa716205663b30b510f820cf896d1e30d89b983.exe" /f3⤵
- Kills process with taskkill
- Suspicious use of AdjustPrivilegeToken
PID:4088
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4344 -s 11322⤵
- Program crash
PID:4868
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 4344 -ip 43441⤵PID:4516
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 544 -p 4344 -ip 43441⤵PID:372
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 432 -p 4344 -ip 43441⤵PID:2024
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 500 -p 4344 -ip 43441⤵PID:4232
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 540 -p 4344 -ip 43441⤵PID:3456
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 556 -p 4344 -ip 43441⤵PID:1696
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 552 -p 4344 -ip 43441⤵PID:1464