- #Sharex screen recording wallpaper engine driver#
- #Sharex screen recording wallpaper engine code#
- #Sharex screen recording wallpaper engine windows#
"ShareX-portable_12.4.1.zip.tmp" wrote 52 bytes to a remote process "C:\Windows\System32\regsvr32.exe" (Handle: 904) "ShareX-portable_12.4.1.zip.tmp" wrote 32 bytes to a remote process "C:\Windows\System32\regsvr32.exe" (Handle: 904) "ShareX-portable_12.4.1.zip.tmp" wrote 4 bytes to a remote process "C:\Windows\System32\regsvr32.exe" (Handle: 904) "ShareX-portable_12.4.1.zip.tmp" wrote 1500 bytes to a remote process "C:\Windows\System32\regsvr32.exe" (Handle: 904) "ShareX-portable_12.4.1.zip.tmp" wrote 52 bytes to a remote process "C:\Users\%USERNAME%\AppData\Local\Temp\is-4CT1G.tmp\vcredist2010.exe" (Handle: 872) "ShareX-portable_12.4.1.zip.tmp" wrote 32 bytes to a remote process "C:\Users\%USERNAME%\AppData\Local\Temp\is-4CT1G.tmp\vcredist2010.exe" (Handle: 872) "ShareX-portable_12.4.1.zip.tmp" wrote 4 bytes to a remote process "C:\Users\%USERNAME%\AppData\Local\Temp\is-4CT1G.tmp\vcredist2010.exe" (Handle: 872) "ShareX-portable_12.4.1.zip.tmp" wrote 1500 bytes to a remote process "C:\Users\%USERNAME%\AppData\Local\Temp\is-4CT1G.tmp\vcredist2010.exe" (Handle: 872) "ShareX-portable_12.4.1.zip.exe" wrote 52 bytes to a remote process "C:\Users\%USERNAME%\AppData\Local\Temp\is-1OFJB.tmp\ShareX-portable_12.4.1.zip.tmp" (Handle: 168) "ShareX-portable_12.4.1.zip.exe" wrote 32 bytes to a remote process "C:\Users\%USERNAME%\AppData\Local\Temp\is-1OFJB.tmp\ShareX-portable_12.4.1.zip.tmp" (Handle: 168) "ShareX-portable_12.4.1.zip.exe" wrote 4 bytes to a remote process "C:\Users\%USERNAME%\AppData\Local\Temp\is-1OFJB.tmp\ShareX-portable_12.4.1.zip.tmp" (Handle: 168) "ShareX-portable_12.4.1.zip.exe" wrote 1500 bytes to a remote process "%TEMP%\is-1OFJB.tmp\ShareX-portable_12.4.1.zip.tmp" (Handle: 168) 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.Ĭontains ability to query CPU informationĪdversaries may attempt to get information about running processes on a system.Īdversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system. Reads information about supported languages
#Sharex screen recording wallpaper engine windows#
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 interact with the Windows Registry to gather information about the system, configuration, and installed software. 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 can use methods of capturing user input for obtaining credentials for ] and information ] that include keylogging and user input field interception.Ĭontains ability to retrieve keyboard strokesĪdversaries may attempt to get a listing of open application windows.
#Sharex screen recording wallpaper engine 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 Installs hooks/patches the running process Windows processes often leverage application programming interface (API) functions to perform tasks that require reusable system resources.
#Sharex screen recording wallpaper engine driver#
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.Ĭontains ability to enumerate processes/modules/threads References security related windows services Processes may automatically execute specific binaries as part of their functionality or to perform other actions. Adversaries may execute a binary, command, or script via a method that interacts with Windows services, such as the Service Control Manager.