Analysis
-
max time kernel
142s -
max time network
147s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
21/11/2022, 21:50
Static task
static1
Behavioral task
behavioral1
Sample
7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe
Resource
win10v2004-20221111-en
General
-
Target
7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe
-
Size
1.4MB
-
MD5
367074a9527dad534f87fd0a8ac88d62
-
SHA1
e7f78f82cfb9db5a1d3a7d076c049888b16b7f61
-
SHA256
7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753
-
SHA512
f608e52382d87799510d19f4c060a7a2057b51e8eebff0454e28adb47e912db3f7b489398de093200315d6b4d217b78f2572e952e4e3bd1eb4397d6f65da7f53
-
SSDEEP
24576:hrK6dClXmekxlm1dl4r260n4dz0as5jc3AZ1COwiUP/5lq8A+:hrBew72604doSw6ewd
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3900 set thread context of 1040 3900 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 83 -
Suspicious use of SetWindowsHookEx 5 IoCs
pid Process 1040 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 1040 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 1040 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 1040 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 1040 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 3900 wrote to memory of 1040 3900 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 83 PID 3900 wrote to memory of 1040 3900 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 83 PID 3900 wrote to memory of 1040 3900 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 83 PID 3900 wrote to memory of 1040 3900 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 83 PID 3900 wrote to memory of 1040 3900 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 83 PID 3900 wrote to memory of 1040 3900 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 83 PID 3900 wrote to memory of 1040 3900 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 83 PID 3900 wrote to memory of 1040 3900 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 83 PID 3900 wrote to memory of 1040 3900 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 83 PID 3900 wrote to memory of 1040 3900 7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe"C:\Users\Admin\AppData\Local\Temp\7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3900 -
C:\Users\Admin\AppData\Local\Temp\7aee1f8e49f05bc0992bd575dddbc90c2b70002ea116b402f782f9b51fcb7753.exe
- Suspicious use of SetWindowsHookEx
PID:1040
-