Analysis
-
max time kernel
142s -
max time network
120s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
16-03-2024 01:32
Behavioral task
behavioral1
Sample
ccc54a5b79c3cc02c75eeff2f1a71e83.exe
Resource
win7-20240221-en
windows7-x64
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
ccc54a5b79c3cc02c75eeff2f1a71e83.exe
Resource
win10v2004-20231215-en
windows10-2004-x64
6 signatures
150 seconds
General
-
Target
ccc54a5b79c3cc02c75eeff2f1a71e83.exe
-
Size
29KB
-
MD5
ccc54a5b79c3cc02c75eeff2f1a71e83
-
SHA1
839df3453f3733f3db848b44d62089cd20411150
-
SHA256
71f6d6bfed507eae1ddaea68535dd7783a9650c8ba43aa269b69f73a7ba72e0c
-
SHA512
991f49a0fecf31ea6086907ba87816bbe9a1daf7ba6da370c9f58596b7512b5f5ee62e9aa91292a8c073ee19e4227697afdc49b391ec8c276e783feae8826133
-
SSDEEP
768:Aw5O9B8/BRaPEDiJmSH+0Q2kLpSfyWsUW7yWcE:75O9B8DaPEDiJmSHMOswE
Score
7/10
Malware Config
Signatures
-
resource yara_rule behavioral1/memory/1196-0-0x0000000000400000-0x000000000040E000-memory.dmp upx behavioral1/memory/1196-2-0x0000000000400000-0x000000000040E000-memory.dmp upx behavioral1/memory/2484-3-0x0000000000400000-0x000000000040E000-memory.dmp upx behavioral1/memory/1196-1-0x00000000021A0000-0x00000000021AE000-memory.dmp upx behavioral1/memory/2484-4-0x0000000000400000-0x000000000040E000-memory.dmp upx behavioral1/memory/2484-7-0x0000000000400000-0x000000000040E000-memory.dmp upx -
Drops file in System32 directory 2 IoCs
description ioc Process File created C:\Windows\SysWOW64\gca5Svt6.exe ccc54a5b79c3cc02c75eeff2f1a71e83.exe File opened for modification C:\Windows\SysWOW64\gca5Svt6.exe ccc54a5b79c3cc02c75eeff2f1a71e83.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Program crash 1 IoCs
pid pid_target Process procid_target 2532 2484 WerFault.exe 28 -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 1196 wrote to memory of 2484 1196 ccc54a5b79c3cc02c75eeff2f1a71e83.exe 28 PID 1196 wrote to memory of 2484 1196 ccc54a5b79c3cc02c75eeff2f1a71e83.exe 28 PID 1196 wrote to memory of 2484 1196 ccc54a5b79c3cc02c75eeff2f1a71e83.exe 28 PID 1196 wrote to memory of 2484 1196 ccc54a5b79c3cc02c75eeff2f1a71e83.exe 28 PID 2484 wrote to memory of 2532 2484 ccc54a5b79c3cc02c75eeff2f1a71e83.exe 29 PID 2484 wrote to memory of 2532 2484 ccc54a5b79c3cc02c75eeff2f1a71e83.exe 29 PID 2484 wrote to memory of 2532 2484 ccc54a5b79c3cc02c75eeff2f1a71e83.exe 29 PID 2484 wrote to memory of 2532 2484 ccc54a5b79c3cc02c75eeff2f1a71e83.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\ccc54a5b79c3cc02c75eeff2f1a71e83.exe"C:\Users\Admin\AppData\Local\Temp\ccc54a5b79c3cc02c75eeff2f1a71e83.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:1196 -
C:\Users\Admin\AppData\Local\Temp\ccc54a5b79c3cc02c75eeff2f1a71e83.exe"C:\Users\Admin\AppData\Local\Temp\ccc54a5b79c3cc02c75eeff2f1a71e83.exe" y±²³2⤵
- Drops file in System32 directory
- Suspicious use of WriteProcessMemory
PID:2484 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2484 -s 2403⤵
- Program crash
PID:2532
-
-