Analysis
-
max time kernel
140s -
max time network
146s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
02-10-2023 09:52
Static task
static1
1 signatures
General
-
Target
f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe
-
Size
285KB
-
MD5
8af37816cac54e025bb53c9e1f03a3a1
-
SHA1
114f6da8def9e811f5bb30a67c8e426be27ebd00
-
SHA256
f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1
-
SHA512
2e16ef2577c4dcfb0ec0171ddc4a1d7e9a3a1b49cba2bab4a5fd3790507dd678bed250237ef41d83df24c0201cd0de336b2c6bc5baeb96800dee4795f26fe1f3
-
SSDEEP
6144:u+U+Elo4WGFw16HcDuFC6xURfqj6liu5f2NczoXo5FY0ox:jU+ElodKHciFC6eicv5fGczo45Fex
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2140 set thread context of 2204 2140 f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe 83 -
Program crash 1 IoCs
pid pid_target Process procid_target 2852 2140 WerFault.exe 81 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 2140 wrote to memory of 2204 2140 f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe 83 PID 2140 wrote to memory of 2204 2140 f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe 83 PID 2140 wrote to memory of 2204 2140 f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe 83 PID 2140 wrote to memory of 2204 2140 f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe 83 PID 2140 wrote to memory of 2204 2140 f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe 83 PID 2140 wrote to memory of 2204 2140 f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe 83 PID 2140 wrote to memory of 2204 2140 f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe 83 PID 2140 wrote to memory of 2204 2140 f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe 83 PID 2140 wrote to memory of 2204 2140 f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe 83 PID 2140 wrote to memory of 2204 2140 f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe"C:\Users\Admin\AppData\Local\Temp\f442cca3d641d1dd9b93d65adcc5cc44e1c20d9242f02873c97f073c918b45e1.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2140 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2204
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2140 -s 4082⤵
- Program crash
PID:2852
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 420 -p 2140 -ip 21401⤵PID:4400