Analysis
-
max time kernel
151s -
max time network
152s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
26-06-2022 23:28
Static task
static1
Behavioral task
behavioral1
Sample
35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe
Resource
win7-20220414-en
Behavioral task
behavioral2
Sample
35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe
Resource
win10v2004-20220414-en
General
-
Target
35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe
-
Size
218KB
-
MD5
4adfc91f1cc5545b6903a300d11dd3b0
-
SHA1
eda7667e1081397ba43ccc5d6ba6d76434e05403
-
SHA256
35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6
-
SHA512
0ea92491ac4fec5487cca2b1f6570f52ae4597b92b6f6ce0760f487fed97c13db7ee7c348a0865a50c8a068cb5c50ee4af0034272dd053f7418c22903a4f472d
Malware Config
Signatures
-
Locky
Ransomware strain released in 2016, with advanced features like anti-analysis.
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exedescription pid process target process PID 4836 set thread context of 2016 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe -
Suspicious use of WriteProcessMemory 16 IoCs
Processes:
35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exedescription pid process target process PID 4836 wrote to memory of 3120 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 3120 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 3120 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 1856 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 1856 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 1856 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 2016 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 2016 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 2016 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 2016 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 2016 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 2016 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 2016 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 2016 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 2016 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe PID 4836 wrote to memory of 2016 4836 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe 35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe"C:\Users\Admin\AppData\Local\Temp\35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4836 -
C:\Users\Admin\AppData\Local\Temp\35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe"C:\Users\Admin\AppData\Local\Temp\35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe"2⤵PID:3120
-
C:\Users\Admin\AppData\Local\Temp\35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe"C:\Users\Admin\AppData\Local\Temp\35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe"2⤵PID:1856
-
C:\Users\Admin\AppData\Local\Temp\35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe"C:\Users\Admin\AppData\Local\Temp\35a9ffbbe20f8d4ed483916e15052df53714b7d5fb57fa0326cd0b138c4b73a6.exe"2⤵PID:2016
Network
MITRE ATT&CK Matrix
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/1856-131-0x0000000000000000-mapping.dmp
-
memory/2016-132-0x0000000000000000-mapping.dmp
-
memory/2016-133-0x0000000000400000-0x0000000000426000-memory.dmpFilesize
152KB
-
memory/2016-135-0x0000000000400000-0x0000000000426000-memory.dmpFilesize
152KB
-
memory/2016-136-0x0000000000400000-0x0000000000426000-memory.dmpFilesize
152KB
-
memory/2016-137-0x0000000000400000-0x0000000000426000-memory.dmpFilesize
152KB
-
memory/2016-138-0x00000000028D0000-0x00000000028F6000-memory.dmpFilesize
152KB
-
memory/3120-130-0x0000000000000000-mapping.dmp