Analysis
-
max time kernel
150s -
max time network
46s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
04/12/2022, 02:38
Static task
static1
Behavioral task
behavioral1
Sample
56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe
Resource
win10v2004-20220812-en
General
-
Target
56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe
-
Size
79KB
-
MD5
fed6c7287e92dfbabc86d972599e7e62
-
SHA1
0e8ce9e183c7f3b90b7216eb6dd08232c6264842
-
SHA256
56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710
-
SHA512
56d3a505e5422fb91be3ae94b091f5a83d7dc06a15b45067513bf6041d90eccd621e5e05fc1c5b86cb6f4a4e88e637058ecb7ef38c28f2ee8cac866cba3f99c4
-
SSDEEP
1536:/scQPQirHU2CkvfFn9vacey97WEaKa1EVTpuhzaRIv:/yBojsnvaPy93E1EaIRIv
Malware Config
Extracted
xtremerat
r4f4.no-ip.biz
Signatures
-
Detect XtremeRAT payload 6 IoCs
resource yara_rule behavioral1/memory/1724-61-0x0000000010000000-0x000000001004B000-memory.dmp family_xtremerat behavioral1/memory/1700-64-0x0000000000000000-mapping.dmp family_xtremerat behavioral1/memory/1724-66-0x0000000010000000-0x000000001004B000-memory.dmp family_xtremerat behavioral1/memory/1700-67-0x0000000010000000-0x000000001004B000-memory.dmp family_xtremerat behavioral1/memory/1724-68-0x0000000010000000-0x000000001004B000-memory.dmp family_xtremerat behavioral1/memory/1700-69-0x0000000010000000-0x000000001004B000-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 behavioral1/memory/1724-56-0x0000000010000000-0x000000001004B000-memory.dmp upx behavioral1/memory/1724-60-0x0000000010000000-0x000000001004B000-memory.dmp upx behavioral1/memory/1724-61-0x0000000010000000-0x000000001004B000-memory.dmp upx behavioral1/memory/1724-66-0x0000000010000000-0x000000001004B000-memory.dmp upx behavioral1/memory/1700-67-0x0000000010000000-0x000000001004B000-memory.dmp upx behavioral1/memory/1724-68-0x0000000010000000-0x000000001004B000-memory.dmp upx behavioral1/memory/1700-69-0x0000000010000000-0x000000001004B000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 896 set thread context of 1724 896 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 28 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 896 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe -
Suspicious use of WriteProcessMemory 19 IoCs
description pid Process procid_target PID 896 wrote to memory of 1724 896 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 28 PID 896 wrote to memory of 1724 896 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 28 PID 896 wrote to memory of 1724 896 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 28 PID 896 wrote to memory of 1724 896 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 28 PID 896 wrote to memory of 1724 896 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 28 PID 896 wrote to memory of 1724 896 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 28 PID 896 wrote to memory of 1724 896 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 28 PID 896 wrote to memory of 1724 896 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 28 PID 896 wrote to memory of 1724 896 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 28 PID 1724 wrote to memory of 1700 1724 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 29 PID 1724 wrote to memory of 1700 1724 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 29 PID 1724 wrote to memory of 1700 1724 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 29 PID 1724 wrote to memory of 1700 1724 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 29 PID 1724 wrote to memory of 1700 1724 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 29 PID 1724 wrote to memory of 1464 1724 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 30 PID 1724 wrote to memory of 1464 1724 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 30 PID 1724 wrote to memory of 1464 1724 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 30 PID 1724 wrote to memory of 1464 1724 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 30 PID 1724 wrote to memory of 1464 1724 56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe"C:\Users\Admin\AppData\Local\Temp\56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:896 -
C:\Users\Admin\AppData\Local\Temp\56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exeC:\Users\Admin\AppData\Local\Temp\56ebc8c312c92df9d6f73c5a2d8d9f384e9b5bff7b329e788fdc8600ede03710.exe2⤵
- Suspicious use of WriteProcessMemory
PID:1724 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:1700
-
-
C:\Program Files\Internet Explorer\iexplore.exe"C:\Program Files\Internet Explorer\iexplore.exe"3⤵PID:1464
-
-