Analysis
-
max time kernel
135s -
max time network
153s -
platform
windows10-2004_x64 -
resource
win10v2004-20230220-en -
resource tags
arch:x64arch:x86image:win10v2004-20230220-enlocale:en-usos:windows10-2004-x64system -
submitted
15-04-2023 09:25
Behavioral task
behavioral1
Sample
file.exe
Resource
win7-20230220-en
General
-
Target
file.exe
-
Size
2.2MB
-
MD5
c06097200ce77e7d68dc2ca18b183096
-
SHA1
378e60eee98c8407808c05561b144537d0b22731
-
SHA256
36de150cba3d3477191cbe04958e9f887725df1e2e21a92cb18887620238dea2
-
SHA512
022cc8ea990c987f95f1c50fbaaa4fd40568722574393183e17fe5bca8ab18f5b5ac44054b3708d616ff5b1065be0da1b6040024edc6ab610e5a908cb9eab2ec
-
SSDEEP
49152:MqfnQVsS7590/aJKx0Wp8BKgZsj8oZ703EPaaX8nlRMAEL:MqfQjN90/eKuWp8WfZY3naXiMl
Malware Config
Extracted
vidar
3.4
76b614a229b9a88f7d0ba57796ab0fc2
https://steamcommunity.com/profiles/76561199494593681
https://t.me/auftriebs
-
profile_id_v2
76b614a229b9a88f7d0ba57796ab0fc2
-
user_agent
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:105.0) Gecko/20100101 Firefox/105.0
Signatures
-
Identifies VirtualBox via ACPI registry values (likely anti-VM) 2 TTPs 1 IoCs
description ioc Process Key opened \REGISTRY\MACHINE\HARDWARE\ACPI\DSDT\VBOX__ file.exe -
Checks BIOS information in registry 2 TTPs 2 IoCs
BIOS information is often read in order to detect sandboxing environments.
description ioc Process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion file.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion file.exe -
Loads dropped DLL 2 IoCs
pid Process 1616 jsc.exe 1616 jsc.exe -
resource yara_rule behavioral2/memory/2652-135-0x0000000000780000-0x0000000000D24000-memory.dmp themida behavioral2/memory/2652-144-0x0000000000780000-0x0000000000D24000-memory.dmp themida -
Accesses cryptocurrency files/wallets, possible credential harvesting 2 TTPs
-
description ioc Process Key value queried \REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA file.exe -
Suspicious use of NtSetInformationThreadHideFromDebugger 1 IoCs
pid Process 2652 file.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2652 set thread context of 1616 2652 file.exe 96 -
Checks processor information in registry 2 TTPs 2 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 jsc.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString jsc.exe -
Delays execution with timeout.exe 1 IoCs
pid Process 5004 timeout.exe -
Suspicious behavior: EnumeratesProcesses 24 IoCs
pid Process 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 2652 file.exe 1616 jsc.exe 1616 jsc.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 2652 file.exe -
Suspicious use of WriteProcessMemory 38 IoCs
description pid Process procid_target PID 2652 wrote to memory of 3564 2652 file.exe 85 PID 2652 wrote to memory of 3564 2652 file.exe 85 PID 2652 wrote to memory of 4536 2652 file.exe 86 PID 2652 wrote to memory of 4536 2652 file.exe 86 PID 2652 wrote to memory of 536 2652 file.exe 87 PID 2652 wrote to memory of 536 2652 file.exe 87 PID 2652 wrote to memory of 1604 2652 file.exe 88 PID 2652 wrote to memory of 1604 2652 file.exe 88 PID 2652 wrote to memory of 2340 2652 file.exe 89 PID 2652 wrote to memory of 2340 2652 file.exe 89 PID 2652 wrote to memory of 1148 2652 file.exe 90 PID 2652 wrote to memory of 1148 2652 file.exe 90 PID 2652 wrote to memory of 1452 2652 file.exe 91 PID 2652 wrote to memory of 1452 2652 file.exe 91 PID 2652 wrote to memory of 1488 2652 file.exe 92 PID 2652 wrote to memory of 1488 2652 file.exe 92 PID 2652 wrote to memory of 4568 2652 file.exe 93 PID 2652 wrote to memory of 4568 2652 file.exe 93 PID 2652 wrote to memory of 1392 2652 file.exe 94 PID 2652 wrote to memory of 1392 2652 file.exe 94 PID 2652 wrote to memory of 1560 2652 file.exe 95 PID 2652 wrote to memory of 1560 2652 file.exe 95 PID 2652 wrote to memory of 1616 2652 file.exe 96 PID 2652 wrote to memory of 1616 2652 file.exe 96 PID 2652 wrote to memory of 1616 2652 file.exe 96 PID 2652 wrote to memory of 1616 2652 file.exe 96 PID 2652 wrote to memory of 1616 2652 file.exe 96 PID 2652 wrote to memory of 1616 2652 file.exe 96 PID 2652 wrote to memory of 1616 2652 file.exe 96 PID 2652 wrote to memory of 1616 2652 file.exe 96 PID 2652 wrote to memory of 1616 2652 file.exe 96 PID 2652 wrote to memory of 1616 2652 file.exe 96 PID 1616 wrote to memory of 764 1616 jsc.exe 103 PID 1616 wrote to memory of 764 1616 jsc.exe 103 PID 1616 wrote to memory of 764 1616 jsc.exe 103 PID 764 wrote to memory of 5004 764 cmd.exe 105 PID 764 wrote to memory of 5004 764 cmd.exe 105 PID 764 wrote to memory of 5004 764 cmd.exe 105
Processes
-
C:\Users\Admin\AppData\Local\Temp\file.exe"C:\Users\Admin\AppData\Local\Temp\file.exe"1⤵
- Identifies VirtualBox via ACPI registry values (likely anti-VM)
- Checks BIOS information in registry
- Checks whether UAC is enabled
- Suspicious use of NtSetInformationThreadHideFromDebugger
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:2652 -
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe"2⤵PID:3564
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\cvtres.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\cvtres.exe"2⤵PID:4536
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ilasm.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ilasm.exe"2⤵PID:536
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorsvw.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorsvw.exe"2⤵PID:1604
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngentask.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngentask.exe"2⤵PID:2340
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Workflow.Compiler.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Workflow.Compiler.exe"2⤵PID:1148
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_compiler.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_compiler.exe"2⤵PID:1452
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_wp.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_wp.exe"2⤵PID:1488
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AppLaunch.exe"2⤵PID:4568
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\CasPol.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\CasPol.exe"2⤵PID:1392
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe"2⤵PID:1560
-
-
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\jsc.exe"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\jsc.exe"2⤵
- Loads dropped DLL
- Checks processor information in registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1616 -
C:\Windows\SysWOW64\cmd.exe"C:\Windows\System32\cmd.exe" /c timeout /t 6 & del /f /q "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\jsc.exe" & exit3⤵
- Suspicious use of WriteProcessMemory
PID:764 -
C:\Windows\SysWOW64\timeout.exetimeout /t 64⤵
- Delays execution with timeout.exe
PID:5004
-
-
-
Network
MITRE ATT&CK Enterprise v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
593KB
MD5c8fd9be83bc728cc04beffafc2907fe9
SHA195ab9f701e0024cedfbd312bcfe4e726744c4f2e
SHA256ba06a6ee0b15f5be5c4e67782eec8b521e36c107a329093ec400fe0404eb196a
SHA512fbb446f4a27ef510e616caad52945d6c9cc1fd063812c41947e579ec2b54df57c6dc46237ded80fca5847f38cbe1747a6c66a13e2c8c19c664a72be35eb8b040
-
Filesize
2.0MB
MD51cc453cdf74f31e4d913ff9c10acdde2
SHA16e85eae544d6e965f15fa5c39700fa7202f3aafe
SHA256ac5c92fe6c51cfa742e475215b83b3e11a4379820043263bf50d4068686c6fa5
SHA512dd9ff4e06b00dc831439bab11c10e9b2ae864ea6e780d3835ea7468818f35439f352ef137da111efcdf2bb6465f6ca486719451bf6cf32c6a4420a56b1d64571