Analysis
-
max time kernel
148s -
max time network
155s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
07/11/2022, 01:26
Behavioral task
behavioral1
Sample
c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe
Resource
win7-20220901-en
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe
Resource
win10v2004-20220812-en
5 signatures
150 seconds
General
-
Target
c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe
-
Size
186KB
-
MD5
13073ebe522b75413777ce5464ec0d56
-
SHA1
cf47c00c319e214612b8c01b43462af9d2abbaeb
-
SHA256
c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d
-
SHA512
39dbd987231636753456130ed240b5c67cd0cb7811d58f7dc578d2b10e027eae3391734891efa021a3ee950ad949e3e59f6cf2e3c64e6cc7a852fdd97ceafe52
-
SSDEEP
3072:rFvg4i9/EEr8Lk1NgK80lqLWeGONZyo5JkCIoCcQFmE1YLfth1XYWW:tgZL4LEV8kjbONZdkCI70jH2
Score
8/10
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/4840-137-0x0000000000400000-0x00000000004B7000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4840 set thread context of 5112 4840 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 80 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 5112 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 5112 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 5112 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 5112 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4840 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 4840 wrote to memory of 5112 4840 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 80 PID 4840 wrote to memory of 5112 4840 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 80 PID 4840 wrote to memory of 5112 4840 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 80 PID 4840 wrote to memory of 5112 4840 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 80 PID 4840 wrote to memory of 5112 4840 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 80 PID 4840 wrote to memory of 5112 4840 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 80 PID 4840 wrote to memory of 5112 4840 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 80 PID 5112 wrote to memory of 968 5112 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 39 PID 5112 wrote to memory of 968 5112 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 39 PID 5112 wrote to memory of 968 5112 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 39 PID 5112 wrote to memory of 968 5112 c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe 39
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:968
-
C:\Users\Admin\AppData\Local\Temp\c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe"C:\Users\Admin\AppData\Local\Temp\c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4840 -
C:\Users\Admin\AppData\Local\Temp\c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe"C:\Users\Admin\AppData\Local\Temp\c0c46f5be5d5739dc3a8e758b6bab7ed8883b58fc2bffd026147a38e7feb624d.exe"3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:5112
-
-