Analysis
- max time kernel
16s - max time network
8s - platform
windows7_x64 - resource
win7v20201028 - submitted
06/11/2020, 11:32
Static task
static1
Behavioral task
behavioral1
Sample
308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target 308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe
- Size 1.0MB
- Sample201106-g2gyv2able
- SHA256 308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8
- MD5 7688741f9299d3f988a7db8a17535346
- SHA1 1bdd4a5898181531e6f7db44a75ff7cdcac62dbb
- SHA512 459b7bc7d80c5602e8f146786e5939166bf12e19761f88924317373072242d813f1ab71541361b118805119ce342995818ce8ef74f9bb5f3587f4fc340364bda
- MD5 SHA1 SHA512
Malware Config
Signatures
- Runs ping.exe 1 TTPs 1 IoCs
pid Process 1372 PING.EXE - Suspicious behavior: EnumeratesProcesses 3 IoCs
pid Process 1084 308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe 1820 308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe 1820 308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe - Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 1084 wrote to memory of 1820 1084 308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe 29 PID 1084 wrote to memory of 1820 1084 308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe 29 PID 1084 wrote to memory of 1820 1084 308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe 29 PID 1084 wrote to memory of 1820 1084 308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe 29 PID 1084 wrote to memory of 1596 1084 308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe 30 PID 1084 wrote to memory of 1596 1084 308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe 30 PID 1084 wrote to memory of 1596 1084 308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe 30 PID 1084 wrote to memory of 1596 1084 308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe 30 PID 1596 wrote to memory of 1372 1596 cmd.exe 32 PID 1596 wrote to memory of 1372 1596 cmd.exe 32 PID 1596 wrote to memory of 1372 1596 cmd.exe 32 PID 1596 wrote to memory of 1372 1596 cmd.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe"C:\Users\Admin\AppData\Local\Temp\308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1084 -
C:\Users\Admin\AppData\Local\Temp\308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exeC:\Users\Admin\AppData\Local\Temp\308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe /C2⤵
- Suspicious behavior: EnumeratesProcesses
PID:1820
-
-
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\308c0bc34011d739fe7546bbef874c6267e77a7e1bea698380bd9602971e00b8.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1596 -
C:\Windows\SysWOW64\PING.EXEping.exe -n 6 127.0.0.13⤵
- Runs ping.exe
PID:1372
-
-