Analysis
-
max time kernel
91s -
max time network
145s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
01/12/2022, 17:00
Static task
static1
Behavioral task
behavioral1
Sample
d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe
Resource
win7-20220901-en
windows7-x64
3 signatures
150 seconds
Behavioral task
behavioral2
Sample
d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe
Resource
win10v2004-20220901-en
windows10-2004-x64
3 signatures
150 seconds
General
-
Target
d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe
-
Size
52KB
-
MD5
bcaf98c8af296e9efaa539ca60a7b03a
-
SHA1
7a0bff743e6a012d5bba6fb9990d4214a7880ee0
-
SHA256
d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673
-
SHA512
630eef2667d3505796dfba24d1993869718bed051ba0db4b0a6febfb733307890ab9551e62e93904728721d805459f58fa3ff2efcf8a9b8109c3593f63a0bce5
-
SSDEEP
384:LjHXHvu6y+Z5WFqj1C+NMvjS2ONl4aJU6YFB+1cuw3KYf6kzdU6U6KL:nMeJ/SG2ONRU6YsIZd/KL
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2128 set thread context of 2164 2128 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 82 -
Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 2128 wrote to memory of 2164 2128 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 82 PID 2128 wrote to memory of 2164 2128 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 82 PID 2128 wrote to memory of 2164 2128 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 82 PID 2128 wrote to memory of 2164 2128 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 82 PID 2128 wrote to memory of 2164 2128 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 82 PID 2128 wrote to memory of 2164 2128 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 82 PID 2128 wrote to memory of 2164 2128 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 82 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40 PID 2164 wrote to memory of 2248 2164 d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe 40
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:2248
-
C:\Users\Admin\AppData\Local\Temp\d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe"C:\Users\Admin\AppData\Local\Temp\d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2128 -
C:\Users\Admin\AppData\Local\Temp\d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exeC:\Users\Admin\AppData\Local\Temp\d6ac15ee05f60b49378f4c42b7f3ab0e79aad2a48b235092157ece01e749c673.exe3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:2164
-
-