Analysis
-
max time kernel
132s -
max time network
112s -
platform
windows10_x64 -
resource
win10v20201028 -
submitted
01/11/2020, 18:55
Static task
static1
Behavioral task
behavioral1
Sample
d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe
Resource
win7v20201028
0 signatures
0 seconds
Behavioral task
behavioral2
Sample
d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe
Resource
win10v20201028
0 signatures
0 seconds
General
-
Target
d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe
-
Size
133KB
-
MD5
ba59b52b445f45aaf8fb707445587b48
-
SHA1
4d8a885624f580a3578026acae4f0bd53032db5d
-
SHA256
d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f
-
SHA512
be951dca8946e187aacc86ef16fa319e6524191286316e3f387d21b1797f92dea6aa0f37ae47efd60f5fb7ccb342135049bb3753bbb35941438f6a690bae3137
Score
8/10
Malware Config
Signatures
-
Executes dropped EXE 3 IoCs
pid Process 4176 dJVofYvyjlan.exe 3936 wJaajIvbJlan.exe 4080 lSIBvFnOTlan.exe -
Suspicious use of WriteProcessMemory 9 IoCs
description pid Process procid_target PID 4640 wrote to memory of 4176 4640 d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe 78 PID 4640 wrote to memory of 4176 4640 d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe 78 PID 4640 wrote to memory of 4176 4640 d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe 78 PID 4640 wrote to memory of 3936 4640 d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe 79 PID 4640 wrote to memory of 3936 4640 d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe 79 PID 4640 wrote to memory of 3936 4640 d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe 79 PID 4640 wrote to memory of 4080 4640 d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe 80 PID 4640 wrote to memory of 4080 4640 d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe 80 PID 4640 wrote to memory of 4080 4640 d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe 80
Processes
-
C:\Users\Admin\AppData\Local\Temp\d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe"C:\Users\Admin\AppData\Local\Temp\d5d744e0f7984ec01593da35f26bf24e95e4b1cc8bd1c0ff4f31de5dbf94e38f.bin.sample.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:4640 -
C:\Users\Admin\AppData\Local\Temp\dJVofYvyjlan.exe"C:\Users\Admin\AppData\Local\Temp\dJVofYvyjlan.exe" 8 LAN2⤵
- Executes dropped EXE
PID:4176
-
-
C:\Users\Admin\AppData\Local\Temp\wJaajIvbJlan.exe"C:\Users\Admin\AppData\Local\Temp\wJaajIvbJlan.exe" 8 LAN2⤵
- Executes dropped EXE
PID:3936
-
-
C:\Users\Admin\AppData\Local\Temp\lSIBvFnOTlan.exe"C:\Users\Admin\AppData\Local\Temp\lSIBvFnOTlan.exe" 8 LAN2⤵
- Executes dropped EXE
PID:4080
-