Analysis
-
max time kernel
153s -
max time network
162s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
11/06/2022, 18:23
Static task
static1
Behavioral task
behavioral1
Sample
25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe
Resource
win7-20220414-en
0 signatures
0 seconds
General
-
Target
25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe
-
Size
431KB
-
MD5
f8260ab4d6bf22cb50ac4281af1528be
-
SHA1
8dd7e1ed9b17082f07e13594ea03206d1482903f
-
SHA256
25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a
-
SHA512
223600c72e56827dee049b218007798d4f1e602048fcb2e8f9a795a9cb0c94396d6b8f9cc96dbd283e79ac3e8c60a7fbfe382629ededa6b6583b9e81be115092
Malware Config
Signatures
-
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious behavior: EnumeratesProcesses 22 IoCs
pid Process 4040 25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe 4040 25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe 3396 25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe 3396 25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe 1768 detectsvcs.exe 1768 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe 1988 detectsvcs.exe -
Suspicious behavior: RenamesItself 1 IoCs
pid Process 3396 25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe -
Suspicious use of WriteProcessMemory 6 IoCs
description pid Process procid_target PID 4040 wrote to memory of 3396 4040 25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe 81 PID 4040 wrote to memory of 3396 4040 25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe 81 PID 4040 wrote to memory of 3396 4040 25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe 81 PID 1768 wrote to memory of 1988 1768 detectsvcs.exe 83 PID 1768 wrote to memory of 1988 1768 detectsvcs.exe 83 PID 1768 wrote to memory of 1988 1768 detectsvcs.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe"C:\Users\Admin\AppData\Local\Temp\25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:4040 -
C:\Users\Admin\AppData\Local\Temp\25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe"C:\Users\Admin\AppData\Local\Temp\25aaecf7f0d2fbaf8860b11c8899982912aed82d8387e87d9938bcea89a0ba8a.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: RenamesItself
PID:3396
-
-
C:\Windows\SysWOW64\detectsvcs.exe"C:\Windows\SysWOW64\detectsvcs.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1768 -
C:\Windows\SysWOW64\detectsvcs.exe"C:\Windows\SysWOW64\detectsvcs.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
PID:1988
-