c358154b48ad7e666839e5cda7f41e85c1c94db320cdbd596bb251a83c80c484

Analysis

max time kernel
90s
max time network
110s
platform
windows10-2004_x64
resource
win10v2004-20220901-en
resource tags

arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system
submitted
03-12-2022 05:39

Target

c358154b48ad7e666839e5cda7f41e85c1c94db320cdbd596bb251a83c80c484.exe
Size

784KB
MD5

146a13a4c1735062c7e144f8a6aee6f3
SHA1

9a00f7e67196c436a4d9355007055982c24a90e7
SHA256

c358154b48ad7e666839e5cda7f41e85c1c94db320cdbd596bb251a83c80c484
SHA512

b4a50c3b11af3f9f3d4944d456b11743ce96381f80d98061b850719a21d7d669261b4a9a394b91a1291053ace1b1b4446ecc5c45f048e534dfed20e8ae830710
SSDEEP

12288:GefX5bxGTsLvx/WvBLlmDLI/wA0qSniuMVGnmjKnRlgqdQ3QCNTI:GUX5dDFWLUkWqSnZMknmMIfr5I

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
5072	2368	WerFault.exe	80

Suspicious use of WriteProcessMemory 3 IoCs

description	pid	Process	procid_target
PID 2368 wrote to memory of 1772	2368	c358154b48ad7e666839e5cda7f41e85c1c94db320cdbd596bb251a83c80c484.exe	81
PID 2368 wrote to memory of 1772	2368	c358154b48ad7e666839e5cda7f41e85c1c94db320cdbd596bb251a83c80c484.exe	81
PID 2368 wrote to memory of 1772	2368	c358154b48ad7e666839e5cda7f41e85c1c94db320cdbd596bb251a83c80c484.exe	81

C:\Users\Admin\AppData\Local\Temp\c358154b48ad7e666839e5cda7f41e85c1c94db320cdbd596bb251a83c80c484.exe
"C:\Users\Admin\AppData\Local\Temp\c358154b48ad7e666839e5cda7f41e85c1c94db320cdbd596bb251a83c80c484.exe"
1⤵
- Suspicious use of WriteProcessMemory
PID:2368
- C:\Users\Admin\AppData\Local\Temp\c358154b48ad7e666839e5cda7f41e85c1c94db320cdbd596bb251a83c80c484.exe
  C:\Users\Admin\AppData\Local\Temp\c358154b48ad7e666839e5cda7f41e85c1c94db320cdbd596bb251a83c80c484.exe
  2⤵
  PID:1772
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 2368 -s 536
  2⤵
  - Program crash
  PID:5072

C:\Windows\SysWOW64\WerFault.exe
C:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 2368 -ip 2368
1⤵
PID:4192