Analysis
-
max time kernel
152s -
max time network
157s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
14/10/2023, 20:57
Static task
static1
Behavioral task
behavioral1
Sample
b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe
Resource
win7-20230831-en
Behavioral task
behavioral2
Sample
b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe
Resource
win10v2004-20230915-en
General
-
Target
b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe
-
Size
1.3MB
-
MD5
3b066ed8d386182ab068ead6eeb3f56f
-
SHA1
3be081054832612234ac15aa4693628de481511d
-
SHA256
b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c
-
SHA512
cbec0e603cae1fdad04afc255a68ba33881d8f90bcc46e8fc5990dcc48cf47eabe05a5fa5cd45d259b038b1ec18e9ae1d4e679cda1226f9485a9a98fb46b1c6e
-
SSDEEP
24576:UpwVrXW1/BToUFzFx3QP6ADGaWl2fpIUAFuVTp44O5DXqS5OWCSfMqMhl:UWwLTomkCrwfpORhXqS5OeUqM
Malware Config
Signatures
-
Suspicious use of NtSetInformationThreadHideFromDebugger 4 IoCs
pid Process 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe -
Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe -
Suspicious use of WriteProcessMemory 36 IoCs
description pid Process procid_target PID 3160 wrote to memory of 4712 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 85 PID 3160 wrote to memory of 4712 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 85 PID 3160 wrote to memory of 4776 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 87 PID 3160 wrote to memory of 4776 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 87 PID 3160 wrote to memory of 1972 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 88 PID 3160 wrote to memory of 1972 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 88 PID 3160 wrote to memory of 1020 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 89 PID 3160 wrote to memory of 1020 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 89 PID 3160 wrote to memory of 1072 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 91 PID 3160 wrote to memory of 1072 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 91 PID 3160 wrote to memory of 2636 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 92 PID 3160 wrote to memory of 2636 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 92 PID 3160 wrote to memory of 5092 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 93 PID 3160 wrote to memory of 5092 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 93 PID 3160 wrote to memory of 1632 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 94 PID 3160 wrote to memory of 1632 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 94 PID 3160 wrote to memory of 4328 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 95 PID 3160 wrote to memory of 4328 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 95 PID 3160 wrote to memory of 1400 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 96 PID 3160 wrote to memory of 1400 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 96 PID 3160 wrote to memory of 4528 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 97 PID 3160 wrote to memory of 4528 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 97 PID 3160 wrote to memory of 3840 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 98 PID 3160 wrote to memory of 3840 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 98 PID 3160 wrote to memory of 3968 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 100 PID 3160 wrote to memory of 3968 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 100 PID 3160 wrote to memory of 3992 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 101 PID 3160 wrote to memory of 3992 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 101 PID 3160 wrote to memory of 2380 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 102 PID 3160 wrote to memory of 2380 3160 b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe 102 PID 2380 wrote to memory of 2260 2380 cmd.exe 103 PID 2380 wrote to memory of 2260 2380 cmd.exe 103 PID 2380 wrote to memory of 464 2380 cmd.exe 104 PID 2380 wrote to memory of 464 2380 cmd.exe 104 PID 2380 wrote to memory of 3708 2380 cmd.exe 105 PID 2380 wrote to memory of 3708 2380 cmd.exe 105
Processes
-
C:\Users\Admin\AppData\Local\Temp\b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe"C:\Users\Admin\AppData\Local\Temp\b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe"1⤵
- Suspicious use of NtSetInformationThreadHideFromDebugger
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:3160 -
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c color 52⤵PID:4712
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c CLS2⤵PID:4776
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c CLS2⤵PID:1972
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c CLS2⤵PID:1020
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c CLS2⤵PID:1072
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c CLS2⤵PID:2636
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c CLS2⤵PID:5092
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c CLS2⤵PID:1632
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c CLS2⤵PID:4328
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c CLS2⤵PID:1400
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c CLS2⤵PID:4528
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c CLS2⤵PID:3840
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c CLS2⤵PID:3968
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c CLS2⤵PID:3992
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c certutil -hashfile "C:\Users\Admin\AppData\Local\Temp\b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe" MD5 | find /i /v "md5" | find /i /v "certutil"2⤵
- Suspicious use of WriteProcessMemory
PID:2380 -
C:\Windows\system32\certutil.execertutil -hashfile "C:\Users\Admin\AppData\Local\Temp\b9584aa08f0dda8101e6b2c679d112d5102d44c80d8aa910c29cbf20df3ea11c.exe" MD53⤵PID:2260
-
-
C:\Windows\system32\find.exefind /i /v "md5"3⤵PID:464
-
-
C:\Windows\system32\find.exefind /i /v "certutil"3⤵PID:3708
-
-