Analysis
-
max time kernel
86s -
max time network
142s -
platform
windows10-1703_x64 -
resource
win10-20220812-en -
resource tags
arch:x64arch:x86image:win10-20220812-enlocale:en-usos:windows10-1703-x64system -
submitted
08/10/2022, 11:50
Static task
static1
General
-
Target
5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe
-
Size
1.3MB
-
MD5
c52a84100b9087a2f012b0c4518b34f5
-
SHA1
ee2d7f28779e2b0e66678b1566d02d8c2f8afc82
-
SHA256
5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551
-
SHA512
648d5c210340f3a3aae357d52eb8325878f5fe22e6a04fb48ba9f514d4a9ff914e8b683eda17ff9f009ff79aeafc5b4d780286875fa967e2ba40a0643d960bcc
-
SSDEEP
24576:LkNdZZ2WeYXLILyHqnKXjhnQL4l/T5uHfYddHbLqQjDsH:LsjrdVM4hVu/Yd9
Malware Config
Extracted
Family
danabot
C2
192.236.233.188:443
192.119.70.159:443
23.106.124.171:443
213.227.155.103:443
Attributes
-
embedded_hash
56951C922035D696BFCE443750496462
-
type
loader
Signatures
-
Program crash 2 IoCs
pid pid_target Process procid_target 996 3048 WerFault.exe 65 2900 3048 WerFault.exe 65 -
Suspicious use of WriteProcessMemory 17 IoCs
description pid Process procid_target PID 3048 wrote to memory of 1940 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 66 PID 3048 wrote to memory of 1940 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 66 PID 3048 wrote to memory of 1940 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 66 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68 PID 3048 wrote to memory of 2432 3048 5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe 68
Processes
-
C:\Users\Admin\AppData\Local\Temp\5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe"C:\Users\Admin\AppData\Local\Temp\5bf179d7a0b5939cecd4cd9bd387d75b69f2691be0d251cbea9fbdff3580c551.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:3048 -
C:\Windows\SysWOW64\appidtel.exeC:\Windows\system32\appidtel.exe2⤵PID:1940
-
-
C:\Windows\syswow64\rundll32.exe"C:\Windows\syswow64\rundll32.exe" "C:\Windows\syswow64\shell32.dll",#612⤵PID:2432
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3048 -s 6162⤵
- Program crash
PID:996
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3048 -s 5922⤵
- Program crash
PID:2900
-