Analysis
-
max time kernel
90s -
max time network
156s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
24-05-2022 18:01
Static task
static1
Behavioral task
behavioral1
Sample
0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe
Resource
win7-20220414-en
windows7_x64
0 signatures
0 seconds
Behavioral task
behavioral2
Sample
0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe
Resource
win10v2004-20220414-en
windows10-2004_x64
0 signatures
0 seconds
General
-
Target
0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe
-
Size
237KB
-
MD5
63bb49f37aa25a2c83b1fd2040ca162e
-
SHA1
e5f7b42635fedb27f5627989a621d8ca486c35fa
-
SHA256
0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75
-
SHA512
7811e1fe99bb835490193c5848468f03725821a29cde561356876ffdee3a10d338d59bc410c3e7fcb053eceb1ee1606feeae18a13c6a2d534e27ad8a2dcc3e5d
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exedescription pid process target process PID 1452 set thread context of 4128 1452 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe -
Modifies registry class 3 IoCs
Processes:
0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exedescription ioc process Key created \REGISTRY\MACHINE\SOFTWARE\Classes\.key 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\Classes\.key\ 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\Classes\.key\ = "regfile" 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
Processes:
0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exepid process 4128 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe 4128 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe 4128 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe 4128 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exepid process 1452 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe -
Suspicious use of WriteProcessMemory 11 IoCs
Processes:
0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exedescription pid process target process PID 1452 wrote to memory of 4128 1452 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe PID 1452 wrote to memory of 4128 1452 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe PID 1452 wrote to memory of 4128 1452 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe PID 1452 wrote to memory of 4128 1452 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe PID 1452 wrote to memory of 4128 1452 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe PID 1452 wrote to memory of 4128 1452 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe PID 1452 wrote to memory of 4128 1452 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe PID 4128 wrote to memory of 2156 4128 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe Explorer.EXE PID 4128 wrote to memory of 2156 4128 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe Explorer.EXE PID 4128 wrote to memory of 2156 4128 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe Explorer.EXE PID 4128 wrote to memory of 2156 4128 0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe Explorer.EXE
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:2156
-
C:\Users\Admin\AppData\Local\Temp\0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe"C:\Users\Admin\AppData\Local\Temp\0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe"2⤵
- Suspicious use of SetThreadContext
- Modifies registry class
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1452 -
C:\Users\Admin\AppData\Local\Temp\0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exeC:\Users\Admin\AppData\Local\Temp\0eca2a787e561acf25d5532971c735c04d95c99fd7db612864b7eb35bc916b75.exe3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:4128
-
-