Analysis
-
max time kernel
144s -
max time network
152s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
22/11/2022, 11:01
Static task
static1
Behavioral task
behavioral1
Sample
70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe
Resource
win10v2004-20220812-en
General
-
Target
70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe
-
Size
1.3MB
-
MD5
aac987835408ce47a3d4f79fcdb62a06
-
SHA1
9e1582610ddd316f4c56cd5139110820469cdce8
-
SHA256
70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a
-
SHA512
4aaf6f7ecf43fbd478785383588ba6d15b84c635ac7afcd004526a81427db68d24b4f151053940c3939d09272d1cd371a6593891fb30b3ef5f943ea6d1c4931e
-
SSDEEP
24576:jrKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPakL:jrKo4ZwCOnYjVmJPaY
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4248 set thread context of 3472 4248 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 80 -
Suspicious use of SetWindowsHookEx 5 IoCs
pid Process 3472 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 3472 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 3472 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 3472 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 3472 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4248 wrote to memory of 3472 4248 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 80 PID 4248 wrote to memory of 3472 4248 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 80 PID 4248 wrote to memory of 3472 4248 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 80 PID 4248 wrote to memory of 3472 4248 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 80 PID 4248 wrote to memory of 3472 4248 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 80 PID 4248 wrote to memory of 3472 4248 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 80 PID 4248 wrote to memory of 3472 4248 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 80 PID 4248 wrote to memory of 3472 4248 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 80 PID 4248 wrote to memory of 3472 4248 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 80 PID 4248 wrote to memory of 3472 4248 70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe 80
Processes
-
C:\Users\Admin\AppData\Local\Temp\70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe"C:\Users\Admin\AppData\Local\Temp\70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4248 -
C:\Users\Admin\AppData\Local\Temp\70fd0ad2e1353080ef75afd1689f68473a5dd9f77db7de2a29f6e54b68aed17a.exe
- Suspicious use of SetWindowsHookEx
PID:3472
-