2f3d617a1d8b16ff870171d168938f5076ef72d24c5bed6a4280dc10bcfa8273

Analysis

max time kernel
42s
max time network
47s
platform
windows7_x64
resource
win7-20220812-en
resource tags

arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system
submitted
20-10-2022 01:42

Target

2f3d617a1d8b16ff870171d168938f5076ef72d24c5bed6a4280dc10bcfa8273.exe
Size

240KB
MD5

775ffe490fc88929a4ca56e51fa23f80
SHA1

8c2cc63452864882f23832e31ba6099aaac7dc19
SHA256

2f3d617a1d8b16ff870171d168938f5076ef72d24c5bed6a4280dc10bcfa8273
SHA512

4232874bd59e69de10c94c700a3531ca4a97f29997ed30ade4370b66c5ef89b2452a4a96668d84291409300914e2a46cb63bcf9e644066054f32094b09f868e8
SSDEEP

1536:G1olr2Or2CR1RpvR1RURmJSiEUE8M7uA4w6RARZR5RARPRmRm2e7ve7ze7ve7ZeI:N2G2KrZR6

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
2016	1032	WerFault.exe	9

Suspicious use of SetWindowsHookEx 1 IoCs

pid	Process
1032	2f3d617a1d8b16ff870171d168938f5076ef72d24c5bed6a4280dc10bcfa8273.exe

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 1032 wrote to memory of 2016	1032	2f3d617a1d8b16ff870171d168938f5076ef72d24c5bed6a4280dc10bcfa8273.exe	28
PID 1032 wrote to memory of 2016	1032	2f3d617a1d8b16ff870171d168938f5076ef72d24c5bed6a4280dc10bcfa8273.exe	28
PID 1032 wrote to memory of 2016	1032	2f3d617a1d8b16ff870171d168938f5076ef72d24c5bed6a4280dc10bcfa8273.exe	28
PID 1032 wrote to memory of 2016	1032	2f3d617a1d8b16ff870171d168938f5076ef72d24c5bed6a4280dc10bcfa8273.exe	28

C:\Users\Admin\AppData\Local\Temp\2f3d617a1d8b16ff870171d168938f5076ef72d24c5bed6a4280dc10bcfa8273.exe
"C:\Users\Admin\AppData\Local\Temp\2f3d617a1d8b16ff870171d168938f5076ef72d24c5bed6a4280dc10bcfa8273.exe"
1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1032
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 1032 -s 232
  2⤵
  - Program crash
  PID:2016