Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
124s -
max time network
150s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
03/11/2022, 19:24
Static task
static1
Behavioral task
behavioral1
Sample
4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe
Resource
win10v2004-20220812-en
4 signatures
150 seconds
General
-
Target
4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe
-
Size
328KB
-
MD5
aaa709e0052892f2cf24305d8f884586
-
SHA1
8194c6d9bafdbc12ff51908ea79f874039324a32
-
SHA256
4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c
-
SHA512
8c923dc3a73fa9d293ddc1c6b20134323ed8c4791490863162baec0584b40dc0f0585d6975dae9a4f7d834e39d7ae0e56243682d14fddfea734b0e6a98cb9ca9
-
SSDEEP
6144:eKlzr1sYCzek2ciDaP9Xk6Ln1W8W/9InBSkZZmLdGcAdgdY6RKpjS:eGhQ2ciDq9ZL1W8q9InBRqELdolRKpj
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2636 set thread context of 4908 2636 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe 80 -
Program crash 1 IoCs
pid pid_target Process procid_target 5048 4908 WerFault.exe 80 -
Suspicious use of UnmapMainImage 1 IoCs
pid Process 4908 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe -
Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 2636 wrote to memory of 1988 2636 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe 79 PID 2636 wrote to memory of 1988 2636 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe 79 PID 2636 wrote to memory of 1988 2636 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe 79 PID 2636 wrote to memory of 4908 2636 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe 80 PID 2636 wrote to memory of 4908 2636 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe 80 PID 2636 wrote to memory of 4908 2636 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe 80 PID 2636 wrote to memory of 4908 2636 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe 80 PID 2636 wrote to memory of 4908 2636 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe 80 PID 2636 wrote to memory of 4908 2636 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe 80 PID 2636 wrote to memory of 4908 2636 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe 80 PID 2636 wrote to memory of 4908 2636 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe 80 PID 2636 wrote to memory of 4908 2636 4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe 80
Processes
-
C:\Users\Admin\AppData\Local\Temp\4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe"C:\Users\Admin\AppData\Local\Temp\4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2636 -
C:\Users\Admin\AppData\Local\Temp\4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exeC:\Users\Admin\AppData\Local\Temp\4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe2⤵PID:1988
-
-
C:\Users\Admin\AppData\Local\Temp\4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exeC:\Users\Admin\AppData\Local\Temp\4d2f55fdc6336e3035404f88c59d1bb3bf4a274e4112c48bba7e0ecf741a667c.exe2⤵
- Suspicious use of UnmapMainImage
PID:4908 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4908 -s 123⤵
- Program crash
PID:5048
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 4908 -ip 49081⤵PID:4476