Analysis
- max time kernel
15s - max time network
8s - platform
windows7_x64 - resource
win7v20201028 - submitted
12/11/2020, 14:23
Static task
static1
Behavioral task
behavioral1
Sample
ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe
- Size 270KB
- Sample201112-xayffc3vbx
- SHA256 ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38
- MD5 ba546238e387e476eee6004bccb88a9f
- SHA1 4a7cccad08cd8ad49e89b7fea14bc72d69e53480
- SHA512 a220b9966e63e4dcf97c3b6d12491c96bada0d48a29f96fedc076f73d3a3cb2369c41a8e1be029383b2afa4f98c0860c0158cede68494e4bec26e2066426d9b7
- MD5 SHA1 SHA512
Malware Config
Signatures
- Runs ping.exe 1 TTPs 1 IoCs
pid Process 1416 PING.EXE - Suspicious behavior: EnumeratesProcesses 3 IoCs
pid Process 1668 ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe 2024 ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe 2024 ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe - Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 1668 wrote to memory of 2024 1668 ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe 29 PID 1668 wrote to memory of 2024 1668 ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe 29 PID 1668 wrote to memory of 2024 1668 ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe 29 PID 1668 wrote to memory of 2024 1668 ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe 29 PID 1668 wrote to memory of 1320 1668 ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe 30 PID 1668 wrote to memory of 1320 1668 ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe 30 PID 1668 wrote to memory of 1320 1668 ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe 30 PID 1668 wrote to memory of 1320 1668 ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe 30 PID 1320 wrote to memory of 1416 1320 cmd.exe 32 PID 1320 wrote to memory of 1416 1320 cmd.exe 32 PID 1320 wrote to memory of 1416 1320 cmd.exe 32 PID 1320 wrote to memory of 1416 1320 cmd.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe"C:\Users\Admin\AppData\Local\Temp\ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1668 -
C:\Users\Admin\AppData\Local\Temp\ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exeC:\Users\Admin\AppData\Local\Temp\ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe /C2⤵
- Suspicious behavior: EnumeratesProcesses
PID:2024
-
-
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\ba82050e7d3f9eb857dac4746b78e62796043abc2a70028a4efa834119214c38.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1320 -
C:\Windows\SysWOW64\PING.EXEping.exe -n 6 127.0.0.13⤵
- Runs ping.exe
PID:1416
-
-