Analysis
-
max time kernel
121s -
max time network
122s -
platform
windows7_x64 -
resource
win7-20240220-en -
resource tags
arch:x64arch:x86image:win7-20240220-enlocale:en-usos:windows7-x64system -
submitted
02/05/2024, 01:25
Static task
static1
Behavioral task
behavioral1
Sample
5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe
Resource
win7-20240220-en
Behavioral task
behavioral2
Sample
5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe
Resource
win10v2004-20240419-en
General
-
Target
5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe
-
Size
56KB
-
MD5
4f561433fb2f2231a7ac54139d0cf5f0
-
SHA1
93c83697ccad4978de499290eb6e452d6bc30c8e
-
SHA256
5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0
-
SHA512
a2e8ab0253150a0f9aabd95fffb92d3e3b91e2c280c6f2bbe56192edadaa1270e40b857ddaf4b44810b3e01ae2bc9d8227c4b0deb85197cfef652917d11b871b
-
SSDEEP
768:n6rMP5D+rgR4vZdidsAtMnhHzfOe+bF/ZUrExMIh:dP5DCvkeZT+b/oE+I
Malware Config
Signatures
-
Detects executables packed with SmartAssembly 1 IoCs
resource yara_rule behavioral1/memory/1720-1-0x0000000000830000-0x0000000000842000-memory.dmp INDICATOR_EXE_Packed_SmartAssembly -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1720 set thread context of 2808 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 28 -
Creates scheduled task(s) 1 TTPs 1 IoCs
Schtasks is often used by malware for persistence or to perform post-infection execution.
pid Process 2716 schtasks.exe -
Suspicious behavior: RenamesItself 1 IoCs
pid Process 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 1720 wrote to memory of 2808 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 28 PID 1720 wrote to memory of 2808 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 28 PID 1720 wrote to memory of 2808 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 28 PID 1720 wrote to memory of 2808 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 28 PID 1720 wrote to memory of 2808 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 28 PID 1720 wrote to memory of 2808 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 28 PID 1720 wrote to memory of 2808 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 28 PID 1720 wrote to memory of 2808 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 28 PID 1720 wrote to memory of 2808 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 28 PID 1720 wrote to memory of 2348 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 29 PID 1720 wrote to memory of 2348 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 29 PID 1720 wrote to memory of 2348 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 29 PID 1720 wrote to memory of 2348 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 29 PID 1720 wrote to memory of 2692 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 31 PID 1720 wrote to memory of 2692 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 31 PID 1720 wrote to memory of 2692 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 31 PID 1720 wrote to memory of 2692 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 31 PID 2692 wrote to memory of 2716 2692 cmd.exe 33 PID 2692 wrote to memory of 2716 2692 cmd.exe 33 PID 2692 wrote to memory of 2716 2692 cmd.exe 33 PID 2692 wrote to memory of 2716 2692 cmd.exe 33 PID 1720 wrote to memory of 2920 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 34 PID 1720 wrote to memory of 2920 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 34 PID 1720 wrote to memory of 2920 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 34 PID 1720 wrote to memory of 2920 1720 5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe 34
Processes
-
C:\Users\Admin\AppData\Local\Temp\5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe"C:\Users\Admin\AppData\Local\Temp\5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: RenamesItself
- Suspicious use of WriteProcessMemory
PID:1720 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\csc.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\csc.exe"2⤵PID:2808
-
-
C:\Windows\SysWOW64\cmd.exe"cmd.exe" /C mkdir "C:\Users\Admin\AppData\Roaming\MicrosoftTools"2⤵PID:2348
-
-
C:\Windows\SysWOW64\cmd.exe"cmd.exe" /C schtasks /create /sc minute /mo 1 /tn "Nafifas" /tr "'C:\Users\Admin\AppData\Roaming\MicrosoftTools\MicrosoftTools.exe'" /f2⤵
- Suspicious use of WriteProcessMemory
PID:2692 -
C:\Windows\SysWOW64\schtasks.exeschtasks /create /sc minute /mo 1 /tn "Nafifas" /tr "'C:\Users\Admin\AppData\Roaming\MicrosoftTools\MicrosoftTools.exe'" /f3⤵
- Creates scheduled task(s)
PID:2716
-
-
-
C:\Windows\SysWOW64\cmd.exe"cmd.exe" /C copy "C:\Users\Admin\AppData\Local\Temp\5907026171021689f041dd8ad2a1533e8fb87910f695d811772be619f3b98dc0.exe" "C:\Users\Admin\AppData\Roaming\MicrosoftTools\MicrosoftTools.exe"2⤵PID:2920
-
-
C:\Windows\system32\taskeng.exetaskeng.exe {DDFFD2DC-2EF4-40B0-AAB1-196CDDFE36A8} S-1-5-21-2721934792-624042501-2768869379-1000:BISMIZHX\Admin:Interactive:[1]1⤵PID:2724