Analysis
-
max time kernel
154s -
max time network
158s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
23-11-2022 09:05
Static task
static1
Behavioral task
behavioral1
Sample
7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exe
Resource
win10v2004-20221111-en
General
-
Target
7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exe
-
Size
48KB
-
MD5
2ec27cc0872ac93cda45d164ef2c7443
-
SHA1
3e3ba10618d7d95b5cdd144079a46df1295193bf
-
SHA256
7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617
-
SHA512
223ea9175565b45cbdda2e0a4dbfbadc5cf48535b9ee641e7806e15d7de125f3a152abc66c804ee4a310d2607b87caf95c2db537ad32a15bfef903f3d11da9f2
-
SSDEEP
768:GKlHQGq9uySmZHmwqyxxluSpuCJCwtYy8:nlHQTU0wxOqSpZt98
Malware Config
Signatures
-
Modifies Installed Components in the registry 2 TTPs 2 IoCs
Processes:
7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exedescription ioc process Key created \REGISTRY\MACHINE\SOFTWARE\WOW6432Node\Microsoft\Active Setup\Installed Components\{0DA6F99F-957E-29CD-5A1A-10B6EDD5BE69} 7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\WOW6432Node\Microsoft\Active Setup\Installed Components\{0DA6F99F-957E-29CD-5A1A-10B6EDD5BE69}\stubpath = "%SystemRoot%\\system32\\V3Medic.exe" 7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exe -
Drops file in System32 directory 2 IoCs
Processes:
7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exedescription ioc process File created C:\Windows\SysWOW64\V3Medic.exe 7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exe File opened for modification C:\Windows\SysWOW64\V3Medic.exe 7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exe -
Suspicious use of WriteProcessMemory 3 IoCs
Processes:
7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exedescription pid process target process PID 3468 wrote to memory of 1776 3468 7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exe reg.exe PID 3468 wrote to memory of 1776 3468 7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exe reg.exe PID 3468 wrote to memory of 1776 3468 7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exe reg.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exe"C:\Users\Admin\AppData\Local\Temp\7c30acc6531f4502a322fb80fd9808f6265899b8ad5d0248d96954519469c617.exe"1⤵
- Modifies Installed Components in the registry
- Drops file in System32 directory
- Suspicious use of WriteProcessMemory
PID:3468 -
C:\Windows\SysWOW64\reg.exereg delete "HKEY_CURRENT_USER\Software\Microsoft\Active Setup\Installed Components\{0DA6F99F-957E-29CD-5A1A-10B6EDD5BE69}" /f2⤵PID:1776