Analysis
-
max time kernel
168s -
max time network
177s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
27/11/2022, 08:47
Behavioral task
behavioral1
Sample
6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe
Resource
win10v2004-20221111-en
General
-
Target
6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe
-
Size
20KB
-
MD5
18877a94ab9ef09d58390bfbfa957fd0
-
SHA1
7de8c127aae5f16fced196fe5cf120ca5d97e082
-
SHA256
6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347
-
SHA512
43a953cdd2c3705a549d5ade83e856d05086d556db3edfdb8466f91b742cf6a9c05c7a7f2ff1570f429177351e93cae066fe5990fc42e6feb990a66fb1bb378b
-
SSDEEP
384:G8z+NdFxyhC3YzkDh7caNJawcudoD7U9wAKDy/KD9XhLQ:F+Ty2YGHnbcuyD7U9wT
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/1924-132-0x0000000000400000-0x000000000040D000-memory.dmp upx behavioral2/memory/1924-135-0x0000000000400000-0x000000000040D000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1924 set thread context of 4212 1924 6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe 82 -
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 6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\~MHz 6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe -
Suspicious behavior: RenamesItself 1 IoCs
pid Process 4212 6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe -
Suspicious use of WriteProcessMemory 5 IoCs
description pid Process procid_target PID 1924 wrote to memory of 4212 1924 6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe 82 PID 1924 wrote to memory of 4212 1924 6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe 82 PID 1924 wrote to memory of 4212 1924 6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe 82 PID 1924 wrote to memory of 4212 1924 6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe 82 PID 1924 wrote to memory of 4212 1924 6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe"C:\Users\Admin\AppData\Local\Temp\6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1924 -
C:\Users\Admin\AppData\Local\Temp\6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe"C:\Users\Admin\AppData\Local\Temp\6da2fc4b7ae84e7b846fda53256d9642ae9c5b3a5e18a3e34938b15237678347.exe"2⤵
- Checks processor information in registry
- Suspicious behavior: RenamesItself
PID:4212
-