Analysis
- max time kernel
114s - max time network
116s - platform
windows7_x64 - resource
win7v20201028 - submitted
15/11/2020, 23:12
Static task
static1
Behavioral task
behavioral1
Sample
ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe
- Size 270KB
- Sample201115-g3ev2lw8we
- SHA256 ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736
- MD5 7abb3f3b269cb538d97400d4924800a3
- SHA1 32e9c7d5a95cfe1c5149015e822df31293f2cec3
- SHA512 edc687909f78603bf6c093e99e408043c7d481b246ce5add21b3ea77104a40561a6065c0d9e377978da011736813e6d812fd3bad9d33ecb81c6046a1666fe770
- MD5 SHA1 SHA512
Malware Config
Signatures
- Runs ping.exe 1 TTPs 1 IoCs
pid Process 1516 PING.EXE - Suspicious behavior: EnumeratesProcesses 3 IoCs
pid Process 1036 ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe 1420 ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe 1420 ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe - Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 1036 wrote to memory of 1420 1036 ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe 29 PID 1036 wrote to memory of 1420 1036 ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe 29 PID 1036 wrote to memory of 1420 1036 ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe 29 PID 1036 wrote to memory of 1420 1036 ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe 29 PID 1036 wrote to memory of 1704 1036 ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe 30 PID 1036 wrote to memory of 1704 1036 ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe 30 PID 1036 wrote to memory of 1704 1036 ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe 30 PID 1036 wrote to memory of 1704 1036 ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe 30 PID 1704 wrote to memory of 1516 1704 cmd.exe 32 PID 1704 wrote to memory of 1516 1704 cmd.exe 32 PID 1704 wrote to memory of 1516 1704 cmd.exe 32 PID 1704 wrote to memory of 1516 1704 cmd.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe"C:\Users\Admin\AppData\Local\Temp\ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1036 -
C:\Users\Admin\AppData\Local\Temp\ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exeC:\Users\Admin\AppData\Local\Temp\ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe /C2⤵
- Suspicious behavior: EnumeratesProcesses
PID:1420
-
-
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\ea51db7d12ade290b5b46b3ce763bc5a86e779cd2fbb49c8e912c6dec50d1736.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1704 -
C:\Windows\SysWOW64\PING.EXEping.exe -n 6 127.0.0.13⤵
- Runs ping.exe
PID:1516
-
-