Analysis
-
max time kernel
145s -
max time network
147s -
platform
windows10_x64 -
resource
win10v20210410 -
submitted
16-05-2021 02:17
Static task
static1
Behavioral task
behavioral1
Sample
938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe
Resource
win7v20210410
windows7_x64
0 signatures
0 seconds
General
-
Target
938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe
-
Size
304KB
-
MD5
05854a0fff3ce7a777edf403bab54bc1
-
SHA1
1f0838f0a9597f9aac55452143e5fa5656688b7d
-
SHA256
938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0
-
SHA512
95e571e2db43e3c123802fb04fd34a84ea178f0e5edaf5a7c1871e2faaece753c8be923d08c020f46cfa61685f65a19f3240c557c24fa74297f1f08d5e4cc73a
Malware Config
Signatures
-
Drops file in System32 directory 1 IoCs
Processes:
diagjersey.exedescription ioc process File opened for modification C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache\counters2.dat diagjersey.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious behavior: EnumeratesProcesses 20 IoCs
Processes:
938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exediagjersey.exediagjersey.exepid process 2112 938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe 2112 938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe 4028 938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe 4028 938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe 3964 diagjersey.exe 3964 diagjersey.exe 3132 diagjersey.exe 3132 diagjersey.exe 3132 diagjersey.exe 3132 diagjersey.exe 3132 diagjersey.exe 3132 diagjersey.exe 3132 diagjersey.exe 3132 diagjersey.exe 3132 diagjersey.exe 3132 diagjersey.exe 3132 diagjersey.exe 3132 diagjersey.exe 3132 diagjersey.exe 3132 diagjersey.exe -
Suspicious behavior: RenamesItself 1 IoCs
Processes:
938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exepid process 4028 938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe -
Suspicious use of WriteProcessMemory 6 IoCs
Processes:
938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exediagjersey.exedescription pid process target process PID 2112 wrote to memory of 4028 2112 938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe 938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe PID 2112 wrote to memory of 4028 2112 938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe 938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe PID 2112 wrote to memory of 4028 2112 938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe 938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe PID 3964 wrote to memory of 3132 3964 diagjersey.exe diagjersey.exe PID 3964 wrote to memory of 3132 3964 diagjersey.exe diagjersey.exe PID 3964 wrote to memory of 3132 3964 diagjersey.exe diagjersey.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe"C:\Users\Admin\AppData\Local\Temp\938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:2112 -
C:\Users\Admin\AppData\Local\Temp\938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe"C:\Users\Admin\AppData\Local\Temp\938fc7e926c0ab109006f9a9fc6ffb1f8d5e592e188ad92eb26b0a40ff3670d0.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: RenamesItself
PID:4028
-
-
C:\Windows\SysWOW64\diagjersey.exe"C:\Windows\SysWOW64\diagjersey.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:3964 -
C:\Windows\SysWOW64\diagjersey.exe"C:\Windows\SysWOW64\diagjersey.exe"2⤵
- Drops file in System32 directory
- Suspicious behavior: EnumeratesProcesses
PID:3132
-