Analysis
-
max time kernel
278s -
max time network
323s -
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 12:29
Static task
static1
Behavioral task
behavioral1
Sample
6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe
Resource
win10v2004-20221111-en
General
-
Target
6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe
-
Size
1.3MB
-
MD5
6236fe5c26aba602d58100bf8e349c26
-
SHA1
1993827ed828a6b4d3aa97617b8a916cc391fa46
-
SHA256
6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5
-
SHA512
5f5492ae3eca41ad5ed9a9de6da4fc0fb6ae53b38565542207034f345c1a4fdfc110cceba3ca14a85727c9a87009899b319f31143144f25dfa768db06dec054b
-
SSDEEP
24576:TrKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPakc:TrKo4ZwCOnYjVmJPaD
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exedescription pid process target process PID 3476 set thread context of 3980 3476 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exedescription pid process target process PID 3476 wrote to memory of 3980 3476 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe PID 3476 wrote to memory of 3980 3476 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe PID 3476 wrote to memory of 3980 3476 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe PID 3476 wrote to memory of 3980 3476 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe PID 3476 wrote to memory of 3980 3476 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe PID 3476 wrote to memory of 3980 3476 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe PID 3476 wrote to memory of 3980 3476 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe PID 3476 wrote to memory of 3980 3476 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe PID 3476 wrote to memory of 3980 3476 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe PID 3476 wrote to memory of 3980 3476 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe 6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe"C:\Users\Admin\AppData\Local\Temp\6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3476 -
C:\Users\Admin\AppData\Local\Temp\6ad090a6f3dc81ad9d3d774bc917f0ee2b80d8efebe3af9776e618fc2bfe61a5.exePID:3980
-