Analysis
-
max time kernel
35s -
max time network
44s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
23-11-2022 10:10
Static task
static1
Behavioral task
behavioral1
Sample
be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe
Resource
win10v2004-20221111-en
General
-
Target
be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe
-
Size
1.3MB
-
MD5
89f79418a36f479cd02baf8344eeb7e5
-
SHA1
2191ffad028019454258933c6a31df832438a494
-
SHA256
be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1
-
SHA512
fcb3cc9f6214fb73baf7173006ffd61240d5550227575d44991246ebdb4e4848f8fd773421835a01171ccb322aaf1b5cc16702cfff2b2328d17a893d1d1a60bb
-
SSDEEP
24576:rrKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPakH:rrKo4ZwCOnYjVmJPak
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exedescription pid process target process PID 1772 set thread context of 1476 1772 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe -
Processes:
be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exedescription ioc process Key created \REGISTRY\USER\S-1-5-21-3406023954-474543476-3319432036-1000\Software\Microsoft\Internet Explorer\Main be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe -
Suspicious use of SetWindowsHookEx 5 IoCs
Processes:
be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exepid process 1476 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe 1476 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe 1476 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe 1476 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe 1476 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe -
Suspicious use of WriteProcessMemory 11 IoCs
Processes:
be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exedescription pid process target process PID 1772 wrote to memory of 1476 1772 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe PID 1772 wrote to memory of 1476 1772 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe PID 1772 wrote to memory of 1476 1772 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe PID 1772 wrote to memory of 1476 1772 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe PID 1772 wrote to memory of 1476 1772 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe PID 1772 wrote to memory of 1476 1772 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe PID 1772 wrote to memory of 1476 1772 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe PID 1772 wrote to memory of 1476 1772 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe PID 1772 wrote to memory of 1476 1772 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe PID 1772 wrote to memory of 1476 1772 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe PID 1772 wrote to memory of 1476 1772 be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe"C:\Users\Admin\AppData\Local\Temp\be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1772 -
C:\Users\Admin\AppData\Local\Temp\be2b0bc49c6aea6f0b77e07d71d50cf79e6e035fd2cb114cda1ad449313b7ae1.exe
- Modifies Internet Explorer settings
- Suspicious use of SetWindowsHookEx
PID:1476