Analysis
-
max time kernel
205s -
max time network
172s -
platform
windows10-1703_x64 -
resource
win10-20220812-en -
resource tags
arch:x64arch:x86image:win10-20220812-enlocale:en-usos:windows10-1703-x64system -
submitted
12-10-2022 05:29
Static task
static1
Behavioral task
behavioral1
Sample
6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe
Resource
win7-20220812-en
windows7-x64
3 signatures
300 seconds
General
-
Target
6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe
-
Size
1.2MB
-
MD5
e70c8bbbd8faa7cb8fb555f6bbe98a12
-
SHA1
c6c1d1fa31fe1d2906ef7837c1151a1d13a80679
-
SHA256
6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960
-
SHA512
3029d003a4d59dff4549959a030407f47136cfd8b85c985bd55aa800590579e95183d50de740c09cacc7fe2e9113d162c3b1296d7b2dff679c4a77ab7aded0ef
-
SSDEEP
24576:xImPENtb1LF4cCysOYImXOO9u8TFYFfZd4rj9YlmAxOZppvOGTJ/u:xLsfAIo40S9ZeRkmAxOHpvOG1G
Malware Config
Extracted
Family
danabot
C2
198.15.112.179:443
185.62.56.245:443
153.92.223.225:443
192.119.70.159:443
Attributes
-
embedded_hash
6618C163D57D6441FCCA65D86C4D380D
-
type
loader
Signatures
-
Program crash 3 IoCs
pid pid_target Process procid_target 3420 2748 WerFault.exe 65 1812 2748 WerFault.exe 65 4288 2748 WerFault.exe 65 -
Suspicious use of WriteProcessMemory 31 IoCs
description pid Process procid_target PID 2748 wrote to memory of 4092 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 66 PID 2748 wrote to memory of 4092 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 66 PID 2748 wrote to memory of 4092 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 66 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69 PID 2748 wrote to memory of 5088 2748 6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe 69
Processes
-
C:\Users\Admin\AppData\Local\Temp\6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe"C:\Users\Admin\AppData\Local\Temp\6563565af9b7b4e106e8687f64a80922b10dc33e3f4020b07b8b640575d35960.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2748 -
C:\Windows\SysWOW64\appidtel.exeC:\Windows\system32\appidtel.exe2⤵PID:4092
-
-
C:\Windows\syswow64\rundll32.exe"C:\Windows\syswow64\rundll32.exe" "C:\Windows\syswow64\shell32.dll",#612⤵PID:5088
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2748 -s 6082⤵
- Program crash
PID:3420
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2748 -s 6322⤵
- Program crash
PID:1812
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2748 -s 6402⤵
- Program crash
PID:4288
-