Analysis
- max time kernel
143s - max time network
172s - platform
windows10-2004_x64 - resource
win10v2004-20220310-en - submitted
12/03/2022, 02:00
Static task
static1
Behavioral task
behavioral1
Sample
a602aab2fa46985654a578e7b29f1505011272587d8a7545f579a44410bb245c.exe
Resource
win7-20220310-en
0 signatures
0 seconds
Behavioral task
behavioral2
Sample
a602aab2fa46985654a578e7b29f1505011272587d8a7545f579a44410bb245c.exe
Resource
win10v2004-20220310-en
0 signatures
0 seconds
General
- Target a602aab2fa46985654a578e7b29f1505011272587d8a7545f579a44410bb245c.exe
- Size 552KB
- Sample220312-ce9xtaebb8
- SHA256 a602aab2fa46985654a578e7b29f1505011272587d8a7545f579a44410bb245c
- MD5 4403a26c829661b9f5263dfa487fb580
- SHA1 55cb63dc159648200ad7635cd381606e14c5c239
- SHA512 021b848067b2295465f63fccb84e747495c7bcb844b637b8b5875f1c0b6734479482966184119a3198145793c1e9e58487722470891b66963facb7575590906a
- MD5 SHA1 SHA512
Score
5/10
Malware Config
Signatures
- Drops file in System32 directory 2 IoCs
description ioc Process File created C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\InstallService\{85516CC6-A5EE-4250-9966-8D2AE5B043E4}.catalogItem svchost.exe File created C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\InstallService\{C6AA0727-7522-429A-A9B5-6E221DB0DD65}.catalogItem svchost.exe - Checks processor information in registry 2 TTPs 3 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\Hardware\Description\System\CentralProcessor\0 svchost.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\~MHz svchost.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString svchost.exe - Enumerates system info in registry 2 TTPs 2 IoCs
description ioc Process Key opened \REGISTRY\MACHINE\Hardware\Description\System\BIOS svchost.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\BIOS\SystemSKU svchost.exe - Suspicious use of WriteProcessMemory 5 IoCs
description pid Process procid_target PID 4788 wrote to memory of 4104 4788 a602aab2fa46985654a578e7b29f1505011272587d8a7545f579a44410bb245c.exe 82 PID 4788 wrote to memory of 4104 4788 a602aab2fa46985654a578e7b29f1505011272587d8a7545f579a44410bb245c.exe 82 PID 4788 wrote to memory of 4104 4788 a602aab2fa46985654a578e7b29f1505011272587d8a7545f579a44410bb245c.exe 82 PID 4104 wrote to memory of 4040 4104 fondue.exe 90 PID 4104 wrote to memory of 4040 4104 fondue.exe 90
Processes
-
C:\Users\Admin\AppData\Local\Temp\a602aab2fa46985654a578e7b29f1505011272587d8a7545f579a44410bb245c.exe"C:\Users\Admin\AppData\Local\Temp\a602aab2fa46985654a578e7b29f1505011272587d8a7545f579a44410bb245c.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:4788 -
C:\Windows\SysWOW64\fondue.exe"C:\Windows\system32\fondue.exe" /enable-feature:NetFx3 /caller-name:mscoreei.dll2⤵
- Suspicious use of WriteProcessMemory
PID:4104 -
C:\Windows\system32\FonDUE.EXE"C:\Windows\sysnative\FonDUE.EXE" /enable-feature:NetFx3 /caller-name:mscoreei.dll3⤵PID:4040
-
-
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k netsvcs -p1⤵
- Drops file in System32 directory
- Checks processor information in registry
- Enumerates system info in registry
PID:3868