Analysis
-
max time kernel
112s -
max time network
138s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
07-07-2022 11:06
Static task
static1
Behavioral task
behavioral1
Sample
45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe
Resource
win7-20220414-en
Behavioral task
behavioral2
Sample
45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe
Resource
win10v2004-20220414-en
General
-
Target
45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe
-
Size
136KB
-
MD5
0c8d4181cfb8a34505b231c7d0fdc401
-
SHA1
ab6d29707a9121b2267d213cec0edbf0d9f896f1
-
SHA256
45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14
-
SHA512
d7f8e2a6d01f48f8591cbc297f1906416b810aa730e66c7618c9ab6d8e7ed1a68935bf38984b392c211a9d1186e1e8ba9f68ed7370f88b11b5568285adbb1a86
Malware Config
Signatures
-
Detect XtremeRAT payload 11 IoCs
Processes:
resource yara_rule behavioral2/memory/1180-133-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/1180-134-0x0000000010000000-0x0000000010047000-memory.dmp family_xtremerat behavioral2/memory/1180-135-0x0000000010000000-0x0000000010047000-memory.dmp family_xtremerat behavioral2/memory/1180-136-0x0000000010000000-0x0000000010047000-memory.dmp family_xtremerat behavioral2/memory/1180-138-0x0000000010000000-0x0000000010047000-memory.dmp family_xtremerat behavioral2/memory/4552-139-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/4552-140-0x0000000010000000-0x0000000010047000-memory.dmp family_xtremerat behavioral2/memory/4116-141-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/1180-142-0x0000000010000000-0x0000000010047000-memory.dmp family_xtremerat behavioral2/memory/4116-143-0x0000000010000000-0x0000000010047000-memory.dmp family_xtremerat behavioral2/memory/4552-144-0x0000000010000000-0x0000000010047000-memory.dmp family_xtremerat -
XtremeRAT
The XtremeRAT was developed by xtremecoder and has been available since at least 2010, and written in Delphi.
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exedescription pid Process procid_target PID 4624 set thread context of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Program crash 4 IoCs
Processes:
WerFault.exeWerFault.exeWerFault.exeWerFault.exepid pid_target Process procid_target 760 4116 WerFault.exe 84 2320 4552 WerFault.exe 83 4216 4116 WerFault.exe 84 4332 4552 WerFault.exe 83 -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exepid Process 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe -
Suspicious use of WriteProcessMemory 21 IoCs
Processes:
45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exedescription pid Process procid_target PID 4624 wrote to memory of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 PID 4624 wrote to memory of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 PID 4624 wrote to memory of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 PID 4624 wrote to memory of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 PID 4624 wrote to memory of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 PID 4624 wrote to memory of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 PID 4624 wrote to memory of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 PID 4624 wrote to memory of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 PID 4624 wrote to memory of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 PID 4624 wrote to memory of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 PID 4624 wrote to memory of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 PID 4624 wrote to memory of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 PID 4624 wrote to memory of 1180 4624 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 82 PID 1180 wrote to memory of 4552 1180 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 83 PID 1180 wrote to memory of 4552 1180 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 83 PID 1180 wrote to memory of 4552 1180 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 83 PID 1180 wrote to memory of 4552 1180 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 83 PID 1180 wrote to memory of 4116 1180 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 84 PID 1180 wrote to memory of 4116 1180 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 84 PID 1180 wrote to memory of 4116 1180 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 84 PID 1180 wrote to memory of 4116 1180 45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe 84
Processes
-
C:\Users\Admin\AppData\Local\Temp\45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe"C:\Users\Admin\AppData\Local\Temp\45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4624 -
C:\Users\Admin\AppData\Local\Temp\45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe"C:\Users\Admin\AppData\Local\Temp\45b2938ed3ae72cc8079d9730fa948c7919500da3bf52b7385f8725c72c18d14.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1180 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:4552
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4552 -s 4884⤵
- Program crash
PID:2320
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4552 -s 4964⤵
- Program crash
PID:4332
-
-
-
C:\Windows\SysWOW64\notepad.exenotepad.exe3⤵PID:4116
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4116 -s 4804⤵
- Program crash
PID:760
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4116 -s 4884⤵
- Program crash
PID:4216
-
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 4552 -ip 45521⤵PID:3896
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 436 -p 4116 -ip 41161⤵PID:2580
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 560 -p 4116 -ip 41161⤵PID:3456
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 588 -p 4552 -ip 45521⤵PID:4268