Analysis
-
max time kernel
145s -
max time network
153s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
24-11-2022 18:57
Static task
static1
Behavioral task
behavioral1
Sample
cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe
Resource
win10v2004-20220812-en
General
-
Target
cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe
-
Size
980KB
-
MD5
409a8d80d84aa23fedb10b49160051d9
-
SHA1
4aa47235e60cfc78040360e9840c2f9a55f0d67a
-
SHA256
cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359
-
SHA512
2ebcba46759db8efff11490d2771057e9119ca6273fbc38f5a53b13916639d01532672620d9d27f2d9e5f221c48c2b45869fb8362a93d849eef7b18404dcab3a
-
SSDEEP
24576:YTLHLXccWMukmi4AQ7CsVbqQr/kV8u69fUg:QLMBRuQus/4V8uib
Malware Config
Signatures
-
Detect XtremeRAT payload 5 IoCs
Processes:
resource yara_rule behavioral2/memory/3748-137-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/3748-138-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/3748-139-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/3748-145-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/3748-147-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat -
XtremeRAT
The XtremeRAT was developed by xtremecoder and has been available since at least 2010, and written in Delphi.
-
Identifies VirtualBox via ACPI registry values (likely anti-VM) 2 TTPs 1 IoCs
Processes:
cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exedescription ioc process Key opened \REGISTRY\MACHINE\HARDWARE\ACPI\DSDT\VBOX__ cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe -
Identifies Wine through registry keys 2 TTPs 1 IoCs
Wine is a compatibility layer capable of running Windows applications, which can be used as sandboxing environment.
Processes:
cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exedescription ioc process Key opened \REGISTRY\USER\S-1-5-21-2629973501-4017243118-3254762364-1000\Software\Wine cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe -
Suspicious use of NtSetInformationThreadHideFromDebugger 1 IoCs
Processes:
cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exepid process 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exedescription pid process target process PID 5076 set thread context of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Runs net.exe
-
Suspicious behavior: EnumeratesProcesses 10 IoCs
Processes:
cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exepid process 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
Processes:
cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exepid process 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe -
Suspicious use of WriteProcessMemory 25 IoCs
Processes:
cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.execmd.exenet.execfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exedescription pid process target process PID 5076 wrote to memory of 3640 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cmd.exe PID 5076 wrote to memory of 3640 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cmd.exe PID 5076 wrote to memory of 3640 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cmd.exe PID 5076 wrote to memory of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe PID 5076 wrote to memory of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe PID 5076 wrote to memory of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe PID 5076 wrote to memory of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe PID 5076 wrote to memory of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe PID 5076 wrote to memory of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe PID 5076 wrote to memory of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe PID 5076 wrote to memory of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe PID 5076 wrote to memory of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe PID 5076 wrote to memory of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe PID 5076 wrote to memory of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe PID 5076 wrote to memory of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe PID 5076 wrote to memory of 3748 5076 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe PID 3640 wrote to memory of 2752 3640 cmd.exe net.exe PID 3640 wrote to memory of 2752 3640 cmd.exe net.exe PID 3640 wrote to memory of 2752 3640 cmd.exe net.exe PID 2752 wrote to memory of 2296 2752 net.exe net1.exe PID 2752 wrote to memory of 2296 2752 net.exe net1.exe PID 2752 wrote to memory of 2296 2752 net.exe net1.exe PID 3748 wrote to memory of 2488 3748 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe msedge.exe PID 3748 wrote to memory of 2488 3748 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe msedge.exe PID 3748 wrote to memory of 2488 3748 cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe msedge.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe"C:\Users\Admin\AppData\Local\Temp\cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe"1⤵
- Identifies VirtualBox via ACPI registry values (likely anti-VM)
- Identifies Wine through registry keys
- Suspicious use of NtSetInformationThreadHideFromDebugger
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:5076 -
C:\Windows\SysWOW64\cmd.exe/c net stop MpsSvc2⤵
- Suspicious use of WriteProcessMemory
PID:3640 -
C:\Windows\SysWOW64\net.exenet stop MpsSvc3⤵
- Suspicious use of WriteProcessMemory
PID:2752 -
C:\Windows\SysWOW64\net1.exeC:\Windows\system32\net1 stop MpsSvc4⤵PID:2296
-
C:\Users\Admin\AppData\Local\Temp\cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exeC:\Users\Admin\AppData\Local\Temp\cfc440d88a6d4f34035e9a9b2cbe63e5628f01f0e893370cd66cdd9c9725e359.exe2⤵
- Suspicious use of WriteProcessMemory
PID:3748 -
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:2488