Analysis
- max time kernel
22s - max time network
23s - platform
windows7_x64 - resource
win7v20201028 - submitted
11/11/2020, 10:52
Static task
static1
Behavioral task
behavioral1
Sample
739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target 739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe
- Size 270KB
- Sample201111-knc73lteln
- SHA256 739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f
- MD5 29b1e22cb47cd89cc58b83084b9fdff1
- SHA1 b9fbf997ed549e1c6a90cc36aa74ed793b7cc1dd
- SHA512 58fa7bd9f2cb69c117e454cb5e7b3604dc0ad58c8721257fce3900909dd6adaacbce4d932e1f2c8d94e14e6d025711b3f5d8a6d39c4e59263376f856b675797c
- MD5 SHA1 SHA512
Malware Config
Signatures
- Runs ping.exe 1 TTPs 1 IoCs
pid Process 1572 PING.EXE - Suspicious behavior: EnumeratesProcesses 3 IoCs
pid Process 1828 739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe 1740 739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe 1740 739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe - Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 1828 wrote to memory of 1740 1828 739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe 29 PID 1828 wrote to memory of 1740 1828 739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe 29 PID 1828 wrote to memory of 1740 1828 739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe 29 PID 1828 wrote to memory of 1740 1828 739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe 29 PID 1828 wrote to memory of 616 1828 739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe 30 PID 1828 wrote to memory of 616 1828 739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe 30 PID 1828 wrote to memory of 616 1828 739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe 30 PID 1828 wrote to memory of 616 1828 739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe 30 PID 616 wrote to memory of 1572 616 cmd.exe 32 PID 616 wrote to memory of 1572 616 cmd.exe 32 PID 616 wrote to memory of 1572 616 cmd.exe 32 PID 616 wrote to memory of 1572 616 cmd.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe"C:\Users\Admin\AppData\Local\Temp\739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1828 -
C:\Users\Admin\AppData\Local\Temp\739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exeC:\Users\Admin\AppData\Local\Temp\739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe /C2⤵
- Suspicious behavior: EnumeratesProcesses
PID:1740
-
-
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\739db48ea6b1103b9172815788a94d77e305edf5057748910c1afb865c26363f.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:616 -
C:\Windows\SysWOW64\PING.EXEping.exe -n 6 127.0.0.13⤵
- Runs ping.exe
PID:1572
-
-