Analysis
-
max time kernel
50s -
max time network
61s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
23-11-2022 14:36
Static task
static1
Behavioral task
behavioral1
Sample
1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe
Resource
win10v2004-20221111-en
General
-
Target
1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe
-
Size
1.6MB
-
MD5
f0f354af83319a24a08b8d2edac663e2
-
SHA1
d3f952136e3f44154f789627be072cc79e43d4bf
-
SHA256
1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19
-
SHA512
98183a518fe569f77a71875a68a456de393c052f21bf623396f438616ab3c6cb28ca048ba02ebc0dbc94f19d4c90a63786fe46fdfe2607dbbc9765047f49b10e
-
SSDEEP
24576:RzD5urNhRWx2Mk4JJQByw7Imlq3g495S0PwbphrpgXXOZuv/rTWeR5j4UwJZQUYf:j6/ye0PIphrp9Zuvjqa0Uid0
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exedescription pid process target process PID 1228 set thread context of 940 1228 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe -
Processes:
1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exedescription ioc process Key created \REGISTRY\USER\S-1-5-21-3385717845-2518323428-350143044-1000\Software\Microsoft\Internet Explorer\Main 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe -
Suspicious use of SetWindowsHookEx 5 IoCs
Processes:
1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exepid process 940 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 940 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 940 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 940 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 940 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe -
Suspicious use of WriteProcessMemory 11 IoCs
Processes:
1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exedescription pid process target process PID 1228 wrote to memory of 940 1228 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe PID 1228 wrote to memory of 940 1228 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe PID 1228 wrote to memory of 940 1228 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe PID 1228 wrote to memory of 940 1228 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe PID 1228 wrote to memory of 940 1228 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe PID 1228 wrote to memory of 940 1228 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe PID 1228 wrote to memory of 940 1228 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe PID 1228 wrote to memory of 940 1228 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe PID 1228 wrote to memory of 940 1228 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe PID 1228 wrote to memory of 940 1228 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe PID 1228 wrote to memory of 940 1228 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe 1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe"C:\Users\Admin\AppData\Local\Temp\1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1228 -
C:\Users\Admin\AppData\Local\Temp\1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe"C:\Users\Admin\AppData\Local\Temp\1c37cc0dd2e2dc3d738df6935e4bf2ef6c38e9d6c0a742b4a33750f8b9489d19.exe"2⤵
- Modifies Internet Explorer settings
- Suspicious use of SetWindowsHookEx
PID:940