Analysis
-
max time kernel
163s -
max time network
199s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
27/11/2022, 18:19
Static task
static1
Behavioral task
behavioral1
Sample
5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe
Resource
win10v2004-20221111-en
General
-
Target
5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe
-
Size
1.6MB
-
MD5
1986b28dd4ed9b5c6a14fb303e4d3e44
-
SHA1
3d73b6420bcf40fe1d9d4f43b0073cbb133b3b42
-
SHA256
5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662
-
SHA512
f4ac5de2cc6fb3a3388e63ee3e2368abd1b1192270f21e0c734b9096533f420a326f73b24ca617fe439291dac67dd959c49a96b87fea56e9211ab5c1f396235e
-
SSDEEP
3072:1K0xSoMD4x73lMY8l3C4ymojama7enhhiD5gRLn9NEphvyAzN4VNVOTtAkwkioPF:1JwU0nhQlLcj4Y2Rym
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1252 set thread context of 1372 1252 5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe 28 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 1252 5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 1252 wrote to memory of 1372 1252 5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe 28 PID 1252 wrote to memory of 1372 1252 5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe 28 PID 1252 wrote to memory of 1372 1252 5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe 28 PID 1252 wrote to memory of 1372 1252 5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe 28 PID 1252 wrote to memory of 1372 1252 5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe 28 PID 1252 wrote to memory of 1372 1252 5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe 28 PID 1252 wrote to memory of 1372 1252 5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe 28 PID 1252 wrote to memory of 1372 1252 5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe 28 PID 1252 wrote to memory of 1372 1252 5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe 28 PID 1252 wrote to memory of 1372 1252 5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe 28 PID 1252 wrote to memory of 1372 1252 5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe"C:\Users\Admin\AppData\Local\Temp\5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1252 -
C:\Users\Admin\AppData\Local\Temp\5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe"C:\Users\Admin\AppData\Local\Temp\5fd821eb71a91956694148132aea0503cc14186ae36a4fe45685242ac74e8662.exe"2⤵PID:1372
-