Analysis
- max time kernel
92s - max time network
114s - platform
windows10-2004_x64 - resource
win10v2004-20240221-en - resource tags
arch:x64arch:x86image:win10v2004-20240221-enlocale:en-usos:windows10-2004-x64system - submitted
25/02/2024, 10:25
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
a38b5f58e66770b8e4f0fe394584890f.exe
Resource
win7-20240221-en
7 signatures
150 seconds
Behavioral task
behavioral2
Sample
a38b5f58e66770b8e4f0fe394584890f.exe
Resource
win10v2004-20240221-en
8 signatures
150 seconds
General
- Target a38b5f58e66770b8e4f0fe394584890f.exe
- Size 109KB
- Sample240225-mf1ewahe53
- SHA256 c3e1eb83a02677a2085d64b6449be29d6ee375aa012a3a7641a29675eabd92d3
- MD5 a38b5f58e66770b8e4f0fe394584890f
- SHA1 934bd3706b78f98ec6e666d32ead74da12e77a4a
- SHA512 c27f438e118faa2a7a828414c4d79fae097b585f442599a9fdee860abda0e79803679bc930a0f3bffc6f962e09d3a2704edba9dd4a41976a3de345f15f590dd8
- SSDEEP 3072:dMY2L2FmgTOIzzuLD/v4pFKAoF4wRDEbFUHId:dMdumgTBz2v4mxyCDEpUod
- MD5 SHA1 SHA512 SSDEEP
Score
10/10
Malware Config
Signatures
- Detect XtremeRAT payload 5 IoCs
resource yara_rule behavioral2/memory/2132-9-0x0000000010000000-0x000000001004B000-memory.dmp family_xtremerat behavioral2/memory/2132-10-0x0000000010000000-0x000000001004B000-memory.dmp family_xtremerat behavioral2/memory/2408-11-0x0000000010000000-0x000000001004B000-memory.dmp family_xtremerat behavioral2/memory/2132-12-0x0000000010000000-0x000000001004B000-memory.dmp family_xtremerat behavioral2/memory/2408-13-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 behavioral2/memory/2132-4-0x0000000010000000-0x000000001004B000-memory.dmp upx behavioral2/memory/2132-7-0x0000000010000000-0x000000001004B000-memory.dmp upx behavioral2/memory/2132-9-0x0000000010000000-0x000000001004B000-memory.dmp upx behavioral2/memory/2132-10-0x0000000010000000-0x000000001004B000-memory.dmp upx behavioral2/memory/2408-11-0x0000000010000000-0x000000001004B000-memory.dmp upx behavioral2/memory/2132-12-0x0000000010000000-0x000000001004B000-memory.dmp upx behavioral2/memory/2408-13-0x0000000010000000-0x000000001004B000-memory.dmp upx - Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 408 set thread context of 2132 408 a38b5f58e66770b8e4f0fe394584890f.exe 88 - 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 4468 2408 WerFault.exe 89 4852 2408 WerFault.exe 89 - Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 408 a38b5f58e66770b8e4f0fe394584890f.exe - Suspicious use of WriteProcessMemory 15 IoCs
description pid Process procid_target PID 408 wrote to memory of 2132 408 a38b5f58e66770b8e4f0fe394584890f.exe 88 PID 408 wrote to memory of 2132 408 a38b5f58e66770b8e4f0fe394584890f.exe 88 PID 408 wrote to memory of 2132 408 a38b5f58e66770b8e4f0fe394584890f.exe 88 PID 408 wrote to memory of 2132 408 a38b5f58e66770b8e4f0fe394584890f.exe 88 PID 408 wrote to memory of 2132 408 a38b5f58e66770b8e4f0fe394584890f.exe 88 PID 408 wrote to memory of 2132 408 a38b5f58e66770b8e4f0fe394584890f.exe 88 PID 408 wrote to memory of 2132 408 a38b5f58e66770b8e4f0fe394584890f.exe 88 PID 408 wrote to memory of 2132 408 a38b5f58e66770b8e4f0fe394584890f.exe 88 PID 2132 wrote to memory of 2408 2132 a38b5f58e66770b8e4f0fe394584890f.exe 89 PID 2132 wrote to memory of 2408 2132 a38b5f58e66770b8e4f0fe394584890f.exe 89 PID 2132 wrote to memory of 2408 2132 a38b5f58e66770b8e4f0fe394584890f.exe 89 PID 2132 wrote to memory of 2408 2132 a38b5f58e66770b8e4f0fe394584890f.exe 89 PID 2132 wrote to memory of 1660 2132 a38b5f58e66770b8e4f0fe394584890f.exe 92 PID 2132 wrote to memory of 1660 2132 a38b5f58e66770b8e4f0fe394584890f.exe 92 PID 2132 wrote to memory of 1660 2132 a38b5f58e66770b8e4f0fe394584890f.exe 92
Processes
-
C:\Users\Admin\AppData\Local\Temp\a38b5f58e66770b8e4f0fe394584890f.exe"C:\Users\Admin\AppData\Local\Temp\a38b5f58e66770b8e4f0fe394584890f.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:408 -
C:\Users\Admin\AppData\Local\Temp\a38b5f58e66770b8e4f0fe394584890f.exe"C:\Users\Admin\AppData\Local\Temp\a38b5f58e66770b8e4f0fe394584890f.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2132 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:2408
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2408 -s 4844⤵
- Program crash
PID:4468
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2408 -s 4924⤵
- Program crash
PID:4852
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:1660
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 428 -p 2408 -ip 24081⤵PID:2788
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 544 -p 2408 -ip 24081⤵PID:4408