Analysis
- max time kernel
105s - max time network
108s - platform
windows7_x64 - resource
win7v20201028 - submitted
10/11/2020, 11:07
Static task
static1
Behavioral task
behavioral1
Sample
5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target 5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe
- Size 270KB
- Sample201110-jprrlct5va
- SHA256 5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89
- MD5 b97fb7190bf16c3d08771c0f1f43683a
- SHA1 47ce74368a7da85310e909c8b332e7fb029dc491
- SHA512 8edef6e4c347c2dfa5ed673563d7ec9e0c2496927178d67ce0b1889165ee839d1c5ef29ded36b61cca0ec4732f31fca3ca7dbc6d317583f42fb9257bedf55342
- MD5 SHA1 SHA512
Malware Config
Signatures
- Runs ping.exe 1 TTPs 1 IoCs
pid Process 1920 PING.EXE - Suspicious behavior: EnumeratesProcesses 3 IoCs
pid Process 1360 5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe 1836 5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe 1836 5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe - Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 1360 wrote to memory of 1836 1360 5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe 29 PID 1360 wrote to memory of 1836 1360 5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe 29 PID 1360 wrote to memory of 1836 1360 5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe 29 PID 1360 wrote to memory of 1836 1360 5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe 29 PID 1360 wrote to memory of 2004 1360 5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe 30 PID 1360 wrote to memory of 2004 1360 5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe 30 PID 1360 wrote to memory of 2004 1360 5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe 30 PID 1360 wrote to memory of 2004 1360 5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe 30 PID 2004 wrote to memory of 1920 2004 cmd.exe 32 PID 2004 wrote to memory of 1920 2004 cmd.exe 32 PID 2004 wrote to memory of 1920 2004 cmd.exe 32 PID 2004 wrote to memory of 1920 2004 cmd.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe"C:\Users\Admin\AppData\Local\Temp\5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1360 -
C:\Users\Admin\AppData\Local\Temp\5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exeC:\Users\Admin\AppData\Local\Temp\5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe /C2⤵
- Suspicious behavior: EnumeratesProcesses
PID:1836
-
-
C:\Windows\SysWOW64\cmd.exe"C:\Windows\System32\cmd.exe" /c ping.exe -n 6 127.0.0.1 & type "C:\Windows\System32\calc.exe" > "C:\Users\Admin\AppData\Local\Temp\5576bf0632dec198d55e299606c9b703c5c504c7f5e4a865408cdaf2d3311d89.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2004 -
C:\Windows\SysWOW64\PING.EXEping.exe -n 6 127.0.0.13⤵
- Runs ping.exe
PID:1920
-
-