Analysis
-
max time kernel
90s -
max time network
139s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
28/10/2022, 21:55
Static task
static1
Behavioral task
behavioral1
Sample
d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe
Resource
win10v2004-20220901-en
General
-
Target
d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe
-
Size
210KB
-
MD5
0f51672a55a399ae1f55d193587b1fb0
-
SHA1
8d9fd2d1e0008c01426f81cfb287b1a5455eaa0e
-
SHA256
d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6
-
SHA512
8544a19d9be192f8c4c629dfb7b3f270469ebb6fe77c1a6988db014e420a147eac5b786c68bdc9ec72446a13d9258d94fff334d474920834c6129cc7602527d2
-
SSDEEP
3072:GQSX9ZtY+aNukDvGHZKEhfrFm3BVexFd2X3FvJ/XjO0gfOws3e8ssslHixkSHir3:GQmmM55KEJronrBtXjOV/GI
Malware Config
Extracted
xtremerat
Svicen2010dj.zapto.org
Signatures
-
Detect XtremeRAT payload 4 IoCs
resource yara_rule behavioral2/memory/1324-138-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/1368-139-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/1324-140-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/1368-141-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat -
XtremeRAT
The XtremeRAT was developed by xtremecoder and has been available since at least 2010, and written in Delphi.
-
resource yara_rule behavioral2/memory/1324-135-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/1324-137-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/1324-138-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/1324-140-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/1368-141-0x0000000010000000-0x000000001004D000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4896 set thread context of 1324 4896 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 83 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Program crash 2 IoCs
pid pid_target Process procid_target 1556 1368 WerFault.exe 84 1836 1368 WerFault.exe 84 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4896 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe -
Suspicious use of WriteProcessMemory 15 IoCs
description pid Process procid_target PID 4896 wrote to memory of 1324 4896 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 83 PID 4896 wrote to memory of 1324 4896 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 83 PID 4896 wrote to memory of 1324 4896 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 83 PID 4896 wrote to memory of 1324 4896 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 83 PID 4896 wrote to memory of 1324 4896 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 83 PID 4896 wrote to memory of 1324 4896 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 83 PID 4896 wrote to memory of 1324 4896 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 83 PID 4896 wrote to memory of 1324 4896 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 83 PID 1324 wrote to memory of 1368 1324 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 84 PID 1324 wrote to memory of 1368 1324 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 84 PID 1324 wrote to memory of 1368 1324 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 84 PID 1324 wrote to memory of 1368 1324 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 84 PID 1324 wrote to memory of 1580 1324 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 85 PID 1324 wrote to memory of 1580 1324 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 85 PID 1324 wrote to memory of 1580 1324 d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe 85
Processes
-
C:\Users\Admin\AppData\Local\Temp\d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe"C:\Users\Admin\AppData\Local\Temp\d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4896 -
C:\Users\Admin\AppData\Local\Temp\d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exeC:\Users\Admin\AppData\Local\Temp\d2aeef4cfda303e6ba76ea2bb618f7a4c0a79ffe925bf154aa8912c50b7b97f6.exe2⤵
- Suspicious use of WriteProcessMemory
PID:1324 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:1368
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1368 -s 4964⤵
- Program crash
PID:1556
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1368 -s 5044⤵
- Program crash
PID:1836
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:1580
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 180 -p 1368 -ip 13681⤵PID:1912
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 488 -p 1368 -ip 13681⤵PID:4832