Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
143s -
max time network
148s -
platform
windows10-2004_x64 -
resource
win10v2004-20231127-en -
resource tags
arch:x64arch:x86image:win10v2004-20231127-enlocale:en-usos:windows10-2004-x64system -
submitted
04/12/2023, 04:04
Behavioral task
behavioral1
Sample
249fa2a560a2a8e1ae5a6b114e31afb2.exe
Resource
win7-20231023-en
6 signatures
150 seconds
Behavioral task
behavioral2
Sample
249fa2a560a2a8e1ae5a6b114e31afb2.exe
Resource
win10v2004-20231127-en
6 signatures
150 seconds
General
-
Target
249fa2a560a2a8e1ae5a6b114e31afb2.exe
-
Size
3.0MB
-
MD5
249fa2a560a2a8e1ae5a6b114e31afb2
-
SHA1
3d1cecb12c80bbb4c3d69d25f8295c867a40828f
-
SHA256
13e2517eb9d45a3d68feec9d8cec5e8aeeed4b57d63db428f68c54be4224390e
-
SHA512
0c1f25f518e7026bcc0ba1ea55ab498e85e68ac6ce27cc12c554e75718f2d8956eb7b7407898d9cc8fbf4bd6335c63d97876c267ac3a54268930738c0b9f824b
-
SSDEEP
98304:RjB+06fkx9KWqBDeRTsnBF75riKIJWsHGR:RjB+Rfe7RTsBF75OKjs+
Score
10/10
Malware Config
Signatures
-
Detect PureLogs payload 1 IoCs
resource yara_rule behavioral2/memory/4900-0-0x0000000000310000-0x000000000061E000-memory.dmp family_purelogs -
Adds Run key to start application 2 TTPs 1 IoCs
description ioc Process Set value (str) \REGISTRY\USER\S-1-5-21-2037190880-819243489-950462038-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\Cphekmz = "C:\\Users\\Admin\\AppData\\Roaming\\Cphekmz.exe" 249fa2a560a2a8e1ae5a6b114e31afb2.exe -
Suspicious behavior: EnumeratesProcesses 21 IoCs
pid Process 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe -
Suspicious use of WriteProcessMemory 40 IoCs
description pid Process procid_target PID 4900 wrote to memory of 4124 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 90 PID 4900 wrote to memory of 4124 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 90 PID 4900 wrote to memory of 4124 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 90 PID 4900 wrote to memory of 4124 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 90 PID 4900 wrote to memory of 4440 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 99 PID 4900 wrote to memory of 4440 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 99 PID 4900 wrote to memory of 4440 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 99 PID 4900 wrote to memory of 4440 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 99 PID 4900 wrote to memory of 1372 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 98 PID 4900 wrote to memory of 1372 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 98 PID 4900 wrote to memory of 1372 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 98 PID 4900 wrote to memory of 1372 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 98 PID 4900 wrote to memory of 228 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 97 PID 4900 wrote to memory of 228 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 97 PID 4900 wrote to memory of 228 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 97 PID 4900 wrote to memory of 228 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 97 PID 4900 wrote to memory of 4024 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 96 PID 4900 wrote to memory of 4024 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 96 PID 4900 wrote to memory of 4024 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 96 PID 4900 wrote to memory of 4024 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 96 PID 4900 wrote to memory of 3804 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 94 PID 4900 wrote to memory of 3804 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 94 PID 4900 wrote to memory of 3804 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 94 PID 4900 wrote to memory of 3804 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 94 PID 4900 wrote to memory of 484 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 91 PID 4900 wrote to memory of 484 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 91 PID 4900 wrote to memory of 484 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 91 PID 4900 wrote to memory of 484 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 91 PID 4900 wrote to memory of 1052 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 93 PID 4900 wrote to memory of 1052 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 93 PID 4900 wrote to memory of 1052 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 93 PID 4900 wrote to memory of 1052 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 93 PID 4900 wrote to memory of 4036 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 92 PID 4900 wrote to memory of 4036 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 92 PID 4900 wrote to memory of 4036 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 92 PID 4900 wrote to memory of 4036 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 92 PID 4900 wrote to memory of 3656 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 95 PID 4900 wrote to memory of 3656 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 95 PID 4900 wrote to memory of 3656 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 95 PID 4900 wrote to memory of 3656 4900 249fa2a560a2a8e1ae5a6b114e31afb2.exe 95
Processes
-
C:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exe"C:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exe"1⤵
- Adds Run key to start application
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:4900 -
C:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exeC:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exe2⤵PID:4124
-
-
C:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exeC:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exe2⤵PID:484
-
-
C:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exeC:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exe2⤵PID:4036
-
-
C:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exeC:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exe2⤵PID:1052
-
-
C:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exeC:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exe2⤵PID:3804
-
-
C:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exeC:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exe2⤵PID:3656
-
-
C:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exeC:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exe2⤵PID:4024
-
-
C:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exeC:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exe2⤵PID:228
-
-
C:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exeC:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exe2⤵PID:1372
-
-
C:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exeC:\Users\Admin\AppData\Local\Temp\249fa2a560a2a8e1ae5a6b114e31afb2.exe2⤵PID:4440
-