Analysis
-
max time kernel
137s -
max time network
160s -
platform
windows10_x64 -
resource
win10-en-20211208 -
submitted
29-01-2022 15:07
Static task
static1
Behavioral task
behavioral1
Sample
6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe
Resource
win7-en-20211208
windows7_x64
0 signatures
0 seconds
Behavioral task
behavioral2
Sample
6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe
Resource
win10-en-20211208
windows10_x64
0 signatures
0 seconds
General
-
Target
6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe
-
Size
169KB
-
MD5
d3c8ecf591381b31d3aa796471b5b0f1
-
SHA1
efb8b908c614ef0dc791e53ad579485bc6f5e33b
-
SHA256
6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39
-
SHA512
a49d1bef7ae6e40809efe3055a78ef5d2b8c8ecbafc4499c834c80c4ad7cd1aa839e9a0914902e86b1307324b4b3d8c5f097a741ec598f1a8dd333276d54748a
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exedescription pid process target process PID 2656 set thread context of 2188 2656 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 1528 2188 WerFault.exe 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exedescription pid process Token: SeDebugPrivilege 2656 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe -
Suspicious use of WriteProcessMemory 8 IoCs
Processes:
6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exedescription pid process target process PID 2656 wrote to memory of 2188 2656 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe PID 2656 wrote to memory of 2188 2656 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe PID 2656 wrote to memory of 2188 2656 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe PID 2656 wrote to memory of 2188 2656 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe PID 2656 wrote to memory of 2188 2656 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe PID 2656 wrote to memory of 2188 2656 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe PID 2656 wrote to memory of 2188 2656 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe PID 2656 wrote to memory of 2188 2656 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe 6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe"C:\Users\Admin\AppData\Local\Temp\6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exeC:\Users\Admin\AppData\Local\Temp\6bb3c42d9ed6d25bd82fa8568cee962b6e10edddc38bc5273e97e5128872ae39.exe2⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2188 -s 923⤵
- Program crash