Analysis
- max time kernel
150s - max time network
151s - platform
windows10-2004_x64 - resource
win10v2004-20240226-en - resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system - submitted
20/03/2024, 03:58
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
d7d3f6f2cc55eab8d6aa69a0250326aa.exe
Resource
win7-20240220-en
6 signatures
150 seconds
Behavioral task
behavioral2
Sample
d7d3f6f2cc55eab8d6aa69a0250326aa.exe
Resource
win10v2004-20240226-en
7 signatures
150 seconds
General
- Target d7d3f6f2cc55eab8d6aa69a0250326aa.exe
- Size 240KB
- Sample240320-ejjbrsgg2y
- SHA256 971b24b1a066cd7d50bab115fcc975f6e686091188a36e8ae4ca5635b18814da
- MD5 d7d3f6f2cc55eab8d6aa69a0250326aa
- SHA1 e8143a56e0de00dd39a031debfd7d88d6876006b
- SHA512 a5d0e84bb37bd95d90051711fc3efa77df70a1dc09c1d3f37fd266bdab77d5f1b1e4294efa519fdea9d5885617686595d7c1066073c3064779cabf04ef70bc9d
- SSDEEP 6144:H3nWKZPImc6V3RZQzwSyArvjACr9/z4hFZVj8aFHvb:H39ZPIeV3zQzlr9L4hFZ9HT
- MD5 SHA1 SHA512 SSDEEP
Score
10/10
Malware Config
Signatures
- Detect XtremeRAT payload 7 IoCs
resource yara_rule behavioral2/memory/3860-3-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/3860-6-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/3860-4-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/3860-7-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/5004-8-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/3860-9-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/5004-10-0x0000000010000000-0x0000000010048000-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
description pid Process procid_target PID 2512 set thread context of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 - Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
- Program crash 2 IoCs
pid pid_target Process procid_target 4448 5004 WerFault.exe 92 2636 5004 WerFault.exe 92 - Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe - Suspicious use of WriteProcessMemory 20 IoCs
description pid Process procid_target PID 2512 wrote to memory of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 PID 2512 wrote to memory of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 PID 2512 wrote to memory of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 PID 2512 wrote to memory of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 PID 2512 wrote to memory of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 PID 2512 wrote to memory of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 PID 2512 wrote to memory of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 PID 2512 wrote to memory of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 PID 2512 wrote to memory of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 PID 2512 wrote to memory of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 PID 2512 wrote to memory of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 PID 2512 wrote to memory of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 PID 2512 wrote to memory of 3860 2512 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 91 PID 3860 wrote to memory of 5004 3860 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 92 PID 3860 wrote to memory of 5004 3860 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 92 PID 3860 wrote to memory of 5004 3860 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 92 PID 3860 wrote to memory of 5004 3860 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 92 PID 3860 wrote to memory of 2608 3860 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 94 PID 3860 wrote to memory of 2608 3860 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 94 PID 3860 wrote to memory of 2608 3860 d7d3f6f2cc55eab8d6aa69a0250326aa.exe 94
Processes
-
C:\Users\Admin\AppData\Local\Temp\d7d3f6f2cc55eab8d6aa69a0250326aa.exe"C:\Users\Admin\AppData\Local\Temp\d7d3f6f2cc55eab8d6aa69a0250326aa.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2512 -
C:\Users\Admin\AppData\Local\Temp\d7d3f6f2cc55eab8d6aa69a0250326aa.exe"C:\Users\Admin\AppData\Local\Temp\d7d3f6f2cc55eab8d6aa69a0250326aa.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:3860 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:5004
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 5004 -s 4804⤵
- Program crash
PID:4448
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 5004 -s 4884⤵
- Program crash
PID:2636
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:2608
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 5004 -ip 50041⤵PID:2564
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 516 -p 5004 -ip 50041⤵PID:1820