Analysis
-
max time kernel
148s -
max time network
146s -
platform
windows7_x64 -
resource
win7-20230705-en -
resource tags
arch:x64arch:x86image:win7-20230705-enlocale:en-usos:windows7-x64system -
submitted
10-07-2023 14:19
Static task
static1
Behavioral task
behavioral1
Sample
4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe
Resource
win7-20230705-en
Behavioral task
behavioral2
Sample
4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe
Resource
win10v2004-20230703-en
General
-
Target
4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe
-
Size
977KB
-
MD5
f000ca9522aafa0c54b863528228a43b
-
SHA1
c636e88b9e8079ba086f5cdb132fa39e747d0f23
-
SHA256
4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3
-
SHA512
ccbb478d676a3c6f1355ab30933196c5bf41b64b613e8efe661546c238700ce2aec340390af9069c303a43bc7c4f41400c418920041cf4967c6e02b272ef372d
-
SSDEEP
24576:2ZcgQmXNGZQFXu+pcUKR9ZS2hWN8ow/hvdY/:2ZBgZRZUwJ
Malware Config
Extracted
bandook
iamgood.blogdns.net
Signatures
-
Bandook payload 2 IoCs
Processes:
resource yara_rule behavioral1/memory/2084-61-0x0000000013140000-0x0000000013B93000-memory.dmp family_bandook behavioral1/memory/2084-64-0x0000000013140000-0x0000000013B93000-memory.dmp family_bandook -
Suspicious use of SetThreadContext 1 IoCs
Processes:
4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exedescription pid process target process PID 3012 set thread context of 2084 3012 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Suspicious use of WriteProcessMemory 16 IoCs
Processes:
4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exedescription pid process target process PID 3012 wrote to memory of 2084 3012 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe PID 3012 wrote to memory of 2084 3012 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe PID 3012 wrote to memory of 2084 3012 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe PID 3012 wrote to memory of 2084 3012 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe PID 3012 wrote to memory of 2084 3012 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe PID 3012 wrote to memory of 2084 3012 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe PID 2084 wrote to memory of 2172 2084 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe iexplore.exe PID 2084 wrote to memory of 2172 2084 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe iexplore.exe PID 2084 wrote to memory of 2172 2084 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe iexplore.exe PID 2084 wrote to memory of 2172 2084 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe iexplore.exe PID 2084 wrote to memory of 2172 2084 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe iexplore.exe PID 2084 wrote to memory of 2296 2084 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe iexplore.exe PID 2084 wrote to memory of 2296 2084 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe iexplore.exe PID 2084 wrote to memory of 2296 2084 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe iexplore.exe PID 2084 wrote to memory of 2296 2084 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe iexplore.exe PID 2084 wrote to memory of 2296 2084 4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe iexplore.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe"C:\Users\Admin\AppData\Local\Temp\4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3012 -
C:\Users\Admin\AppData\Local\Temp\4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe"C:\Users\Admin\AppData\Local\Temp\4f1923485e8cdd052467d335a6384f93cd1d50b5d927aea471e56290be29ffa3.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2084 -
C:\Program Files (x86)\Internet Explorer\iexplore.exe"C:\Program Files (x86)\Internet Explorer\iexplore.exe"3⤵PID:2172
-
-
C:\Program Files (x86)\Internet Explorer\iexplore.exe"C:\Program Files (x86)\Internet Explorer\iexplore.exe"3⤵PID:2296
-
-