Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
90s -
max time network
154s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
03/12/2022, 11:37
Static task
static1
Behavioral task
behavioral1
Sample
eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe
Resource
win10v2004-20220901-en
General
-
Target
eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe
-
Size
353KB
-
MD5
b442c685a5e64df6dbec376c36ec5080
-
SHA1
53e0c963d440d51f97f06a2176d7be750dbef36f
-
SHA256
eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8
-
SHA512
b6ed362dc4557e56ef58713c6c9f46e949b405504033df482e065ab610fdcd7815ce0c3e7c793f30e9a7fa92f27ea29c261544cf7bf8849a96f23ab7b95d89f0
-
SSDEEP
6144:ljYOzSV1/4WbjeWDPItkwrMsyC8mq8kcMc6kLIG3zbywe8PlIawe:lcOWV1Vbje9tkEfS3i6kLrl9Kawe
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/1028-135-0x0000000000400000-0x0000000000427000-memory.dmp upx behavioral2/memory/1028-139-0x0000000000400000-0x0000000000427000-memory.dmp upx behavioral2/memory/1028-140-0x0000000000400000-0x0000000000427000-memory.dmp upx behavioral2/memory/1028-147-0x0000000000400000-0x0000000000427000-memory.dmp upx -
Suspicious use of SetThreadContext 2 IoCs
description pid Process procid_target PID 3116 set thread context of 1028 3116 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 81 PID 1028 set thread context of 1780 1028 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 82 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 1780 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 1780 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 1780 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 1780 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 3116 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 1028 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe -
Suspicious use of WriteProcessMemory 19 IoCs
description pid Process procid_target PID 3116 wrote to memory of 1028 3116 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 81 PID 3116 wrote to memory of 1028 3116 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 81 PID 3116 wrote to memory of 1028 3116 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 81 PID 3116 wrote to memory of 1028 3116 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 81 PID 3116 wrote to memory of 1028 3116 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 81 PID 3116 wrote to memory of 1028 3116 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 81 PID 3116 wrote to memory of 1028 3116 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 81 PID 3116 wrote to memory of 1028 3116 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 81 PID 1028 wrote to memory of 1780 1028 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 82 PID 1028 wrote to memory of 1780 1028 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 82 PID 1028 wrote to memory of 1780 1028 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 82 PID 1028 wrote to memory of 1780 1028 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 82 PID 1028 wrote to memory of 1780 1028 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 82 PID 1028 wrote to memory of 1780 1028 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 82 PID 1028 wrote to memory of 1780 1028 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 82 PID 1780 wrote to memory of 1076 1780 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 29 PID 1780 wrote to memory of 1076 1780 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 29 PID 1780 wrote to memory of 1076 1780 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 29 PID 1780 wrote to memory of 1076 1780 eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe 29
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:1076
-
C:\Users\Admin\AppData\Local\Temp\eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe"C:\Users\Admin\AppData\Local\Temp\eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3116 -
C:\Users\Admin\AppData\Local\Temp\eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exeC:\Users\Admin\AppData\Local\Temp\eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe3⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1028 -
C:\Users\Admin\AppData\Local\Temp\eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exeC:\Users\Admin\AppData\Local\Temp\eb3dca66b68c02df461875fefe67abaf4cd479ab3c68601395950c94666626d8.exe4⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1780
-
-
-