Analysis
-
max time kernel
144s -
max time network
111s -
platform
windows10-2004_x64 -
resource
win10v2004-20230220-en -
resource tags
arch:x64arch:x86image:win10v2004-20230220-enlocale:en-usos:windows10-2004-x64system -
submitted
21-03-2023 20:29
Static task
static1
Behavioral task
behavioral1
Sample
setup2.exe
Resource
win10-20230220-en
General
-
Target
setup2.exe
-
Size
457KB
-
MD5
a966945076f3ac5eb3282a0d1dc2101b
-
SHA1
71c4936cd89ec51e5d8988e6736d9584d6a18b4b
-
SHA256
e33b554abd174a255530352bf7e640f04935eae8bee36034914c131e99c6c339
-
SHA512
939fdf1ec644a2e09739868acbc737a10c19df152ea1b456a370160c31580805336fb7b1c787d6632112d46ec643f8fa940e1c7bb24b3fe06eb39cf2e2cc4d01
-
SSDEEP
12288:NdBCCL9DFn7TvTswnmsyzNkv4Yp2yYiL39g:NdBCCL9DF7Trswcw4k24g
Malware Config
Extracted
vidar
2.6
408
https://t.me/robertotalks
https://steamcommunity.com/profiles/76561199480821604
http://95.217.157.160:80
-
profile_id
408
Signatures
-
Loads dropped DLL 2 IoCs
Processes:
AppLaunch.exepid process 4248 AppLaunch.exe 4248 AppLaunch.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
setup2.exedescription pid process target process PID 2084 set thread context of 4248 2084 setup2.exe AppLaunch.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 4240 4248 WerFault.exe AppLaunch.exe -
Checks processor information in registry 2 TTPs 2 IoCs
Processor information is often read in order to detect sandboxing environments.
Processes:
AppLaunch.exedescription ioc process Key opened \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 AppLaunch.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString AppLaunch.exe -
Suspicious behavior: EnumeratesProcesses 2 IoCs
Processes:
AppLaunch.exepid process 4248 AppLaunch.exe 4248 AppLaunch.exe -
Suspicious use of WriteProcessMemory 5 IoCs
Processes:
setup2.exedescription pid process target process PID 2084 wrote to memory of 4248 2084 setup2.exe AppLaunch.exe PID 2084 wrote to memory of 4248 2084 setup2.exe AppLaunch.exe PID 2084 wrote to memory of 4248 2084 setup2.exe AppLaunch.exe PID 2084 wrote to memory of 4248 2084 setup2.exe AppLaunch.exe PID 2084 wrote to memory of 4248 2084 setup2.exe AppLaunch.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\setup2.exe"C:\Users\Admin\AppData\Local\Temp\setup2.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵
- Loads dropped DLL
- Checks processor information in registry
- Suspicious behavior: EnumeratesProcesses
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4248 -s 18523⤵
- Program crash
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 448 -p 4248 -ip 42481⤵
Network
MITRE ATT&CK Matrix ATT&CK v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\ProgramData\mozglue.dllFilesize
593KB
MD5c8fd9be83bc728cc04beffafc2907fe9
SHA195ab9f701e0024cedfbd312bcfe4e726744c4f2e
SHA256ba06a6ee0b15f5be5c4e67782eec8b521e36c107a329093ec400fe0404eb196a
SHA512fbb446f4a27ef510e616caad52945d6c9cc1fd063812c41947e579ec2b54df57c6dc46237ded80fca5847f38cbe1747a6c66a13e2c8c19c664a72be35eb8b040
-
C:\ProgramData\nss3.dllFilesize
2.0MB
MD51cc453cdf74f31e4d913ff9c10acdde2
SHA16e85eae544d6e965f15fa5c39700fa7202f3aafe
SHA256ac5c92fe6c51cfa742e475215b83b3e11a4379820043263bf50d4068686c6fa5
SHA512dd9ff4e06b00dc831439bab11c10e9b2ae864ea6e780d3835ea7468818f35439f352ef137da111efcdf2bb6465f6ca486719451bf6cf32c6a4420a56b1d64571
-
memory/4248-134-0x0000000000400000-0x0000000000470000-memory.dmpFilesize
448KB
-
memory/4248-140-0x0000000000400000-0x0000000000470000-memory.dmpFilesize
448KB
-
memory/4248-153-0x0000000061E00000-0x0000000061EF3000-memory.dmpFilesize
972KB
-
memory/4248-194-0x0000000000400000-0x0000000000470000-memory.dmpFilesize
448KB
-
memory/4248-195-0x0000000000400000-0x0000000000470000-memory.dmpFilesize
448KB