Analysis
-
max time kernel
152s -
max time network
46s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
23-11-2022 14:32
Static task
static1
Behavioral task
behavioral1
Sample
3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe
Resource
win10v2004-20220812-en
General
-
Target
3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe
-
Size
249KB
-
MD5
e19ba675744a9df9efd521604c260fba
-
SHA1
ead8f01c882f38ae10b6d4427229e8abe3ca0276
-
SHA256
3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654
-
SHA512
0d0566f67aac770fefc7c17b569bee0a2567ad4ab041018f82bb288d7875d0bcafa85001f02835450d313618b2e49b4f53c8c3928e031b41edb658776c288086
-
SSDEEP
6144:M9ZJP8+OZxKzYvJSu4R74kdGyLPkVjTqHD:cZt8+O6zYxSBR7n7LPkkH
Malware Config
Signatures
-
Suspicious use of SetThreadContext 7 IoCs
Processes:
3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exedescription pid process target process PID 1536 set thread context of 1000 1536 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1000 set thread context of 1720 1000 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1720 set thread context of 1796 1720 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1796 set thread context of 1496 1796 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1496 set thread context of 1208 1496 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1208 set thread context of 1076 1208 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1076 set thread context of 592 1076 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe -
Suspicious use of AdjustPrivilegeToken 7 IoCs
Processes:
3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exedescription pid process Token: SeDebugPrivilege 1536 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe Token: SeDebugPrivilege 1000 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe Token: SeDebugPrivilege 1720 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe Token: SeDebugPrivilege 1796 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe Token: SeDebugPrivilege 1496 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe Token: SeDebugPrivilege 1208 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe Token: SeDebugPrivilege 1076 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe -
Suspicious use of WriteProcessMemory 42 IoCs
Processes:
3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exedescription pid process target process PID 1536 wrote to memory of 1000 1536 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1536 wrote to memory of 1000 1536 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1536 wrote to memory of 1000 1536 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1536 wrote to memory of 1000 1536 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1536 wrote to memory of 1000 1536 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1536 wrote to memory of 1000 1536 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1000 wrote to memory of 1720 1000 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1000 wrote to memory of 1720 1000 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1000 wrote to memory of 1720 1000 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1000 wrote to memory of 1720 1000 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1000 wrote to memory of 1720 1000 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1000 wrote to memory of 1720 1000 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1720 wrote to memory of 1796 1720 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1720 wrote to memory of 1796 1720 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1720 wrote to memory of 1796 1720 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1720 wrote to memory of 1796 1720 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1720 wrote to memory of 1796 1720 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1720 wrote to memory of 1796 1720 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1796 wrote to memory of 1496 1796 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1796 wrote to memory of 1496 1796 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1796 wrote to memory of 1496 1796 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1796 wrote to memory of 1496 1796 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1796 wrote to memory of 1496 1796 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1796 wrote to memory of 1496 1796 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1496 wrote to memory of 1208 1496 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1496 wrote to memory of 1208 1496 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1496 wrote to memory of 1208 1496 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1496 wrote to memory of 1208 1496 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1496 wrote to memory of 1208 1496 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1496 wrote to memory of 1208 1496 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1208 wrote to memory of 1076 1208 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1208 wrote to memory of 1076 1208 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1208 wrote to memory of 1076 1208 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1208 wrote to memory of 1076 1208 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1208 wrote to memory of 1076 1208 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1208 wrote to memory of 1076 1208 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1076 wrote to memory of 592 1076 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1076 wrote to memory of 592 1076 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1076 wrote to memory of 592 1076 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1076 wrote to memory of 592 1076 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1076 wrote to memory of 592 1076 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe PID 1076 wrote to memory of 592 1076 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe 3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe"C:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1536 -
C:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exeC:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe2⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1000 -
C:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exeC:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe3⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1720 -
C:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exeC:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe4⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1796 -
C:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exeC:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe5⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1496 -
C:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exeC:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe6⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1208 -
C:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exeC:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe7⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1076 -
C:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exeC:\Users\Admin\AppData\Local\Temp\3d07d2e6578ff72a1b8a1edf8480d124a0e53eb56a5fddbc93d23e84dbb01654.exe8⤵PID:592
-
-
-
-
-
-
-