Analysis
-
max time kernel
143s -
max time network
148s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
23/09/2023, 03:43
Behavioral task
behavioral1
Sample
f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe
Resource
win7-20230831-en
5 signatures
150 seconds
General
-
Target
f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe
-
Size
5.5MB
-
MD5
d54e4139c20b0950b7efa2e53cbeb758
-
SHA1
b5015123a31bd47e69274a7545759d3e569e839a
-
SHA256
f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391
-
SHA512
4a8965e3b933f5dc802191d78f8109b717fa936faf1ef2960382cb1083c613136620f2d081af86c2f2a032409e60a6271dbcd4c55ec783a4e063dc7092413a7a
-
SSDEEP
98304:rOuarx/kHmY5tnVofqwQNp0+EJBAUZLe3cD/8Y:KB6pGJVKMr
Malware Config
Signatures
-
Detect Blackmoon payload 1 IoCs
resource yara_rule behavioral2/memory/1660-44-0x0000000002A80000-0x0000000002CFF000-memory.dmp family_blackmoon -
resource yara_rule behavioral2/memory/1660-1-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-0-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-2-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-3-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-5-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-7-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-9-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-11-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-13-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-15-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-17-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-19-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-21-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-23-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-25-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-27-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-29-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-31-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-33-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-35-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-37-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-39-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-41-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-43-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/1660-52-0x0000000010000000-0x000000001003E000-memory.dmp upx -
Suspicious behavior: EnumeratesProcesses 14 IoCs
pid Process 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe -
Suspicious use of SetWindowsHookEx 3 IoCs
pid Process 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe 1660 f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe"C:\Users\Admin\AppData\Local\Temp\f8ec515e8fb33f96da3045fa53fcdcc2e9ba7c4a0cbefc2f4209fd40217b8391.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
PID:1660