Analysis
-
max time kernel
144s -
max time network
146s -
platform
windows10-1703_x64 -
resource
win10-20220812-en -
resource tags
arch:x64arch:x86image:win10-20220812-enlocale:en-usos:windows10-1703-x64system -
submitted
23/09/2022, 11:50
Static task
static1
General
-
Target
00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe
-
Size
1.3MB
-
MD5
60000415462fcb36858934bf2090206f
-
SHA1
0f3d6297770ee6cc65e9fd0d91d9b6fa92a5eae0
-
SHA256
00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3
-
SHA512
063a6ab23df1d723929d183ad7bb88ec70bf7ae215ebf761708e72c17db31333dbba26977a051b2cfb7f89e2e6e24c0fd408304e5b18ff1ea2d90d660261772d
-
SSDEEP
24576:5p5jHWW9yPz6IVI0RG9go6DdjnNVASgd+6y03P7eTr:5p9HWWcPnXWuJjnMS03PC
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 2 IoCs
pid pid_target Process procid_target 3548 2360 WerFault.exe 65 3628 2360 WerFault.exe 65 -
Suspicious use of WriteProcessMemory 27 IoCs
description pid Process procid_target PID 2360 wrote to memory of 3488 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 66 PID 2360 wrote to memory of 3488 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 66 PID 2360 wrote to memory of 3488 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 66 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69 PID 2360 wrote to memory of 4040 2360 00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe 69
Processes
-
C:\Users\Admin\AppData\Local\Temp\00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe"C:\Users\Admin\AppData\Local\Temp\00da54a3d1f5c38cd0ceeb76ba100df57c16da087948027170179bad9362e6e3.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2360 -
C:\Windows\SysWOW64\appidtel.exeC:\Windows\system32\appidtel.exe2⤵PID:3488
-
-
C:\Windows\syswow64\rundll32.exe"C:\Windows\syswow64\rundll32.exe" "C:\Windows\syswow64\shell32.dll",#612⤵PID:4040
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2360 -s 6042⤵
- Program crash
PID:3548
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2360 -s 6402⤵
- Program crash
PID:3628
-