Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
314s -
max time network
404s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
04/12/2022, 11:41
Static task
static1
Behavioral task
behavioral1
Sample
c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe
Resource
win10v2004-20221111-en
General
-
Target
c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe
-
Size
73KB
-
MD5
12826f85a8f5abca7b418402ae36ed9b
-
SHA1
30b878a9488fd9d9f797c41e32612461f4eab8fd
-
SHA256
c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3
-
SHA512
076c16c4419a9461e123ac5d4e1ce00586b8e573db6072fe5cc2fc09f29e237fa9f29c6f738181a98808b07d663ae431a19dea0a90d5948e97db2550ddd6a918
-
SSDEEP
1536:3CTI3+TqSsoTRcEs+YPFkgmmfAPrUgMWWOfdMNJW:yTInoF0+6Fkg9fErUg5fSNJW
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5032 set thread context of 2652 5032 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 83 -
Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 5032 wrote to memory of 2652 5032 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 83 PID 5032 wrote to memory of 2652 5032 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 83 PID 5032 wrote to memory of 2652 5032 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 83 PID 5032 wrote to memory of 2652 5032 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 83 PID 5032 wrote to memory of 2652 5032 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 83 PID 5032 wrote to memory of 2652 5032 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 83 PID 5032 wrote to memory of 2652 5032 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 83 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40 PID 2652 wrote to memory of 2480 2652 c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe 40
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:2480
-
C:\Users\Admin\AppData\Local\Temp\c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe"C:\Users\Admin\AppData\Local\Temp\c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:5032 -
C:\Users\Admin\AppData\Local\Temp\c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exeC:\Users\Admin\AppData\Local\Temp\c1e8c89e002020a176a4bb8d21364bd44c0c2fcad995d7708d9964b7fd0919a3.exe3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:2652
-
-