1c8d66ef26fd9a9eff02bd5ccfbfab3d5eb7c591f39b3a895eceb1d25d3343ee

Analysis

max time kernel
37s
max time network
46s
platform
windows7_x64
resource
win7-20220812-en
resource tags

arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system
submitted
03/12/2022, 21:29

Target

1c8d66ef26fd9a9eff02bd5ccfbfab3d5eb7c591f39b3a895eceb1d25d3343ee.exe
Size

107KB
MD5

faccdb852c9f61d7cf102cf52f7f6946
SHA1

ef0ebebf69617db0b0ea0d22af8f42aacc075fd6
SHA256

1c8d66ef26fd9a9eff02bd5ccfbfab3d5eb7c591f39b3a895eceb1d25d3343ee
SHA512

756358c26ec8de99ef15ab980f6a53fbeeca19c9ca5cf292ab665e3f23baca193895500fdea3523802447f95d345732b27263471677f1d9f7743dca7c279dc0e
SSDEEP

1536:j+FDoKtniY1u7Nn2JFkC2styJjCKICFjC7EWisS+5mlatSfkZa:j+FDzK71QkbstyJjCKICpC72s/mlaXa

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
836	368	WerFault.exe	8

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 368 wrote to memory of 836	368	1c8d66ef26fd9a9eff02bd5ccfbfab3d5eb7c591f39b3a895eceb1d25d3343ee.exe	27
PID 368 wrote to memory of 836	368	1c8d66ef26fd9a9eff02bd5ccfbfab3d5eb7c591f39b3a895eceb1d25d3343ee.exe	27
PID 368 wrote to memory of 836	368	1c8d66ef26fd9a9eff02bd5ccfbfab3d5eb7c591f39b3a895eceb1d25d3343ee.exe	27
PID 368 wrote to memory of 836	368	1c8d66ef26fd9a9eff02bd5ccfbfab3d5eb7c591f39b3a895eceb1d25d3343ee.exe	27

C:\Users\Admin\AppData\Local\Temp\1c8d66ef26fd9a9eff02bd5ccfbfab3d5eb7c591f39b3a895eceb1d25d3343ee.exe
"C:\Users\Admin\AppData\Local\Temp\1c8d66ef26fd9a9eff02bd5ccfbfab3d5eb7c591f39b3a895eceb1d25d3343ee.exe"
1⤵
- Suspicious use of WriteProcessMemory
PID:368
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 368 -s 128
  2⤵
  - Program crash
  PID:836

memory/368-55-0x0000000000400000-0x0000000000429000-memory.dmp

Filesize
164KB

Download