Analysis
-
max time kernel
150s -
max time network
154s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
11/10/2022, 16:17
Behavioral task
behavioral1
Sample
67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe
Resource
win10v2004-20220812-en
General
-
Target
67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe
-
Size
1020KB
-
MD5
7cb197ebe1ec647ca6088402b424ac3b
-
SHA1
ff4a1d717047c84abd3203728d95f75ddec46c8a
-
SHA256
67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4
-
SHA512
183d000f21c6ebffb80dad422d59deb8c76c5c5de7022071f1315ea9f498c47f99fe47ec11d3de138ef578fedff30dd5d691e9fc162e6d66d48ca9b989b24abc
-
SSDEEP
24576:06D3aQqEE7pnEd7KcKJeju+MlET5JEcAZo23yKCA1jg:06D/enQKtA6bST5aZoPag
Malware Config
Signatures
-
resource yara_rule behavioral1/memory/1920-55-0x0000000000400000-0x0000000000410000-memory.dmp upx behavioral1/memory/1372-72-0x0000000000400000-0x0000000000646000-memory.dmp upx behavioral1/memory/1372-73-0x0000000000400000-0x0000000000646000-memory.dmp upx -
Reads user/profile data of web browsers 2 TTPs
Infostealers often target stored browser data, which can include saved credentials etc.
-
Adds Run key to start application 2 TTPs 2 IoCs
description ioc Process Key created \REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run\NetworkChecker = "C:\\Users\\Admin\\AppData\\Local\\Temp\\67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe" 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe -
Checks installed software on the system 1 TTPs
Looks up Uninstall key entries in the registry to enumerate software on the system.
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1920 set thread context of 1372 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 28 -
Suspicious behavior: EnumeratesProcesses 1 IoCs
pid Process 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe -
Suspicious use of WriteProcessMemory 18 IoCs
description pid Process procid_target PID 1920 wrote to memory of 2000 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 30 PID 1920 wrote to memory of 2000 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 30 PID 1920 wrote to memory of 2000 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 30 PID 1920 wrote to memory of 2000 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 30 PID 1920 wrote to memory of 1364 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 29 PID 1920 wrote to memory of 1364 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 29 PID 1920 wrote to memory of 1364 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 29 PID 1920 wrote to memory of 1364 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 29 PID 1920 wrote to memory of 1372 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 28 PID 1920 wrote to memory of 1372 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 28 PID 1920 wrote to memory of 1372 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 28 PID 1920 wrote to memory of 1372 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 28 PID 1920 wrote to memory of 1372 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 28 PID 1920 wrote to memory of 1372 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 28 PID 1920 wrote to memory of 1372 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 28 PID 1920 wrote to memory of 1372 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 28 PID 1920 wrote to memory of 1372 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 28 PID 1920 wrote to memory of 1372 1920 67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe"C:\Users\Admin\AppData\Local\Temp\67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1920 -
C:\Users\Admin\AppData\Local\Temp\67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exeC:\Users\Admin\AppData\Local\Temp\67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe2⤵
- Adds Run key to start application
PID:1372
-
-
C:\Users\Admin\AppData\Local\Temp\67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exeC:\Users\Admin\AppData\Local\Temp\67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe2⤵PID:1364
-
-
C:\Users\Admin\AppData\Local\Temp\67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exeC:\Users\Admin\AppData\Local\Temp\67ce2f7509abd7cb2fbc1f8f4c37db347345e4df5c72fe46faa89b06cf7e39b4.exe2⤵PID:2000
-