Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
94s -
max time network
118s -
platform
windows10-2004_x64 -
resource
win10v2004-20240802-en -
resource tags
arch:x64arch:x86image:win10v2004-20240802-enlocale:en-usos:windows10-2004-x64system -
submitted
12/09/2024, 00:36
Static task
static1
Behavioral task
behavioral1
Sample
aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe
Resource
win7-20240903-en
General
-
Target
aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe
-
Size
252KB
-
MD5
d90f644ec3bcc8f73f4fec0f971ad29c
-
SHA1
1f34007f55c9592e29e3b808c9d79a7ca79c2f6b
-
SHA256
aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652
-
SHA512
4ad5074c4b017e0e96cdf6bc26a57977a4faab95dc871dd78ae4a0c33e168037e940e0d0417d2237140762454f428b9051fa18a253447f3194de422416c2dbf1
-
SSDEEP
6144:nA35z0DesvXftb8o4zl3uNSfVszNEVvzGB:A3x0DeIf7AQNSdKNEVw
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/2680-4-0x0000000000400000-0x0000000000427000-memory.dmp upx behavioral2/memory/2680-6-0x0000000000400000-0x0000000000427000-memory.dmp upx behavioral2/memory/2680-10-0x0000000000400000-0x0000000000427000-memory.dmp upx behavioral2/memory/2680-20-0x0000000000400000-0x0000000000427000-memory.dmp upx -
Suspicious use of SetThreadContext 2 IoCs
description pid Process procid_target PID 2064 set thread context of 2680 2064 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 83 PID 2680 set thread context of 4232 2680 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 84 -
System Location Discovery: System Language Discovery 1 TTPs 2 IoCs
Attempt gather information about the system language of a victim in order to infer the geographical location of that host.
description ioc Process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 4232 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 4232 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 4232 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 4232 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 2064 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 2680 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe -
Suspicious use of WriteProcessMemory 19 IoCs
description pid Process procid_target PID 2064 wrote to memory of 2680 2064 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 83 PID 2064 wrote to memory of 2680 2064 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 83 PID 2064 wrote to memory of 2680 2064 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 83 PID 2064 wrote to memory of 2680 2064 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 83 PID 2064 wrote to memory of 2680 2064 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 83 PID 2064 wrote to memory of 2680 2064 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 83 PID 2064 wrote to memory of 2680 2064 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 83 PID 2064 wrote to memory of 2680 2064 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 83 PID 2680 wrote to memory of 4232 2680 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 84 PID 2680 wrote to memory of 4232 2680 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 84 PID 2680 wrote to memory of 4232 2680 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 84 PID 2680 wrote to memory of 4232 2680 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 84 PID 2680 wrote to memory of 4232 2680 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 84 PID 2680 wrote to memory of 4232 2680 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 84 PID 2680 wrote to memory of 4232 2680 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 84 PID 4232 wrote to memory of 3408 4232 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 56 PID 4232 wrote to memory of 3408 4232 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 56 PID 4232 wrote to memory of 3408 4232 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 56 PID 4232 wrote to memory of 3408 4232 aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe 56
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:3408
-
C:\Users\Admin\AppData\Local\Temp\aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe"C:\Users\Admin\AppData\Local\Temp\aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe"2⤵
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2064 -
C:\Users\Admin\AppData\Local\Temp\aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exeC:\Users\Admin\AppData\Local\Temp\aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe3⤵
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2680 -
C:\Users\Admin\AppData\Local\Temp\aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exeC:\Users\Admin\AppData\Local\Temp\aa54bb574c6885af13bf66f3f2be69333e79db5c687136848da2b2800e3c3652.exe4⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:4232
-
-
-