Analysis
- max time kernel
90s - max time network
139s - platform
windows10-2004_x64 - resource
win10v2004-20220414-en - submitted
03/07/2022, 03:52
Static task
static1
Behavioral task
behavioral1
Sample
3d3747aa4e6eb4782c1ae5bcb22b736cce54a41a810cd571f9b7eaa34896e9dd.exe
Resource
win7-20220414-en
0 signatures
0 seconds
Behavioral task
behavioral2
Sample
3d3747aa4e6eb4782c1ae5bcb22b736cce54a41a810cd571f9b7eaa34896e9dd.exe
Resource
win10v2004-20220414-en
0 signatures
0 seconds
General
- Target 3d3747aa4e6eb4782c1ae5bcb22b736cce54a41a810cd571f9b7eaa34896e9dd.exe
- Size 434KB
- Sample220703-ee4f5sgah2
- SHA256 3d3747aa4e6eb4782c1ae5bcb22b736cce54a41a810cd571f9b7eaa34896e9dd
- MD5 660f957f13470d2f9c34713c192920b2
- SHA1 07998033267d6a0c8cc6a562c78d9caadaafa918
- SHA512 7c09911d02ad0d8e05615b80cf228c186b319177beea26e899d5e054f2f35c42187f37b7a5a3d567e3663505aae39f1de274b3be86b1ccf22df2df168ac162cd
- 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/4860-131-0x00000000008A0000-0x00000000008E9000-memory.dmp family_onlylogger behavioral2/memory/4860-132-0x0000000000400000-0x000000000089C000-memory.dmp family_onlylogger behavioral2/memory/4860-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 3d3747aa4e6eb4782c1ae5bcb22b736cce54a41a810cd571f9b7eaa34896e9dd.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 3548 4860 WerFault.exe 80 4908 4860 WerFault.exe 80 2040 4860 WerFault.exe 80 4392 4860 WerFault.exe 80 5080 4860 WerFault.exe 80 4360 4860 WerFault.exe 80 1604 4860 WerFault.exe 80 - Kills process with taskkill 1 IoCs
pid Process 3696 taskkill.exe - Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 3696 taskkill.exe - Suspicious use of WriteProcessMemory 6 IoCs
description pid Process procid_target PID 4860 wrote to memory of 3940 4860 3d3747aa4e6eb4782c1ae5bcb22b736cce54a41a810cd571f9b7eaa34896e9dd.exe 94 PID 4860 wrote to memory of 3940 4860 3d3747aa4e6eb4782c1ae5bcb22b736cce54a41a810cd571f9b7eaa34896e9dd.exe 94 PID 4860 wrote to memory of 3940 4860 3d3747aa4e6eb4782c1ae5bcb22b736cce54a41a810cd571f9b7eaa34896e9dd.exe 94 PID 3940 wrote to memory of 3696 3940 cmd.exe 98 PID 3940 wrote to memory of 3696 3940 cmd.exe 98 PID 3940 wrote to memory of 3696 3940 cmd.exe 98
Processes
-
C:\Users\Admin\AppData\Local\Temp\3d3747aa4e6eb4782c1ae5bcb22b736cce54a41a810cd571f9b7eaa34896e9dd.exe"C:\Users\Admin\AppData\Local\Temp\3d3747aa4e6eb4782c1ae5bcb22b736cce54a41a810cd571f9b7eaa34896e9dd.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:4860 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4860 -s 7362⤵
- Program crash
PID:3548
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4860 -s 7922⤵
- Program crash
PID:4908
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4860 -s 7242⤵
- Program crash
PID:2040
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4860 -s 7402⤵
- Program crash
PID:4392
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4860 -s 7402⤵
- Program crash
PID:5080
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4860 -s 9482⤵
- Program crash
PID:4360
-
-
C:\Windows\SysWOW64\cmd.exe"C:\Windows\System32\cmd.exe" /c taskkill /im "3d3747aa4e6eb4782c1ae5bcb22b736cce54a41a810cd571f9b7eaa34896e9dd.exe" /f & erase "C:\Users\Admin\AppData\Local\Temp\3d3747aa4e6eb4782c1ae5bcb22b736cce54a41a810cd571f9b7eaa34896e9dd.exe" & exit2⤵
- Suspicious use of WriteProcessMemory
PID:3940 -
C:\Windows\SysWOW64\taskkill.exetaskkill /im "3d3747aa4e6eb4782c1ae5bcb22b736cce54a41a810cd571f9b7eaa34896e9dd.exe" /f3⤵
- Kills process with taskkill
- Suspicious use of AdjustPrivilegeToken
PID:3696
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4860 -s 11082⤵
- Program crash
PID:1604
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 360 -p 4860 -ip 48601⤵PID:4640
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 452 -p 4860 -ip 48601⤵PID:2264
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 468 -p 4860 -ip 48601⤵PID:4892
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 384 -p 4860 -ip 48601⤵PID:1992
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 384 -p 4860 -ip 48601⤵PID:364
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 488 -p 4860 -ip 48601⤵PID:1272
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 484 -p 4860 -ip 48601⤵PID:2972