Analysis
-
max time kernel
146s -
max time network
127s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
26/05/2024, 15:04
Static task
static1
Behavioral task
behavioral1
Sample
70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe
Resource
win10v2004-20240426-en
General
-
Target
70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe
-
Size
14.8MB
-
MD5
ebb837de5e0a5361e08a0b5f1b91d663
-
SHA1
df35fc640dbd033a51d16530064609ffdedd66d1
-
SHA256
70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849
-
SHA512
80d17d47bf151f3a6d070a52c2673f6b8b1a696046fcd3d15c24f4054169c26c1d7cc6f43fe512cd5548bb95627d24aa0be285efba8420f7c8f5644717a9c71f
-
SSDEEP
393216:d+S2dlA3J9ARMj/0RLIUI++rd4jK/drQAIBITVVZlNovTffMITI1kJqGxl3ACqAV:p3J9ARMj/0LIUI++rd4jK/d8AIBITVVE
Malware Config
Signatures
-
Suspicious behavior: MapViewOfSection 8 IoCs
pid Process 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe -
Suspicious behavior: RenamesItself 1 IoCs
pid Process 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 1640 wrote to memory of 1200 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 21 PID 1640 wrote to memory of 1200 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 21 PID 1640 wrote to memory of 1200 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 21 PID 1640 wrote to memory of 1200 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 21 PID 1640 wrote to memory of 1112 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 19 PID 1640 wrote to memory of 1176 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 20 PID 1640 wrote to memory of 1200 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 21 PID 1640 wrote to memory of 1200 1640 70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe 21
Processes
-
C:\Windows\system32\taskhost.exe"taskhost.exe"1⤵PID:1112
-
C:\Windows\system32\Dwm.exe"C:\Windows\system32\Dwm.exe"1⤵PID:1176
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:1200
-
C:\Users\Admin\AppData\Local\Temp\70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe"C:\Users\Admin\AppData\Local\Temp\70be4623b91e67ed1c9f5da0e36aff15b031b84e9775a7ce49fae9e844ccf849.exe"2⤵
- Suspicious behavior: MapViewOfSection
- Suspicious behavior: RenamesItself
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1640
-
-
C:\Windows\system32\Dwm.exe"C:\Windows\system32\Dwm.exe"1⤵PID:1280