Analysis
-
max time kernel
141s -
max time network
145s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
23-11-2022 13:51
Static task
static1
Behavioral task
behavioral1
Sample
380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe
Resource
win10v2004-20221111-en
General
-
Target
380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe
-
Size
1.3MB
-
MD5
5f6754026d515a62a5bf376b6a6f3c3d
-
SHA1
263f5e8b190065009d0013b1e1d51920e35188f8
-
SHA256
380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243
-
SHA512
76c3d158c269a01a8b1ad51f1f80e2e2c89364d9dc82ca4338e0ebed2858f9a3fa8d4406a0ba7f9a151428f7bd55546f23ea1133b88b64c472142c2d29dba854
-
SSDEEP
24576:jrKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPakK:jrKo4ZwCOnYjVmJPax
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exedescription pid process target process PID 1764 set thread context of 1240 1764 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe -
Processes:
380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exedescription ioc process Key created \REGISTRY\USER\S-1-5-21-575491160-2295418218-1540667289-1000\Software\Microsoft\Internet Explorer\Main 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe -
Suspicious use of SetWindowsHookEx 5 IoCs
Processes:
380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exepid process 1240 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 1240 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 1240 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 1240 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 1240 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe -
Suspicious use of WriteProcessMemory 11 IoCs
Processes:
380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exedescription pid process target process PID 1764 wrote to memory of 1240 1764 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe PID 1764 wrote to memory of 1240 1764 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe PID 1764 wrote to memory of 1240 1764 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe PID 1764 wrote to memory of 1240 1764 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe PID 1764 wrote to memory of 1240 1764 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe PID 1764 wrote to memory of 1240 1764 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe PID 1764 wrote to memory of 1240 1764 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe PID 1764 wrote to memory of 1240 1764 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe PID 1764 wrote to memory of 1240 1764 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe PID 1764 wrote to memory of 1240 1764 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe PID 1764 wrote to memory of 1240 1764 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe 380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe"C:\Users\Admin\AppData\Local\Temp\380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1764 -
C:\Users\Admin\AppData\Local\Temp\380b8f82974aee1e718e5766f4fc84221ce456f722c9af9c535514e5d963d243.exe
- Modifies Internet Explorer settings
- Suspicious use of SetWindowsHookEx
PID:1240
Network
MITRE ATT&CK Enterprise v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/1240-54-0x0000000000400000-0x00000000004D9000-memory.dmpFilesize
868KB
-
memory/1240-55-0x0000000000400000-0x00000000004D9000-memory.dmpFilesize
868KB
-
memory/1240-57-0x0000000000400000-0x00000000004D9000-memory.dmpFilesize
868KB
-
memory/1240-59-0x0000000000400000-0x00000000004D9000-memory.dmpFilesize
868KB
-
memory/1240-61-0x0000000000400000-0x00000000004D9000-memory.dmpFilesize
868KB
-
memory/1240-63-0x0000000000400000-0x00000000004D9000-memory.dmpFilesize
868KB
-
memory/1240-65-0x0000000000400000-0x00000000004D9000-memory.dmpFilesize
868KB
-
memory/1240-66-0x000000000044E057-mapping.dmp
-
memory/1240-68-0x0000000075001000-0x0000000075003000-memory.dmpFilesize
8KB
-
memory/1240-69-0x0000000000400000-0x00000000004D9000-memory.dmpFilesize
868KB
-
memory/1240-70-0x0000000000400000-0x00000000004D9000-memory.dmpFilesize
868KB
-
memory/1240-71-0x0000000000400000-0x00000000004D9000-memory.dmpFilesize
868KB