Analysis
-
max time kernel
41s -
max time network
45s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
07-11-2022 07:52
Static task
static1
Behavioral task
behavioral1
Sample
ad1afdf2af7de0373f64544885bf2e4d35659241554920626141a92aa44b82df.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
ad1afdf2af7de0373f64544885bf2e4d35659241554920626141a92aa44b82df.exe
Resource
win10v2004-20220812-en
General
-
Target
ad1afdf2af7de0373f64544885bf2e4d35659241554920626141a92aa44b82df.exe
-
Size
320KB
-
MD5
04be9e2f3584bee51ad7f6f004a83240
-
SHA1
8b1363a9fc46b148a3d5e87ea02f53ff9ea16dd4
-
SHA256
ad1afdf2af7de0373f64544885bf2e4d35659241554920626141a92aa44b82df
-
SHA512
1b4fbd0e34526762e44ddc52f120045f143ca286b990c11d1f9f20199a348e5ce232518203f0e9345ec0af2eabb1c6a387c1efe5818192e4f31cc468dc0379e3
-
SSDEEP
6144:rXi3VGH2RfS155ONNXBuWoJBO9OMbHLkAqF7Ief9UmM7/uT:0C2EB0NxDIBuOFe7/uT
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 540 368 WerFault.exe 25 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 368 wrote to memory of 540 368 ad1afdf2af7de0373f64544885bf2e4d35659241554920626141a92aa44b82df.exe 26 PID 368 wrote to memory of 540 368 ad1afdf2af7de0373f64544885bf2e4d35659241554920626141a92aa44b82df.exe 26 PID 368 wrote to memory of 540 368 ad1afdf2af7de0373f64544885bf2e4d35659241554920626141a92aa44b82df.exe 26 PID 368 wrote to memory of 540 368 ad1afdf2af7de0373f64544885bf2e4d35659241554920626141a92aa44b82df.exe 26
Processes
-
C:\Users\Admin\AppData\Local\Temp\ad1afdf2af7de0373f64544885bf2e4d35659241554920626141a92aa44b82df.exe"C:\Users\Admin\AppData\Local\Temp\ad1afdf2af7de0373f64544885bf2e4d35659241554920626141a92aa44b82df.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:368 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 368 -s 362⤵
- Program crash
PID:540
-