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 read software policiesĪdversaries may stage collected data in a central location or directory on the local system prior to Exfiltration.Ĭreates a writable file in a temporary directoryĪdversaries may communicate using application layer protocols associated with web traffic to avoid detection/network filtering by blending in with existing traffic.Īdversaries may employ a known encryption algorithm to conceal command and control traffic rather than relying on any inherent protections provided by a communication protocol.įound malicious artifacts related to "65.8.49.90". Reads information about supported languages Queries the internet cache settings (often used to hide footprints in index.dat or internet cache)Ĭhecks warning level of secure to non-secure traffic redirection Installs hooks/patches the running processĪdversaries may interact with the Windows Registry to gather information about the system, configuration, and installed software.
Possibly tries to implement anti-virtualization techniquesĪdversaries may perform software packing or virtual machine software protection to conceal their code.Īdversaries may hook into Windows application programming interface (API) functions to collect user credentials. Adversaries may inject code into processes in order to evade process-based defenses as well as possibly elevate privileges.Īdversaries may delete files left behind by the actions of their intrusion activity.Ī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 persistence and execution.Īdversaries may employ various means to detect and avoid virtualization and analysis environments.
0 kommentar(er)
