Analysis
-
max time kernel
146s -
max time network
161s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
29/11/2022, 06:54
Static task
static1
Behavioral task
behavioral1
Sample
820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe
Resource
win10v2004-20221111-en
General
-
Target
820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe
-
Size
564KB
-
MD5
751b1a5234a26db43173c890ea47d51f
-
SHA1
00db6bad347f29da049ba85002558332cb34efc5
-
SHA256
820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88
-
SHA512
162f7d8b1e01dfb225dbf20016e8d28d3ea92721d4548dd4bebbb21517a3f5fbcd53582fb948d31102e04e8d9f328c153ab008b273f9a41096da00aef90d7b95
-
SSDEEP
12288:mJzAZdFoT487jvoflYBK/lGRgOUqmq9kR6lhKXH6GDOlXq551P:mu/FoT5XFK/cRgOnmq9g6dlXU5
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5080 set thread context of 3140 5080 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 85 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 3140 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 3140 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 3140 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 3140 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 5080 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 5080 wrote to memory of 3140 5080 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 85 PID 5080 wrote to memory of 3140 5080 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 85 PID 5080 wrote to memory of 3140 5080 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 85 PID 5080 wrote to memory of 3140 5080 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 85 PID 5080 wrote to memory of 3140 5080 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 85 PID 5080 wrote to memory of 3140 5080 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 85 PID 5080 wrote to memory of 3140 5080 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 85 PID 3140 wrote to memory of 2596 3140 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 41 PID 3140 wrote to memory of 2596 3140 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 41 PID 3140 wrote to memory of 2596 3140 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 41 PID 3140 wrote to memory of 2596 3140 820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe 41
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:2596
-
C:\Users\Admin\AppData\Local\Temp\820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe"C:\Users\Admin\AppData\Local\Temp\820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:5080 -
C:\Users\Admin\AppData\Local\Temp\820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exeC:\Users\Admin\AppData\Local\Temp\820b4768adb173b54da62028ea2eb5d6abb4b4ab33e239f0da7f409c540dcd88.exe3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:3140
-
-