Analysis
-
max time kernel
124s -
max time network
129s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
01-10-2022 22:46
Static task
static1
Behavioral task
behavioral1
Sample
502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe
Resource
win7-20220812-en
General
-
Target
502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe
-
Size
48KB
-
MD5
00c8de3074534835cab8e3fb7491e2d0
-
SHA1
d9e23e9590135b515a4b65b916bfb89c611149e8
-
SHA256
502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6
-
SHA512
1cd8b58ceaeab571bfafd38c9014712544c6ceb44de58cf84d4b20edffc9631bbe30cb59faf1f7ba1a54d2758653246213bc351b4c55dd57abe4d126311dd053
-
SSDEEP
768:O7UKiE1U4gbZt1gbRIbPqX2CsjUFSuoOiOGf/NjwkNfIxnQtMTsMGh:OAKiE1UBbP9cPsjOSPOiOY+2f8QtksMa
Malware Config
Extracted
njrat
0.7d
HacKed
95.107.204.28:5552
1f2e4aa145fde17c3be518407ab3e0ad
-
reg_key
1f2e4aa145fde17c3be518407ab3e0ad
-
splitter
|'|'|
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exedescription pid process target process PID 2228 set thread context of 2548 2228 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 4560 2548 WerFault.exe 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exedescription pid process Token: SeDebugPrivilege 2228 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe -
Suspicious use of UnmapMainImage 1 IoCs
Processes:
502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exepid process 2548 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe -
Suspicious use of WriteProcessMemory 11 IoCs
Processes:
502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exedescription pid process target process PID 2228 wrote to memory of 2892 2228 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe PID 2228 wrote to memory of 2892 2228 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe PID 2228 wrote to memory of 2892 2228 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe PID 2228 wrote to memory of 2548 2228 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe PID 2228 wrote to memory of 2548 2228 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe PID 2228 wrote to memory of 2548 2228 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe PID 2228 wrote to memory of 2548 2228 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe PID 2228 wrote to memory of 2548 2228 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe PID 2228 wrote to memory of 2548 2228 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe PID 2228 wrote to memory of 2548 2228 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe PID 2228 wrote to memory of 2548 2228 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe 502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe"C:\Users\Admin\AppData\Local\Temp\502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exeC:\Users\Admin\AppData\Local\Temp\502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe2⤵
-
C:\Users\Admin\AppData\Local\Temp\502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exeC:\Users\Admin\AppData\Local\Temp\502fdfabbe8c4ba719eef604ea508bbdd926a3831b4beb3e60de708669f5d2e6.exe2⤵
- Suspicious use of UnmapMainImage
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2548 -s 123⤵
- Program crash
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 2548 -ip 25481⤵
Network
MITRE ATT&CK Matrix
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/2228-132-0x0000000000580000-0x0000000000594000-memory.dmpFilesize
80KB
-
memory/2228-133-0x0000000004F50000-0x0000000004FEC000-memory.dmpFilesize
624KB
-
memory/2548-134-0x0000000000000000-mapping.dmp
-
memory/2548-135-0x0000000000400000-0x000000000040C000-memory.dmpFilesize
48KB