"vuescan.exe" wrote 8 bytes to a remote process "C:\Program Files\Internet Explorer\iexplore.exe" (Handle: 824) "vuescan.exe" wrote 52 bytes to a remote process "C:\Program Files\Internet Explorer\iexplore.exe" (Handle: 824) "vuescan.exe" wrote 32 bytes to a remote process "C:\Program Files\Internet Explorer\iexplore.exe" (Handle: 824) "Setup64.tmp" wrote 8 bytes to a remote process "C:\Program Files\VueScan\vuescan.exe" (Handle: 844) "Setup64.tmp" wrote 4 bytes to a remote process "C:\Program Files\VueScan\vuescan.exe" (Handle: 844) "Setup64.tmp" wrote 52 bytes to a remote process "C:\Program Files\VueScan\vuescan.exe" (Handle: 844) "Setup64.tmp" wrote 32 bytes to a remote process "C:\Program Files\VueScan\vuescan.exe" (Handle: 844) "Setup64.tmp" wrote 8 bytes to a remote process "C:\Program Files\VueScan\vuescan.exe" (Handle: 868) "Setup64.tmp" wrote 4 bytes to a remote process "C:\Program Files\VueScan\vuescan.exe" (Handle: 868) "Setup64.tmp" wrote 52 bytes to a remote process "C:\Program Files\VueScan\vuescan.exe" (Handle: 868) "Setup64.tmp" wrote 32 bytes to a remote process "C:\Program Files\VueScan\vuescan.exe" (Handle: 868) "Setup64.tmp" wrote 52 bytes to a remote process "C:\Program Files\VueScan\Driver\dpinst64.exe" (Handle: 484) "Setup64.tmp" wrote 32 bytes to a remote process "C:\Program Files\VueScan\Driver\dpinst64.exe" (Handle: 484)
"Setup64.tmp" wrote 8 bytes to a remote process "C:\Program Files\VueScan\Driver\dpinst64.exe" (Handle: 484) "Setup64.tmp" wrote 4 bytes to a remote process "C:\Program Files\VueScan\Driver\dpinst64.exe" (Handle: 484) "Setup64.tmp" wrote 1500 bytes to a remote process "C:\Program Files\VueScan\Driver\dpinst64.exe" (Handle: 484) "Setup64.exe" wrote 52 bytes to a remote process "C:\Users\%USERNAME%\AppData\Local\Temp\is-7H3OL.tmp\Setup64.tmp" (Handle: 204) "Setup64.exe" wrote 32 bytes to a remote process "C:\Users\%USERNAME%\AppData\Local\Temp\is-7H3OL.tmp\Setup64.tmp" (Handle: 204) "Setup64.exe" wrote 8 bytes to a remote process "C:\Users\%USERNAME%\AppData\Local\Temp\is-7H3OL.tmp\Setup64.tmp" (Handle: 204) "Setup64.exe" wrote 4 bytes to a remote process "C:\Users\%USERNAME%\AppData\Local\Temp\is-7H3OL.tmp\Setup64.tmp" (Handle: 204) "Setup64.exe" wrote 1500 bytes to a remote process "%TEMP%\is-7H3OL.tmp\Setup64.tmp" (Handle: 204) Reads the registry for installed applicationsĪn adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture.Īdversaries may attempt to get information about running processes on a system.Īdversaries may target user email to collect sensitive information from a target. Reads information about supported languages
HP OFFICEJET PRO 8600 DRIVER .INF WINDOWS
Queries volume information of an entire harddriveĪdversaries may interact with the Windows Registry to gather information about the system, configuration, and installed software. The system time is set and stored by the Windows Time Service within a domain to maintain time synchronization between systems and services in an enterprise network.Īdversaries may attempt to gather information about attached peripheral devices and components connected to a computer system.Ĭhecks a device property (often used to detect VM artifacts) Malware, tools, or other non-native files dropped or created on a system by an adversary may leave traces behind as to what was done within a network and how.Īdversaries may interact with the Windows Registry to hide configuration information within Registry keys, remove information as part of cleaning up, or as part of other techniques to aid in ] and ].Īdversaries may attempt to get a listing of open application windows.
HP OFFICEJET PRO 8600 DRIVER .INF CODE
Process injection is a method of executing arbitrary code in the address space of a separate live process.Īllocates virtual memory in a remote process Opens the Kernel Security Device Driver (KsecDD) of Windows Loadable Kernel Modules (or LKMs) are pieces of code that can be loaded and unloaded into the kernel upon demand.
Installs hooks/patches the running process Windows processes often leverage application programming interface (API) functions to perform tasks that require reusable system resources. Adversaries may execute a binary, command, or script via a method that interacts with Windows services, such as the Service Control Manager.Ĭontains ability to open/control a service