Analysis
-
max time kernel
38s -
max time network
47s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
20/10/2022, 11:10
Static task
static1
Behavioral task
behavioral1
Sample
a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe
Resource
win10v2004-20220812-en
General
-
Target
a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe
-
Size
70KB
-
MD5
4628ce6c6d06bac3c1f9b1e57663db50
-
SHA1
d41b59b3f1accc342014e412df1250b139b61963
-
SHA256
a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f
-
SHA512
47f79f8c9d77aa1eebb368bf1817e74d69e7e693ae6203c33410a245453e1898b5ea8ee34dda3c560ef1753ca1577dfd80c4108d00b31e0f68906f39822a1b22
-
SSDEEP
1536:kvX0vm5+KZbCAvH3yVp5EtdVH9Qq/ZSFQca5DCh6:EX0I+KZb1SsuE8FQcl
Malware Config
Signatures
-
Suspicious behavior: EnumeratesProcesses 1 IoCs
pid Process 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe -
Suspicious behavior: MapViewOfSection 21 IoCs
pid Process 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 340 wrote to memory of 372 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 5 PID 340 wrote to memory of 372 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 5 PID 340 wrote to memory of 372 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 5 PID 340 wrote to memory of 372 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 5 PID 340 wrote to memory of 372 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 5 PID 340 wrote to memory of 372 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 5 PID 340 wrote to memory of 372 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 5 PID 340 wrote to memory of 384 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 4 PID 340 wrote to memory of 384 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 4 PID 340 wrote to memory of 384 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 4 PID 340 wrote to memory of 384 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 4 PID 340 wrote to memory of 384 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 4 PID 340 wrote to memory of 384 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 4 PID 340 wrote to memory of 384 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 4 PID 340 wrote to memory of 420 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 3 PID 340 wrote to memory of 420 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 3 PID 340 wrote to memory of 420 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 3 PID 340 wrote to memory of 420 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 3 PID 340 wrote to memory of 420 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 3 PID 340 wrote to memory of 420 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 3 PID 340 wrote to memory of 420 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 3 PID 340 wrote to memory of 464 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 2 PID 340 wrote to memory of 464 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 2 PID 340 wrote to memory of 464 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 2 PID 340 wrote to memory of 464 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 2 PID 340 wrote to memory of 464 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 2 PID 340 wrote to memory of 464 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 2 PID 340 wrote to memory of 464 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 2 PID 340 wrote to memory of 480 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 1 PID 340 wrote to memory of 480 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 1 PID 340 wrote to memory of 480 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 1 PID 340 wrote to memory of 480 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 1 PID 340 wrote to memory of 480 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 1 PID 340 wrote to memory of 480 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 1 PID 340 wrote to memory of 480 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 1 PID 340 wrote to memory of 488 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 26 PID 340 wrote to memory of 488 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 26 PID 340 wrote to memory of 488 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 26 PID 340 wrote to memory of 488 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 26 PID 340 wrote to memory of 488 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 26 PID 340 wrote to memory of 488 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 26 PID 340 wrote to memory of 488 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 26 PID 340 wrote to memory of 600 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 8 PID 340 wrote to memory of 600 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 8 PID 340 wrote to memory of 600 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 8 PID 340 wrote to memory of 600 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 8 PID 340 wrote to memory of 600 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 8 PID 340 wrote to memory of 600 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 8 PID 340 wrote to memory of 600 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 8 PID 340 wrote to memory of 676 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 25 PID 340 wrote to memory of 676 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 25 PID 340 wrote to memory of 676 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 25 PID 340 wrote to memory of 676 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 25 PID 340 wrote to memory of 676 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 25 PID 340 wrote to memory of 676 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 25 PID 340 wrote to memory of 676 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 25 PID 340 wrote to memory of 768 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 24 PID 340 wrote to memory of 768 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 24 PID 340 wrote to memory of 768 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 24 PID 340 wrote to memory of 768 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 24 PID 340 wrote to memory of 768 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 24 PID 340 wrote to memory of 768 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 24 PID 340 wrote to memory of 768 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 24 PID 340 wrote to memory of 816 340 a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe 23
Processes
-
C:\Windows\system32\lsass.exeC:\Windows\system32\lsass.exe1⤵PID:480
-
C:\Windows\system32\services.exeC:\Windows\system32\services.exe1⤵PID:464
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k DcomLaunch2⤵PID:600
-
-
C:\Windows\System32\spoolsv.exeC:\Windows\System32\spoolsv.exe2⤵PID:1028
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceAndNoImpersonation2⤵PID:1796
-
-
C:\Windows\system32\sppsvc.exeC:\Windows\system32\sppsvc.exe2⤵PID:752
-
-
C:\Windows\system32\taskhost.exe"taskhost.exe"2⤵PID:1128
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceNoNetwork2⤵PID:1056
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k NetworkService2⤵PID:292
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k netsvcs2⤵PID:880
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalService2⤵PID:856
-
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted2⤵PID:816
-
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted2⤵PID:768
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k RPCSS2⤵PID:676
-
-
C:\Windows\system32\winlogon.exewinlogon.exe1⤵PID:420
-
C:\Windows\system32\csrss.exe%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,768 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sxssrv,4 ProfileControl=Off MaxRequestThreads=161⤵PID:384
-
C:\Windows\system32\wininit.exewininit.exe1⤵PID:372
-
C:\Windows\system32\lsm.exeC:\Windows\system32\lsm.exe2⤵PID:488
-
-
\\?\C:\Windows\system32\wbem\WMIADAP.EXEwmiadap.exe /F /T /R1⤵PID:1940
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:1268
-
C:\Users\Admin\AppData\Local\Temp\a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe"C:\Users\Admin\AppData\Local\Temp\a04aab6ea96a2b83e38a82b618fbb9bffe13e8d53d29285f902f41d6dacd0f4f.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: MapViewOfSection
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:340
-
-
C:\Windows\system32\Dwm.exe"C:\Windows\system32\Dwm.exe"1⤵PID:1204