Analysis
-
max time kernel
70s -
max time network
134s -
platform
windows10-2004_x64 -
resource
win10v2004-20230220-en -
resource tags
arch:x64arch:x86image:win10v2004-20230220-enlocale:en-usos:windows10-2004-x64system -
submitted
21-02-2023 04:02
Static task
static1
Behavioral task
behavioral1
Sample
Setup.exe
Resource
win7-20230220-en
General
-
Target
Setup.exe
-
Size
463KB
-
MD5
dcd26511183f2d7eb30678661a88b765
-
SHA1
37157d94c22ddb5be80fb164fab68faede2711e6
-
SHA256
8f0d2909498e32a88ea7a3873958edd5456e0d9d3e766ce7c8bcc303f67d8984
-
SHA512
2bcdd37f94e3bddecaa27bb7abae837e3618debd9c91262d843b53d97e3f2f485ba586b3f7838da85a53ffa7d0887cfd496b87e366202073a7fcc233c355ba3d
-
SSDEEP
12288:LscjpZYrzMP41INt4WxGaZG3oBHgOmZndxwUnM:LscVZYD1iGWxZiQcrxHM
Malware Config
Extracted
vidar
2.5
408
-
profile_id
408
Signatures
-
Loads dropped DLL 2 IoCs
Processes:
AppLaunch.exepid process 3412 AppLaunch.exe 3412 AppLaunch.exe -
Accesses cryptocurrency files/wallets, possible credential harvesting 2 TTPs
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
Setup.exedescription pid process target process PID 2044 set thread context of 3412 2044 Setup.exe AppLaunch.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 4296 3412 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 3412 AppLaunch.exe 3412 AppLaunch.exe -
Suspicious use of WriteProcessMemory 5 IoCs
Processes:
Setup.exedescription pid process target process PID 2044 wrote to memory of 3412 2044 Setup.exe AppLaunch.exe PID 2044 wrote to memory of 3412 2044 Setup.exe AppLaunch.exe PID 2044 wrote to memory of 3412 2044 Setup.exe AppLaunch.exe PID 2044 wrote to memory of 3412 2044 Setup.exe AppLaunch.exe PID 2044 wrote to memory of 3412 2044 Setup.exe AppLaunch.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\Setup.exe"C:\Users\Admin\AppData\Local\Temp\Setup.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 3412 -s 18123⤵
- Program crash
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 468 -p 3412 -ip 34121⤵
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/3412-134-0x0000000000400000-0x0000000000472000-memory.dmpFilesize
456KB
-
memory/3412-140-0x0000000000400000-0x0000000000472000-memory.dmpFilesize
456KB
-
memory/3412-152-0x0000000050D90000-0x0000000050E83000-memory.dmpFilesize
972KB
-
memory/3412-220-0x0000000000400000-0x0000000000472000-memory.dmpFilesize
456KB
-
memory/3412-221-0x0000000000400000-0x0000000000472000-memory.dmpFilesize
456KB