Analysis
-
max time kernel
45s -
max time network
182s -
platform
windows10-1703_x64 -
resource
win10-20220812-en -
resource tags
arch:x64arch:x86image:win10-20220812-enlocale:en-usos:windows10-1703-x64system -
submitted
24-11-2022 22:15
Static task
static1
Behavioral task
behavioral1
Sample
113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe
Resource
win10-20220812-en
General
-
Target
113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe
-
Size
424KB
-
MD5
23e5784ebbdc329735c7f902049b33ae
-
SHA1
21795c04c6aaeb050e80485a740c3bd3d1a790a2
-
SHA256
113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb
-
SHA512
e785dbad42e11cf1ce312e27acf0b21958202be48d1308bc57f065d95c71a0cf6283139ec4d9fba27a79a29a9a1f45db72b3b4f7e6aec2e9810e334286bb72f0
-
SSDEEP
12288:Qce6k34fTqLLvvmZ9osRNoBMnJbaRCzdG01:XzWXyosRNoBUlz1
Malware Config
Signatures
-
Uses the VBS compiler for execution 1 TTPs
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exedescription pid process target process PID 2408 set thread context of 4604 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe vbc.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 1468 4604 WerFault.exe vbc.exe -
Creates scheduled task(s) 1 TTPs 1 IoCs
Schtasks is often used by malware for persistence or to perform post-infection execution.
-
Suspicious behavior: RenamesItself 1 IoCs
Processes:
113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exepid process 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe -
Suspicious use of WriteProcessMemory 22 IoCs
Processes:
113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.execmd.exedescription pid process target process PID 2408 wrote to memory of 4604 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe vbc.exe PID 2408 wrote to memory of 4604 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe vbc.exe PID 2408 wrote to memory of 4604 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe vbc.exe PID 2408 wrote to memory of 4604 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe vbc.exe PID 2408 wrote to memory of 4604 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe vbc.exe PID 2408 wrote to memory of 4604 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe vbc.exe PID 2408 wrote to memory of 4604 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe vbc.exe PID 2408 wrote to memory of 4604 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe vbc.exe PID 2408 wrote to memory of 4604 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe vbc.exe PID 2408 wrote to memory of 4604 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe vbc.exe PID 2408 wrote to memory of 4684 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe cmd.exe PID 2408 wrote to memory of 4684 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe cmd.exe PID 2408 wrote to memory of 4684 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe cmd.exe PID 2408 wrote to memory of 4708 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe cmd.exe PID 2408 wrote to memory of 4708 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe cmd.exe PID 2408 wrote to memory of 4708 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe cmd.exe PID 2408 wrote to memory of 4896 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe cmd.exe PID 2408 wrote to memory of 4896 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe cmd.exe PID 2408 wrote to memory of 4896 2408 113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe cmd.exe PID 4708 wrote to memory of 3988 4708 cmd.exe schtasks.exe PID 4708 wrote to memory of 3988 4708 cmd.exe schtasks.exe PID 4708 wrote to memory of 3988 4708 cmd.exe schtasks.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe"C:\Users\Admin\AppData\Local\Temp\113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: RenamesItself
- Suspicious use of WriteProcessMemory
PID:2408 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\vbc.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\vbc.exe"2⤵PID:4604
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4604 -s 4523⤵
- Program crash
PID:1468 -
C:\Windows\SysWOW64\cmd.exe"cmd" /c mkdir "C:\Users\Admin\AppData\Roaming\Windows Security Notification Icon"2⤵PID:4684
-
C:\Windows\SysWOW64\cmd.exe"cmd" /c schtasks /create /sc minute /mo 1 /tn "Nafifas" /tr "'C:\Users\Admin\AppData\Roaming\Windows Security Notification Icon\Windows Security Notification Icon.exe'" /f2⤵
- Suspicious use of WriteProcessMemory
PID:4708 -
C:\Windows\SysWOW64\schtasks.exeschtasks /create /sc minute /mo 1 /tn "Nafifas" /tr "'C:\Users\Admin\AppData\Roaming\Windows Security Notification Icon\Windows Security Notification Icon.exe'" /f3⤵
- Creates scheduled task(s)
PID:3988 -
C:\Windows\SysWOW64\cmd.exe"cmd" /c copy "C:\Users\Admin\AppData\Local\Temp\113f1373aaeefbde43b540abc97e5a07130b6e4c926c09390e1c8fdcb622baeb.exe" "C:\Users\Admin\AppData\Roaming\Windows Security Notification Icon\Windows Security Notification Icon.exe"2⤵PID:4896