Posts

Showing posts with the label t1112

370. Adversaries Disable UAC Prompts for Administrator Accounts

Image
Hello everyone! Today we’re going to look at another interesting example of the Modify Registry (T1112) technique, this time in the context of the Defense Evasion tactic. So, today’s example comes from an activity cluster known as KONNI . The malware used by the attacker modified the following registry parameter: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ConsentPromptBehaviorAdmin This parameter defines how Windows requests confirmation for privilege elevation for administrators. Of course, the attackers change its value to “0”, which allows privilege elevation to occur without any confirmation. Therefore, it may be a good idea to look for suspicious events related to modification of this parameter: event_type: "registryvaluesetwin" AND reg_key_path: "consentpromptbehavioradmin" AND reg_value_data: "0x00000000" By the way, the report we’re discussing is yet another example of how attackers are abusing AI to develop malware and tools! ...

340. Adversaries Modify the Registry to Disable Two Core Windows Security Mechanisms

Image
Hello everyone! I've shared some notable examples of Modify Registry (T1112) already. It's time for a few more interesting examples. Sophos has published a great report on Red Wolf's recent activities. According to the report, the adversary modified the following registry keys: HKLM\SYSTEM\CurrentControlSet\Control\CI\Config /v VulnerableDriverBlocklistEnable /t REG_DWORD /d 0x0 /f HKLM\\SYSTEM\\CurrentControlSet\\Control\\DeviceGuard\\Scenarios\\HypervisorEnforcedCodeIntegrity /v Enabled /t REG_DWORD /d 0x0 /f The first one disables vulnerable drivers blocklist, the second - Hypervisor-Enforced Code Integrity. Both are good targets for hunting, so: event_type: "registryvaluesetwin" AND reg_key_path: ("VulnerableDriverBlocklistEnable" OR "HypervisorEnforcedCodeIntegrity") AND reg_value_data: "0x00000000" See you tomorrow!

262. That's How Adversaries Disable Warning Messages

Image
Hello everyone! Let's look at another interesting Modify Registry (T1112) example. This time it's related to warning messages, which may trigger the victim. According to this report on CountLoader , the malware changes the registry value for " MaxScriptStatements " under: " HKEY_CURRENT_USER\\Software\\Microsoft\\Internet Explorer\\Styles\\ " to " 10000000 ". Doing this, the adversary likely attempts to bypass warning messages thrown by MSHTA when long scripts are executed. At the same time, for us - it's another hunting opportunity: event_type: "registryvaluesetwin" AND reg_key_path: "MaxScriptStatements" See you tomorrow!