Analysis
-
max time kernel
218s -
max time network
283s -
platform
windows10-1703_x64 -
resource
win10-20240404-en -
resource tags
arch:x64arch:x86image:win10-20240404-enlocale:en-usos:windows10-1703-x64system -
submitted
27-06-2024 23:16
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe
Resource
win7-20240611-en
windows7-x64
2 signatures
300 seconds
General
-
Target
baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe
-
Size
1.8MB
-
MD5
c72e70f29d3dd8fa148df55e8e6dec43
-
SHA1
2f182d43528f78d6d847b37b77da9a09a2ed1f0a
-
SHA256
baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b
-
SHA512
d1923e33057413d478daaaaa54bb157762172a58ae03fc36e0c1c6e4d64c0c33d08bff7aec8759f533331215960d739fec2ffea86d18d1d8a70105927a6a5f12
-
SSDEEP
49152:XZKDuL48I2oJDxrV/4ePVhfBHcXuCEe/vPOM6yWKp3+EmfOS:XZ2uL439144fCXubCv2M6yWy3+i
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exedescription pid process target process PID 3800 set thread context of 5112 3800 baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe RegAsm.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 3332 3800 WerFault.exe baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exedescription pid process target process PID 3800 wrote to memory of 5112 3800 baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe RegAsm.exe PID 3800 wrote to memory of 5112 3800 baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe RegAsm.exe PID 3800 wrote to memory of 5112 3800 baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe RegAsm.exe PID 3800 wrote to memory of 5112 3800 baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe RegAsm.exe PID 3800 wrote to memory of 5112 3800 baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe RegAsm.exe PID 3800 wrote to memory of 5112 3800 baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe RegAsm.exe PID 3800 wrote to memory of 5112 3800 baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe RegAsm.exe PID 3800 wrote to memory of 5112 3800 baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe RegAsm.exe PID 3800 wrote to memory of 5112 3800 baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe RegAsm.exe PID 3800 wrote to memory of 5112 3800 baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe RegAsm.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe"C:\Users\Admin\AppData\Local\Temp\baff3039b9acf97084d1b853f495026c52a4c483d010901e226beb599d23df5b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3800 -s 3002⤵
- Program crash
Network
MITRE ATT&CK Matrix
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/3800-0-0x00000000005F0000-0x00000000005F1000-memory.dmpFilesize
4KB
-
memory/5112-1-0x0000000000400000-0x0000000000596000-memory.dmpFilesize
1.6MB
-
memory/5112-3-0x0000000000400000-0x0000000000596000-memory.dmpFilesize
1.6MB
-
memory/5112-2-0x0000000000400000-0x0000000000596000-memory.dmpFilesize
1.6MB
-
memory/5112-5-0x0000000000400000-0x0000000000596000-memory.dmpFilesize
1.6MB