Analysis
-
max time kernel
148s -
max time network
176s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
03/12/2022, 18:44
Behavioral task
behavioral1
Sample
a6bed9eb56c00e194e05841b1ad055814e985cd9925fb096e61e2c6ccd598981.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
a6bed9eb56c00e194e05841b1ad055814e985cd9925fb096e61e2c6ccd598981.exe
Resource
win10v2004-20220812-en
General
-
Target
a6bed9eb56c00e194e05841b1ad055814e985cd9925fb096e61e2c6ccd598981.exe
-
Size
68KB
-
MD5
0e5c60faa05c8198004b801fa0eda8ca
-
SHA1
78b7ac1fee1bb47f93955e00f0272c89fbcb0716
-
SHA256
a6bed9eb56c00e194e05841b1ad055814e985cd9925fb096e61e2c6ccd598981
-
SHA512
1c68f0a59d9c452bce4b1db4ed73ea0d0e4cc44c44c546837f02f1bca2717faae76769176527e7fa0df4fc72a18721e86261a89baf9de6be5d9a4833eef64b55
-
SSDEEP
1536:odrzxT1YKjplHraHT/QvFxLattbDiTLIs3VWYpBNxUyI:oVRNlHrISLattbeTss3TpBzI
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/3312-132-0x0000000000400000-0x000000000041F000-memory.dmp upx behavioral2/memory/3312-135-0x0000000000400000-0x000000000041F000-memory.dmp upx behavioral2/memory/3312-136-0x0000000000400000-0x000000000041F000-memory.dmp upx -
Checks processor information in registry 2 TTPs 3 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\Identifier a6bed9eb56c00e194e05841b1ad055814e985cd9925fb096e61e2c6ccd598981.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString a6bed9eb56c00e194e05841b1ad055814e985cd9925fb096e61e2c6ccd598981.exe Key created \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 a6bed9eb56c00e194e05841b1ad055814e985cd9925fb096e61e2c6ccd598981.exe -
Suspicious use of WriteProcessMemory 3 IoCs
description pid Process procid_target PID 3312 wrote to memory of 2220 3312 a6bed9eb56c00e194e05841b1ad055814e985cd9925fb096e61e2c6ccd598981.exe 79 PID 3312 wrote to memory of 2220 3312 a6bed9eb56c00e194e05841b1ad055814e985cd9925fb096e61e2c6ccd598981.exe 79 PID 3312 wrote to memory of 2220 3312 a6bed9eb56c00e194e05841b1ad055814e985cd9925fb096e61e2c6ccd598981.exe 79
Processes
-
C:\Users\Admin\AppData\Local\Temp\a6bed9eb56c00e194e05841b1ad055814e985cd9925fb096e61e2c6ccd598981.exe"C:\Users\Admin\AppData\Local\Temp\a6bed9eb56c00e194e05841b1ad055814e985cd9925fb096e61e2c6ccd598981.exe"1⤵
- Checks processor information in registry
- Suspicious use of WriteProcessMemory
PID:3312 -
C:\Windows\SysWOW64\cmd.exeC:\Windows\system32\cmd.exe /c C:\Users\Admin\AppData\Local\Temp\f93a58c116e1ba77daaf13c805f8f645.bat2⤵PID:2220
-
Network
MITRE ATT&CK Enterprise v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
255B
MD5776bb5ec3a05c6e97c8cd53687d40db1
SHA1771753ce9ef6828eed791848a86632859011b8f5
SHA25652673f18c61253acb9a714831e0ab0543a46b3c789030d2905b3700797882004
SHA51225e25fe46e622567662547acb8e1571ec3839b269a49522119b2e22ec5eebfbaaa8c72dbec8b8b5ab0463588572950556865742d6aac67a3c7c5d5434adef597