Analysis
- max time kernel
178s - max time network
182s - platform
windows10-2004_x64 - resource
win10v2004-20220414-en - submitted
03/05/2022, 12:57
Static task
static1
Behavioral task
behavioral1
Sample
ae6a68f651c30d7c6c914114fa14aa0b.exe
Resource
win7-20220414-en
0 signatures
0 seconds
General
- Target ae6a68f651c30d7c6c914114fa14aa0b.exe
- Size 967KB
- Sample220503-p7a1eaheaj
- SHA256 f93628943add0691bc80e1db3cee114133ef839e820f50448b3082c46113cb6d
- MD5 ae6a68f651c30d7c6c914114fa14aa0b
- SHA1 21eeaeb2061461f7bdd20f02542c18cc4ea75baa
- SHA512 e06c62be260746076290d404f90e797d340db014b250d1c78bf05fc33fd469e051d9092df59f7668673cdd7a6a7df47ab5977b241b66da3ad20528c6266ddef9
- MD5 SHA1 SHA512
Malware Config
Extracted
Family
-
danabot
Attributes
-
type
loader
Signatures
- Blocklisted process makes network request 6 IoCs
flow pid Process 12 4012 rundll32.exe 17 4012 rundll32.exe 20 4012 rundll32.exe 25 4012 rundll32.exe 28 4012 rundll32.exe 31 4012 rundll32.exe - Program crash 1 IoCs
pid pid_target Process procid_target 4588 2564 WerFault.exe 79 - Suspicious use of WriteProcessMemory 19 IoCs
description pid Process procid_target PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82 PID 2564 wrote to memory of 4012 2564 ae6a68f651c30d7c6c914114fa14aa0b.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\ae6a68f651c30d7c6c914114fa14aa0b.exe"C:\Users\Admin\AppData\Local\Temp\ae6a68f651c30d7c6c914114fa14aa0b.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2564 -
C:\Windows\SysWOW64\rundll32.exe"C:\Windows\syswow64\rundll32.exe" "C:\Windows\syswow64\shell32.dll",#612⤵
- Blocklisted process makes network request
PID:4012
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2564 -s 4202⤵
- Program crash
PID:4588
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 428 -p 2564 -ip 25641⤵PID:2872