Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
118s -
max time network
125s -
platform
windows7_x64 -
resource
win7-20231020-en -
resource tags
arch:x64arch:x86image:win7-20231020-enlocale:en-usos:windows7-x64system -
submitted
27/11/2023, 16:45
Static task
static1
Behavioral task
behavioral1
Sample
e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe
Resource
win7-20231020-en
Behavioral task
behavioral2
Sample
e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe
Resource
win10v2004-20231023-en
General
-
Target
e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe
-
Size
941KB
-
MD5
00e2bb2624c734506abe9d2c5bd89ade
-
SHA1
fe9ce13b890558a8c85c88cddafdc07fc943012b
-
SHA256
e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933
-
SHA512
9f750b7256fbef4e10c4566505c7482df14087550f7772bd6dafee450852d148f59815e6dcac51e7e6086c4a7f6d6d9e19a26baa43c6e5af0413402b221ff895
-
SSDEEP
24576:SFtD/619Y/FCmKv9XHzrxHoojg6RDJ23wHENt:q6b6FC31HxFcWUr
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2664 set thread context of 2480 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 29 -
Program crash 1 IoCs
pid pid_target Process procid_target 2844 2480 WerFault.exe 29 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 2480 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe -
Suspicious use of WriteProcessMemory 23 IoCs
description pid Process procid_target PID 2664 wrote to memory of 2908 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 28 PID 2664 wrote to memory of 2908 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 28 PID 2664 wrote to memory of 2908 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 28 PID 2664 wrote to memory of 2908 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 28 PID 2664 wrote to memory of 2876 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 32 PID 2664 wrote to memory of 2876 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 32 PID 2664 wrote to memory of 2876 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 32 PID 2664 wrote to memory of 2876 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 32 PID 2664 wrote to memory of 2400 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 30 PID 2664 wrote to memory of 2400 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 30 PID 2664 wrote to memory of 2400 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 30 PID 2664 wrote to memory of 2400 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 30 PID 2664 wrote to memory of 2480 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 29 PID 2664 wrote to memory of 2480 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 29 PID 2664 wrote to memory of 2480 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 29 PID 2664 wrote to memory of 2480 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 29 PID 2664 wrote to memory of 2480 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 29 PID 2664 wrote to memory of 2480 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 29 PID 2664 wrote to memory of 2480 2664 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 29 PID 2480 wrote to memory of 2844 2480 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 31 PID 2480 wrote to memory of 2844 2480 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 31 PID 2480 wrote to memory of 2844 2480 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 31 PID 2480 wrote to memory of 2844 2480 e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe"C:\Users\Admin\AppData\Local\Temp\e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:2664 -
C:\Users\Admin\AppData\Local\Temp\e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe"C:\Users\Admin\AppData\Local\Temp\e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe"2⤵PID:2908
-
-
C:\Users\Admin\AppData\Local\Temp\e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe"C:\Users\Admin\AppData\Local\Temp\e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:2480 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2480 -s 363⤵
- Program crash
PID:2844
-
-
-
C:\Users\Admin\AppData\Local\Temp\e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe"C:\Users\Admin\AppData\Local\Temp\e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe"2⤵PID:2400
-
-
C:\Users\Admin\AppData\Local\Temp\e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe"C:\Users\Admin\AppData\Local\Temp\e3446e1f5a6de1c690cc7cb5cce30547173164c67d9a4ebb6570545c69b34933.exe"2⤵PID:2876
-