Analysis
-
max time kernel
140s -
max time network
120s -
platform
windows7_x64 -
resource
win7-20240220-en -
resource tags
arch:x64arch:x86image:win7-20240220-enlocale:en-usos:windows7-x64system -
submitted
02-04-2024 10:06
Static task
static1
Behavioral task
behavioral1
Sample
dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe
Resource
win7-20240220-en
General
-
Target
dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe
-
Size
1.3MB
-
MD5
5fec958eac0d6cd761e99616b86f9cf2
-
SHA1
fe0515cb74a579b293b3ea2d2cd88b0192326455
-
SHA256
dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699
-
SHA512
7cf78df279f4cf31fa763a7ddbaa70879c5e697adf9fac8cd4650b1e6454ad874a0e058da99a886620740bdd526eb4a8eabb1c9693e991b492a3d627bdcdbe6c
-
SSDEEP
24576:pH4G8P8VYqjxxT6qZk1rFrXc0lLF5HskwGpLF2:GG8P8VcrlcwLXPpL8
Malware Config
Extracted
qakbot
bmw01
1706268333
116.202.110.87:443
77.73.39.175:32103
185.156.172.62:443
185.117.90.142:6882
-
camp_date
2024-01-26 11:25:33 +0000 UTC
Signatures
-
Detect Qakbot Payload 12 IoCs
Processes:
resource yara_rule behavioral1/memory/840-1-0x0000000000420000-0x000000000046E000-memory.dmp family_qakbot_v5 behavioral1/memory/840-3-0x0000000000470000-0x00000000004C3000-memory.dmp family_qakbot_v5 behavioral1/memory/1112-8-0x0000000140000000-0x0000000140030000-memory.dmp family_qakbot_v5 behavioral1/memory/1112-11-0x0000000140000000-0x0000000140030000-memory.dmp family_qakbot_v5 behavioral1/memory/1112-14-0x0000000140000000-0x0000000140030000-memory.dmp family_qakbot_v5 behavioral1/memory/1112-17-0x0000000140000000-0x0000000140030000-memory.dmp family_qakbot_v5 behavioral1/memory/1112-20-0x0000000140000000-0x0000000140030000-memory.dmp family_qakbot_v5 behavioral1/memory/840-22-0x0000000000470000-0x00000000004C3000-memory.dmp family_qakbot_v5 behavioral1/memory/1112-21-0x0000000140000000-0x0000000140030000-memory.dmp family_qakbot_v5 behavioral1/memory/1112-23-0x0000000140000000-0x0000000140030000-memory.dmp family_qakbot_v5 behavioral1/memory/1112-24-0x0000000140000000-0x0000000140030000-memory.dmp family_qakbot_v5 behavioral1/memory/1112-25-0x0000000140000000-0x0000000140030000-memory.dmp family_qakbot_v5 -
Suspicious use of SetThreadContext 1 IoCs
Processes:
dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exedescription pid process target process PID 840 set thread context of 1112 840 dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe -
Suspicious use of WriteProcessMemory 12 IoCs
Processes:
dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exedfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exedescription pid process target process PID 840 wrote to memory of 1112 840 dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe PID 840 wrote to memory of 1112 840 dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe PID 840 wrote to memory of 1112 840 dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe PID 840 wrote to memory of 1112 840 dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe PID 840 wrote to memory of 1112 840 dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe PID 840 wrote to memory of 1112 840 dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe PID 840 wrote to memory of 1112 840 dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe PID 840 wrote to memory of 1112 840 dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe PID 840 wrote to memory of 1112 840 dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe PID 1112 wrote to memory of 2940 1112 dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe WerFault.exe PID 1112 wrote to memory of 2940 1112 dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe WerFault.exe PID 1112 wrote to memory of 2940 1112 dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe WerFault.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe"C:\Users\Admin\AppData\Local\Temp\dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:840 -
C:\Users\Admin\AppData\Local\Temp\dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe"C:\Users\Admin\AppData\Local\Temp\dfe1abe2c591590f0f3b931aa439e966c380d5fdc6a9e74e6012f47f53eca699.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1112 -
C:\Windows\system32\WerFault.exeC:\Windows\system32\WerFault.exe -u -p 1112 -s 2243⤵PID:2940
-
-