Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
123s -
max time network
128s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
18/09/2023, 18:35
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe
Resource
win10v2004-20230915-en
2 signatures
150 seconds
General
-
Target
811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe
-
Size
365KB
-
MD5
8a1f28548f8cbabe9b942b1d487b61aa
-
SHA1
de00308ab374c5e10f1417609b76a0d907ef360e
-
SHA256
811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5
-
SHA512
286abebbe6ce8617d7380b8eb832d86fecb94df5dfca917d175168104bc073d436ea1f8cffa844d9beba41d37e3da320226d562ad3cf89c7b96d869bcf7ee28a
-
SSDEEP
6144:vWpjEZ2jicP5iOo2T8VrSd/sUAOZUlqp9rWx06VhmU8wOBsQRsW1Sa:vWpwqiG59ou/UMWS6VhmU8wosQRsW1Sa
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3508 set thread context of 1740 3508 811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe 86 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 3508 wrote to memory of 1740 3508 811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe 86 PID 3508 wrote to memory of 1740 3508 811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe 86 PID 3508 wrote to memory of 1740 3508 811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe 86 PID 3508 wrote to memory of 1740 3508 811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe 86 PID 3508 wrote to memory of 1740 3508 811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe 86 PID 3508 wrote to memory of 1740 3508 811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe 86 PID 3508 wrote to memory of 1740 3508 811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe 86 PID 3508 wrote to memory of 1740 3508 811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe 86 PID 3508 wrote to memory of 1740 3508 811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe 86 PID 3508 wrote to memory of 1740 3508 811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe 86
Processes
-
C:\Users\Admin\AppData\Local\Temp\811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe"C:\Users\Admin\AppData\Local\Temp\811fa4d63dc3b05d628e178a80310ce4b18a6e5117a25ab943ad7dbc1e51efb5.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3508 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1740
-