Analysis
-
max time kernel
144s -
max time network
149s -
platform
windows10-2004_x64 -
resource
win10v2004-20231222-en -
resource tags
arch:x64arch:x86image:win10v2004-20231222-enlocale:en-usos:windows10-2004-x64system -
submitted
25-01-2024 23:56
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
75d7f4e89d40c202c6a28dfe30d6cc93.exe
Resource
win7-20231215-en
windows7-x64
4 signatures
150 seconds
General
-
Target
75d7f4e89d40c202c6a28dfe30d6cc93.exe
-
Size
1.2MB
-
MD5
75d7f4e89d40c202c6a28dfe30d6cc93
-
SHA1
fe394c2f0abea15f8b6c19fc4e0ac4ebe8c63c6b
-
SHA256
b2dc44fd64beab5b53beb3fbd60e7ddd803337774dac60fcba0d71deb0a138e7
-
SHA512
568dfe60bd6a8443185906fd7e22924ca23d9a2fd4ced2b34c450dfbcd7ca8989017127ba813ff5633c47450c200b2119fa7a4554f9385745cc22a51835e8231
-
SSDEEP
24576:e9wrQhw7iGRv/roB8hd7mWS/16fSYKxQ:0WiALoSnS4tsQ
Malware Config
Extracted
Family
darkcomet
Botnet
x
C2
cppgamer.no-ip.biz:1024
cppgamer.no-ip.biz:1243
Mutex
DC_MUTEX-EN4NFY6
Attributes
-
InstallPath
MSDCSC\msdcsc.exe
-
gencode
0wdCxW5TpJNK
-
install
true
-
offline_keylogger
true
-
persistence
false
-
reg_key
MicroUpdate
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
75d7f4e89d40c202c6a28dfe30d6cc93.exedescription pid process target process PID 5964 set thread context of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 4432 5224 WerFault.exe explorer.exe -
Suspicious use of WriteProcessMemory 14 IoCs
Processes:
75d7f4e89d40c202c6a28dfe30d6cc93.exedescription pid process target process PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe PID 5964 wrote to memory of 5224 5964 75d7f4e89d40c202c6a28dfe30d6cc93.exe explorer.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\75d7f4e89d40c202c6a28dfe30d6cc93.exe"C:\Users\Admin\AppData\Local\Temp\75d7f4e89d40c202c6a28dfe30d6cc93.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:5964 -
C:\Windows\SysWOW64\explorer.exeC:\Windows\system32\explorer.exe2⤵PID:5224
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 5224 -s 7403⤵
- Program crash
PID:4432
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 184 -p 5224 -ip 52241⤵PID:4036