Analysis
-
max time kernel
109s -
max time network
148s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
16-02-2023 16:27
Static task
static1
Behavioral task
behavioral1
Sample
Setup.exe
Resource
win7-20220901-en
General
-
Target
Setup.exe
-
Size
451KB
-
MD5
8a1ecc6285229de387aefc6c5d3fc6e3
-
SHA1
0f2232abd9f6fbe0c29aa0a9c2c93f4532d89f9a
-
SHA256
1e1a94b620ca832df3db9166c3cdb3e2e4da334c04ed6301a7da4ecea586bb12
-
SHA512
358a85c458a36530d7741bd31b368cd676d7913cc02978addd25f868f5cc6a64bdc23e16c9586e76440e84d6151bb74a6e5ec514f8321ae7312d456f4a3fbd1a
-
SSDEEP
6144:MUGCyZKR2xcdgN8BMStlQfAk/X0DfU/8utzIPrdWspxFoZDf820w7/6Fip6y/OMW:MUGCp7e82fZPMfq3tzWdvoZL92fMBg
Malware Config
Extracted
vidar
2.5
408
-
profile_id
408
Signatures
-
Loads dropped DLL 2 IoCs
Processes:
AppLaunch.exepid process 628 AppLaunch.exe 628 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 4488 set thread context of 628 4488 Setup.exe AppLaunch.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 796 628 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 628 AppLaunch.exe 628 AppLaunch.exe -
Suspicious use of WriteProcessMemory 5 IoCs
Processes:
Setup.exedescription pid process target process PID 4488 wrote to memory of 628 4488 Setup.exe AppLaunch.exe PID 4488 wrote to memory of 628 4488 Setup.exe AppLaunch.exe PID 4488 wrote to memory of 628 4488 Setup.exe AppLaunch.exe PID 4488 wrote to memory of 628 4488 Setup.exe AppLaunch.exe PID 4488 wrote to memory of 628 4488 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 628 -s 18283⤵
- Program crash
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 420 -p 628 -ip 6281⤵
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/628-132-0x0000000000000000-mapping.dmp
-
memory/628-133-0x0000000000400000-0x0000000000472000-memory.dmpFilesize
456KB
-
memory/628-139-0x0000000000400000-0x0000000000472000-memory.dmpFilesize
456KB
-
memory/628-140-0x00000000516D0000-0x00000000517C3000-memory.dmpFilesize
972KB