Analysis
-
max time kernel
135s -
max time network
154s -
platform
windows10-2004_x64 -
resource
win10v2004-20230220-en -
resource tags
arch:x64arch:x86image:win10v2004-20230220-enlocale:en-usos:windows10-2004-x64system -
submitted
01-04-2023 20:21
Static task
static1
Behavioral task
behavioral1
Sample
60a4afd704ab562b359032152350024df1c53a12b712135a249c2dbca0d00a27.dll
Resource
win7-20230220-en
windows7-x64
5 signatures
150 seconds
General
-
Target
60a4afd704ab562b359032152350024df1c53a12b712135a249c2dbca0d00a27.dll
-
Size
1.5MB
-
MD5
1eedbd84da8a2761eca0fe9b65f7a912
-
SHA1
a7f068215d4871ef69a65b744e4529af14f40efc
-
SHA256
60a4afd704ab562b359032152350024df1c53a12b712135a249c2dbca0d00a27
-
SHA512
76e92d18d0442a37945a879c8c3c8cf6dc11def0f7bbe8cd2b5eda6082760546fcb158f76bc2aef2a4c706a304f126bcb43b8b6bb02e95eb7c254dcad9914897
-
SSDEEP
24576:KnRZ8hGqfuzVflpEncUikkGsJLQ+xQuJSGsfWhGvOxAW+FN8yoZb1MGjkmq8Gyd5:KnRZqGqcptUVkhNQMJSGsfWOO2j8Dvhp
Malware Config
Signatures
-
Detect Blackmoon payload 1 IoCs
Processes:
resource yara_rule behavioral2/memory/2744-133-0x0000000010000000-0x0000000010404000-memory.dmp family_blackmoon -
Blocklisted process makes network request 1 IoCs
Processes:
rundll32.exeflow pid process 7 2744 rundll32.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
rundll32.exepid process 2744 rundll32.exe -
Suspicious use of WriteProcessMemory 3 IoCs
Processes:
rundll32.exedescription pid process target process PID 3336 wrote to memory of 2744 3336 rundll32.exe rundll32.exe PID 3336 wrote to memory of 2744 3336 rundll32.exe rundll32.exe PID 3336 wrote to memory of 2744 3336 rundll32.exe rundll32.exe
Processes
-
C:\Windows\system32\rundll32.exerundll32.exe C:\Users\Admin\AppData\Local\Temp\60a4afd704ab562b359032152350024df1c53a12b712135a249c2dbca0d00a27.dll,#11⤵
- Suspicious use of WriteProcessMemory
-
C:\Windows\SysWOW64\rundll32.exerundll32.exe C:\Users\Admin\AppData\Local\Temp\60a4afd704ab562b359032152350024df1c53a12b712135a249c2dbca0d00a27.dll,#12⤵
- Blocklisted process makes network request
- Suspicious use of SetWindowsHookEx