Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
149s -
max time network
150s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
25/03/2024, 16:23
Behavioral task
behavioral1
Sample
de6f73f31c25f6b93bc3d8bd47ff9514.exe
Resource
win7-20240221-en
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
de6f73f31c25f6b93bc3d8bd47ff9514.exe
Resource
win10v2004-20240226-en
5 signatures
150 seconds
General
-
Target
de6f73f31c25f6b93bc3d8bd47ff9514.exe
-
Size
312KB
-
MD5
de6f73f31c25f6b93bc3d8bd47ff9514
-
SHA1
bac993096b25db586425ab8ccdae9acd823b7fd6
-
SHA256
7598f007cd7be2347e701a0b100babbe95a59d326d94f522a1e7b641ac6b73eb
-
SHA512
890188f5df449e619c3cde6b952e8cf8d1ad2d538a74e886229d834a01f8d6c88eae9368268e85b709f2613f0e699d2bef1de24b85c3ef283154e9e94a465d19
-
SSDEEP
6144:D6as/nSSs09AkSrz25BWsgRSIKXG73wAHyQzHnxQNqBvs5tKXnm:D9oAPrC5BgRGo3H3HxMtKXm
Score
7/10
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/3512-0-0x0000000000400000-0x00000000004A6000-memory.dmp upx behavioral2/memory/3512-7-0x0000000000400000-0x00000000004A6000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3512 set thread context of 4516 3512 de6f73f31c25f6b93bc3d8bd47ff9514.exe 91 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 4516 de6f73f31c25f6b93bc3d8bd47ff9514.exe 4516 de6f73f31c25f6b93bc3d8bd47ff9514.exe 4516 de6f73f31c25f6b93bc3d8bd47ff9514.exe 4516 de6f73f31c25f6b93bc3d8bd47ff9514.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 3512 de6f73f31c25f6b93bc3d8bd47ff9514.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 3512 wrote to memory of 4516 3512 de6f73f31c25f6b93bc3d8bd47ff9514.exe 91 PID 3512 wrote to memory of 4516 3512 de6f73f31c25f6b93bc3d8bd47ff9514.exe 91 PID 3512 wrote to memory of 4516 3512 de6f73f31c25f6b93bc3d8bd47ff9514.exe 91 PID 3512 wrote to memory of 4516 3512 de6f73f31c25f6b93bc3d8bd47ff9514.exe 91 PID 3512 wrote to memory of 4516 3512 de6f73f31c25f6b93bc3d8bd47ff9514.exe 91 PID 3512 wrote to memory of 4516 3512 de6f73f31c25f6b93bc3d8bd47ff9514.exe 91 PID 3512 wrote to memory of 4516 3512 de6f73f31c25f6b93bc3d8bd47ff9514.exe 91 PID 4516 wrote to memory of 3416 4516 de6f73f31c25f6b93bc3d8bd47ff9514.exe 57 PID 4516 wrote to memory of 3416 4516 de6f73f31c25f6b93bc3d8bd47ff9514.exe 57 PID 4516 wrote to memory of 3416 4516 de6f73f31c25f6b93bc3d8bd47ff9514.exe 57 PID 4516 wrote to memory of 3416 4516 de6f73f31c25f6b93bc3d8bd47ff9514.exe 57
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:3416
-
C:\Users\Admin\AppData\Local\Temp\de6f73f31c25f6b93bc3d8bd47ff9514.exe"C:\Users\Admin\AppData\Local\Temp\de6f73f31c25f6b93bc3d8bd47ff9514.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3512 -
C:\Users\Admin\AppData\Local\Temp\de6f73f31c25f6b93bc3d8bd47ff9514.exeC:\Users\Admin\AppData\Local\Temp\de6f73f31c25f6b93bc3d8bd47ff9514.exe3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:4516
-
-