Analysis
-
max time kernel
38s -
max time network
50s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
23-11-2022 09:09
Static task
static1
Behavioral task
behavioral1
Sample
e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe
Resource
win10v2004-20220812-en
General
-
Target
e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe
-
Size
1.3MB
-
MD5
4a0bc14772d6da9be691168ac2625576
-
SHA1
1cb388927f5e54c1777034b0067bc8c7a310947d
-
SHA256
e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330
-
SHA512
2dd3c9c43e7d4de56f1f329adc9246d8c809ae43457ed3602ec4a8ef9cb27381a7d3629e6f2ea3047572955b1acec40055b40610c4d5b5838d080700e827ef68
-
SSDEEP
24576:zrKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPakc:zrKo4ZwCOnYjVmJPaP
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exedescription pid process target process PID 1664 set thread context of 1760 1664 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe -
Processes:
e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exedescription ioc process Key created \REGISTRY\USER\S-1-5-21-2292972927-2705560509-2768824231-1000\Software\Microsoft\Internet Explorer\Main e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe -
Suspicious use of SetWindowsHookEx 5 IoCs
Processes:
e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exepid process 1760 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe 1760 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe 1760 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe 1760 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe 1760 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe -
Suspicious use of WriteProcessMemory 11 IoCs
Processes:
e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exedescription pid process target process PID 1664 wrote to memory of 1760 1664 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe PID 1664 wrote to memory of 1760 1664 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe PID 1664 wrote to memory of 1760 1664 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe PID 1664 wrote to memory of 1760 1664 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe PID 1664 wrote to memory of 1760 1664 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe PID 1664 wrote to memory of 1760 1664 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe PID 1664 wrote to memory of 1760 1664 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe PID 1664 wrote to memory of 1760 1664 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe PID 1664 wrote to memory of 1760 1664 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe PID 1664 wrote to memory of 1760 1664 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe PID 1664 wrote to memory of 1760 1664 e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe"C:\Users\Admin\AppData\Local\Temp\e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1664 -
C:\Users\Admin\AppData\Local\Temp\e4a0ebc2f0c268c48048909a688c9168f13b98c01d49f43de70be9297f218330.exe
- Modifies Internet Explorer settings
- Suspicious use of SetWindowsHookEx
PID:1760