Analysis
-
max time kernel
163s -
max time network
180s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
23-11-2022 13:25
Static task
static1
Behavioral task
behavioral1
Sample
ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe
Resource
win10v2004-20221111-en
General
-
Target
ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe
-
Size
991KB
-
MD5
b00e12c16d784b4d5e711e51e0430d66
-
SHA1
d2d7d47df634c39f79331dfe2e5f953251266b17
-
SHA256
ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257
-
SHA512
09a7d929a4e3385bde47a51161647bcfa6971e6bdca1c3d40b78951f5b2db46bd448f6e912821ac27e2b54d7c824a5d9efb2c5ddcfe19a4d22317b266b17a94f
-
SSDEEP
24576:KinYayzdUnKEaoxfqyQjnr5iKULyQUVyhaPvNy/UtR:Tyz6BxfxmrNUL7lo0s
Malware Config
Extracted
bandook
sat-iva.org
Signatures
-
Bandook payload 4 IoCs
resource yara_rule behavioral2/memory/1064-142-0x0000000013140000-0x0000000013B8E000-memory.dmp family_bandook behavioral2/memory/1064-145-0x0000000013140000-0x0000000013B8E000-memory.dmp family_bandook behavioral2/memory/1064-146-0x0000000013140000-0x0000000013B8E000-memory.dmp family_bandook behavioral2/memory/1064-147-0x0000000013140000-0x0000000013B8E000-memory.dmp family_bandook -
Adds Run key to start application 2 TTPs 2 IoCs
description ioc Process Key created \REGISTRY\USER\S-1-5-21-2386679933-1492765628-3466841596-1000\Software\Microsoft\Windows\CurrentVersion\Run iexplore.exe Set value (str) \REGISTRY\USER\S-1-5-21-2386679933-1492765628-3466841596-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\obm = "C:\\Users\\Admin\\AppData\\Roaming\\obm\\obm.exe" iexplore.exe -
Suspicious use of SetThreadContext 2 IoCs
description pid Process procid_target PID 1772 set thread context of 4304 1772 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 87 PID 4304 set thread context of 1064 4304 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 94 -
Suspicious use of WriteProcessMemory 33 IoCs
description pid Process procid_target PID 1772 wrote to memory of 4304 1772 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 87 PID 1772 wrote to memory of 4304 1772 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 87 PID 1772 wrote to memory of 4304 1772 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 87 PID 1772 wrote to memory of 4304 1772 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 87 PID 1772 wrote to memory of 4304 1772 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 87 PID 1772 wrote to memory of 4304 1772 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 87 PID 1772 wrote to memory of 4304 1772 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 87 PID 1772 wrote to memory of 4304 1772 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 87 PID 1772 wrote to memory of 4304 1772 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 87 PID 1772 wrote to memory of 4304 1772 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 87 PID 1772 wrote to memory of 4304 1772 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 87 PID 1772 wrote to memory of 4304 1772 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 87 PID 4304 wrote to memory of 1064 4304 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 94 PID 4304 wrote to memory of 1064 4304 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 94 PID 4304 wrote to memory of 1064 4304 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 94 PID 4304 wrote to memory of 1064 4304 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 94 PID 4304 wrote to memory of 1064 4304 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 94 PID 1064 wrote to memory of 2788 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 96 PID 1064 wrote to memory of 2788 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 96 PID 1064 wrote to memory of 2788 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 96 PID 1064 wrote to memory of 2788 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 96 PID 1064 wrote to memory of 3092 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 102 PID 1064 wrote to memory of 3092 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 102 PID 1064 wrote to memory of 3092 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 102 PID 1064 wrote to memory of 3092 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 102 PID 1064 wrote to memory of 4980 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 105 PID 1064 wrote to memory of 4980 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 105 PID 1064 wrote to memory of 4980 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 105 PID 1064 wrote to memory of 4980 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 105 PID 1064 wrote to memory of 3668 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 106 PID 1064 wrote to memory of 3668 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 106 PID 1064 wrote to memory of 3668 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 106 PID 1064 wrote to memory of 3668 1064 ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe 106
Processes
-
C:\Users\Admin\AppData\Local\Temp\ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe"C:\Users\Admin\AppData\Local\Temp\ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1772 -
C:\Users\Admin\AppData\Local\Temp\ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe"C:\Users\Admin\AppData\Local\Temp\ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4304 -
C:\Users\Admin\AppData\Local\Temp\ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe"C:\Users\Admin\AppData\Local\Temp\ab87cb76028fce6863acec34faebf250bad0f17120188b5f95fec8f37a2aa257.exe"3⤵
- Suspicious use of WriteProcessMemory
PID:1064 -
C:\Program Files (x86)\Internet Explorer\iexplore.exe"C:\Program Files (x86)\Internet Explorer\iexplore.exe"4⤵PID:2788
-
-
C:\Program Files (x86)\Internet Explorer\iexplore.exe"C:\Program Files (x86)\Internet Explorer\iexplore.exe"4⤵
- Adds Run key to start application
PID:3092
-
-
C:\Program Files (x86)\Internet Explorer\iexplore.exe"C:\Program Files (x86)\Internet Explorer\iexplore.exe"4⤵PID:4980
-
-
C:\Program Files (x86)\Internet Explorer\iexplore.exe"C:\Program Files (x86)\Internet Explorer\iexplore.exe"4⤵PID:3668
-
-
-