Analysis
-
max time kernel
137s -
max time network
156s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
resource tags
arch:x64arch:x86image:win10v2004-20220414-enlocale:en-usos:windows10-2004-x64system -
submitted
17-07-2022 04:00
Static task
static1
Behavioral task
behavioral1
Sample
521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe
Resource
win7-20220414-en
windows7-x64
5 signatures
150 seconds
General
-
Target
521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe
-
Size
468KB
-
MD5
aba4534e0a32d9b6158514fd6829c29c
-
SHA1
855c1a2c25a270715ca58a8b2319c4538402adf5
-
SHA256
521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe
-
SHA512
ec038de9de260adff7e5d642c58598951425b0a88605da78eaf111a13a20ca9c5316d7a2b15959e92c257075c06237c6ccd3228f17395f4e80ebcb5474167458
Malware Config
Extracted
Family
netwire
C2
77.48.28.246:8912
Attributes
-
activex_autorun
false
-
copy_executable
false
-
delete_original
false
-
host_id
HostId-%Rand%
-
lock_executable
false
-
offline_keylogger
false
-
password
Password
-
registry_autorun
false
-
use_mutex
false
Signatures
-
NetWire RAT payload 2 IoCs
Processes:
resource yara_rule behavioral2/memory/772-138-0x0000000000400000-0x0000000000478000-memory.dmp netwire behavioral2/memory/772-139-0x0000000000400000-0x000000000042C000-memory.dmp netwire -
Suspicious use of SetThreadContext 1 IoCs
Processes:
521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exedescription pid process target process PID 4788 set thread context of 772 4788 521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe 521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exepid process 4788 521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe -
Suspicious use of WriteProcessMemory 3 IoCs
Processes:
521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exedescription pid process target process PID 4788 wrote to memory of 772 4788 521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe 521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe PID 4788 wrote to memory of 772 4788 521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe 521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe PID 4788 wrote to memory of 772 4788 521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe 521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe"C:\Users\Admin\AppData\Local\Temp\521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4788 -
C:\Users\Admin\AppData\Local\Temp\521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exeC:\Users\Admin\AppData\Local\Temp\521f60d83117e098a1864782e1839b8220d36a444210ad9bc8ab13e2be4827fe.exe"2⤵PID:772