Analysis
- max time kernel
14s - max time network
8s - platform
windows7_x64 - resource
win7v20201028 - submitted
15/11/2020, 22:48
Static task
static1
Behavioral task
behavioral1
Sample
e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe
- Size 1.4MB
- Sample201115-qattpg7j86
- SHA256 e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72
- MD5 d0dcb5838088c28bd9259b023e7db1b4
- SHA1 d3fd84d08cf05ddbf50c431a3ee0b923df4a78d7
- SHA512 adab372d75e0a1aec346ab57315f7a24f55304205671e1c81f75d1fd5682b164b33e191a46e220bd8f105326d1fbb2efeca53de1ca50d47b55fb297dc171dc44
- MD5 SHA1 SHA512
Malware Config
Signatures
- Runs ping.exe 1 TTPs 1 IoCs
pid Process 684 PING.EXE - Suspicious behavior: EnumeratesProcesses 3 IoCs
pid Process 1900 e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe 1680 e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe 1680 e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe - Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 1900 wrote to memory of 1680 1900 e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe 29 PID 1900 wrote to memory of 1680 1900 e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe 29 PID 1900 wrote to memory of 1680 1900 e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe 29 PID 1900 wrote to memory of 1680 1900 e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe 29 PID 1900 wrote to memory of 756 1900 e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe 30 PID 1900 wrote to memory of 756 1900 e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe 30 PID 1900 wrote to memory of 756 1900 e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe 30 PID 1900 wrote to memory of 756 1900 e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe 30 PID 756 wrote to memory of 684 756 cmd.exe 32 PID 756 wrote to memory of 684 756 cmd.exe 32 PID 756 wrote to memory of 684 756 cmd.exe 32 PID 756 wrote to memory of 684 756 cmd.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe"C:\Users\Admin\AppData\Local\Temp\e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1900 -
C:\Users\Admin\AppData\Local\Temp\e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exeC:\Users\Admin\AppData\Local\Temp\e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe /C2⤵
- Suspicious behavior: EnumeratesProcesses
PID:1680
-
-
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\e1f2e8d57f930215eecdb592d48ca24a5469e20761491764b71e67a3d1809e72.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:756 -
C:\Windows\SysWOW64\PING.EXEping.exe -n 6 127.0.0.13⤵
- Runs ping.exe
PID:684
-
-