Analysis
-
max time kernel
151s -
max time network
189s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
23-11-2022 15:52
Behavioral task
behavioral1
Sample
82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe
Resource
win10v2004-20221111-en
General
-
Target
82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe
-
Size
80KB
-
MD5
2c751914fbec9760b967f3797b7ba9c5
-
SHA1
6f1676864bfb4ef4b38bdb369c1ca5fa807ecc42
-
SHA256
82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b
-
SHA512
f5f1e6bba2405c40e463f9e14108122fea4b79287c32ed6a7b5a5e7aecb9a097d4f939e640dbdc6f000691cb21722b0919f97d4e3225f52148504bb8b9044673
-
SSDEEP
1536:HL8wNrj0GXboKCZwrbB4kg9wJLe+VfnUsd0d+cK5hXRl4grWRUjh:HowNEGbYE2jCrVfUs+d+cKvRlgq
Malware Config
Signatures
-
Suspicious use of SetThreadContext 2 IoCs
Processes:
82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exedescription pid process target process PID 220 set thread context of 2084 220 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 2084 set thread context of 5040 2084 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
Processes:
82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exepid process 220 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 2084 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe -
Suspicious use of WriteProcessMemory 15 IoCs
Processes:
82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exedescription pid process target process PID 220 wrote to memory of 2084 220 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 220 wrote to memory of 2084 220 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 220 wrote to memory of 2084 220 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 220 wrote to memory of 2084 220 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 220 wrote to memory of 2084 220 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 220 wrote to memory of 2084 220 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 220 wrote to memory of 2084 220 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 220 wrote to memory of 2084 220 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 2084 wrote to memory of 5040 2084 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 2084 wrote to memory of 5040 2084 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 2084 wrote to memory of 5040 2084 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 2084 wrote to memory of 5040 2084 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 2084 wrote to memory of 5040 2084 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 2084 wrote to memory of 5040 2084 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe PID 2084 wrote to memory of 5040 2084 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe 82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe"C:\Users\Admin\AppData\Local\Temp\82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:220 -
C:\Users\Admin\AppData\Local\Temp\82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exeC:\Users\Admin\AppData\Local\Temp\82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2084 -
C:\Users\Admin\AppData\Local\Temp\82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exeC:\Users\Admin\AppData\Local\Temp\82b6c5d1b2016f7d11ca8257470805cf11764a043bd280e8b5de87a444c7cb4b.exe3⤵PID:5040
-
-