Analysis
- max time kernel
290s - max time network
306s - platform
windows10-1703_x64 - resource
win10-20230915-en - resource tags
arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system - submitted
25/09/2023, 01:41
Static task
static1
Behavioral task
behavioral1
Sample
cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe
Resource
win7-20230831-en
4 signatures
300 seconds
Behavioral task
behavioral2
Sample
cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe
Resource
win10-20230915-en
4 signatures
300 seconds
General
- Target cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe
- Size 378KB
- Sample230925-b4b7eabc3t
- SHA256 cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0
- MD5 31d07fde0243b0c6ddc03c2763a3b4e9
- SHA1 948f06a8359aecb24660bc059bc680b9840b3743
- SHA512 3ce02a00fd7cb780960362031983cd8f7a90f33611de685cbfebc5b37f07ec032d9f9840875698481bfd01fb4abffaf96cd888c089ff52cffcf6134b3a29e258
- SSDEEP 6144:RVCRpLdOGUqzzkGp5AO8vKTeok2WZ+qzuYg9kq8o5TquqK:RoRpkJE5cl2WFzuYx/o5TquqK
- MD5 SHA1 SHA512 SSDEEP
Malware Config
Extracted
Family
-
redline
Botnet
-
LogsDiller Cloud (TG: @logsdillabot)
C2
-
51.38.95.107:42494
Attributes
-
auth_value
3a050df92d0cf082b2cdaf87863616be
Signatures
- RedLine
RedLine Stealer is a malware family written in C#, first appearing in early 2020.
- Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5072 set thread context of 5036 5072 cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe 69 - Program crash 1 IoCs
pid pid_target Process procid_target 4612 5072 WerFault.exe 68 - Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 5072 wrote to memory of 5036 5072 cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe 69 PID 5072 wrote to memory of 5036 5072 cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe 69 PID 5072 wrote to memory of 5036 5072 cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe 69 PID 5072 wrote to memory of 5036 5072 cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe 69 PID 5072 wrote to memory of 5036 5072 cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe 69 PID 5072 wrote to memory of 5036 5072 cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe 69 PID 5072 wrote to memory of 5036 5072 cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe 69 PID 5072 wrote to memory of 5036 5072 cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe 69
Processes
-
C:\Users\Admin\AppData\Local\Temp\cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe"C:\Users\Admin\AppData\Local\Temp\cbd638a1495365200c2f32f608cdbb4e07264dc13e3e3a3985eb0494d93390a0.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:5072 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:5036
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 5072 -s 2442⤵
- Program crash
PID:4612
-