Analysis
-
max time kernel
153s -
max time network
195s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
29-11-2022 08:20
Behavioral task
behavioral1
Sample
67b5fd1754c229407f21ae084ab6cccd3100478e45ca872f68274ee19dde8ea3.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
67b5fd1754c229407f21ae084ab6cccd3100478e45ca872f68274ee19dde8ea3.exe
Resource
win10v2004-20220812-en
General
-
Target
67b5fd1754c229407f21ae084ab6cccd3100478e45ca872f68274ee19dde8ea3.exe
-
Size
736KB
-
MD5
6db25c22147139f10a73befb1050f9ed
-
SHA1
d6f06e6160a8bc4a767f6cbb7edfb6139f3f291f
-
SHA256
67b5fd1754c229407f21ae084ab6cccd3100478e45ca872f68274ee19dde8ea3
-
SHA512
04e4e3df1c2f3582508a31c5769e5098bc8b68b5adb10551a64534f800b4a5f207b056352adaa189ccf252423b34131a96497f029b4285890324a9f46f2a4137
-
SSDEEP
12288:3rLzYIubBjwFB6sGK7dXAVBj6LyRL8hhDK0pDg7K5L9Gpk3h/:3srtkFBBGqaB3YDxDgux96o/
Malware Config
Signatures
-
Processes:
resource yara_rule behavioral2/memory/2544-135-0x0000000000400000-0x0000000000600000-memory.dmp vmprotect behavioral2/memory/2544-139-0x0000000000400000-0x0000000000600000-memory.dmp vmprotect behavioral2/memory/2544-140-0x0000000000400000-0x0000000000600000-memory.dmp vmprotect -
Suspicious use of NtSetInformationThreadHideFromDebugger 1 IoCs
Processes:
67b5fd1754c229407f21ae084ab6cccd3100478e45ca872f68274ee19dde8ea3.exepid process 2544 67b5fd1754c229407f21ae084ab6cccd3100478e45ca872f68274ee19dde8ea3.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
67b5fd1754c229407f21ae084ab6cccd3100478e45ca872f68274ee19dde8ea3.exepid process 2544 67b5fd1754c229407f21ae084ab6cccd3100478e45ca872f68274ee19dde8ea3.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\67b5fd1754c229407f21ae084ab6cccd3100478e45ca872f68274ee19dde8ea3.exe"C:\Users\Admin\AppData\Local\Temp\67b5fd1754c229407f21ae084ab6cccd3100478e45ca872f68274ee19dde8ea3.exe"1⤵
- Suspicious use of NtSetInformationThreadHideFromDebugger
- Suspicious use of SetWindowsHookEx