https://amrosia.dev • This is a web feed, also known as an Atom feed. Subscribe by copying the URL from the address bar into your newsreader. Visit About Feeds to learn more and get started. It's free. Visit website Recent posts Updated on $DATE dark date rust Welcome to my blog! Zola2026-07-25T00:00:00+00:00https://amrosia.dev/tags/rust/atom.xml 2026-07-25T00:00:00+00:00 2026-07-25T00:00:00+00:00 amrosia https://amrosia.dev/blog/introducing-wirewrench/ <p>WireWrench v1 automated URL injection for web shells. v2 rethinks the architecture: decouple the shell from the client so the shell survives crashes, disconnects, and agent reboots.</p> <span id="continue-reading"></span><h2 id="problem"><a class="header-anchor no-hover-padding" href="#problem" aria-label="Anchor link for: problem"><span class="link-icon" aria-hidden="true"></span></a> Problem</h2> <p>AI agents and automated tooling need stateless interactions with remote shells. A traditional reverse shell ties the client and shell together — if the agent crashes or the connection drops, the session is gone.</p> <h2 id="solution"><a class="header-anchor no-hover-padding" href="#solution" aria-label="Anchor link for: solution"><span class="link-icon" aria-hidden="true"></span></a> Solution</h2> <p>Two binaries:</p> <ul> <li><strong><code>ww-server</code></strong> — Listens on a port, catches incoming reverse shells, keeps them alive</li> <li><strong><code>ww</code></strong> — Sends one-shot commands to the server, reads output over a Unix socket</li> </ul> <p>The shell stays alive regardless of what happens to the client. Multiple clients can interact with different sessions through the same server.</p> <h2 id="use-cases"><a class="header-anchor no-hover-padding" href="#use-cases" aria-label="Anchor link for: use-cases"><span class="link-icon" aria-hidden="true"></span></a> Use cases</h2> <ul> <li>Penetration testing without fragile session management</li> <li>AI-assisted operations — fire a command, read output, disconnect, come back later</li> <li>Multi-operator scenarios — team members interact with different shells on the same target</li> <li>CTFs — persistent shell access through client crashes</li> </ul> <p><a rel="external" href="https://github.com/amrosia/wirewrench">https://github.com/amrosia/wirewrench</a></p>

WireWrench v1 automated URL injection for web shells. v2 rethinks the architecture: decouple the shell from the client so the shell survives crashes, disconnects, and agent reboots…

2026-07-24T00:00:00+00:00 2026-07-24T00:00:00+00:00 amrosia https://amrosia.dev/blog/introducing-larprdp/ <p>SharpRDP runs commands on Windows over RDP by injecting keystrokes via mstscax.dll. It’s clever — RDP is a GUI protocol, and treating it as a scripting surface brings the same automation benefits that shell scripting brings to a terminal.</p> <p>But SharpRDP is Windows-only and limited to opening the Run dialog and typing one command.</p> <p>LarpRDP is a Linux-native rewrite in Rust wrapping FreeRDP3.</p> <span id="continue-reading"></span><h2 id="what-s-different"><a class="header-anchor no-hover-padding" href="#what-s-different" aria-label="Anchor link for: what-s-different"><span class="link-icon" aria-hidden="true"></span></a> What’s different</h2> <p>Headless RDP is similar to BadUSB. Instead of a single Win+R command, LarpRDP supports DuckyScript — full keystroke sequences with delays, modifier combos, and screenshot capture for verification. Same format USB Rubber Ducky uses, running over RDP.</p> <p>The repo includes an example DuckyScript that automates a reverse shell: start a listener, run <code>larprdp</code>, and it types everything out end to end.</p> <h2 id="where-it-fits"><a class="header-anchor no-hover-padding" href="#where-it-fits" aria-label="Anchor link for: where-it-fits"><span class="link-icon" aria-hidden="true"></span></a> Where it fits</h2> <ul> <li>Pentesting — post-exploitation through RDP without dropping agents</li> <li>CTFs — reverse shell onto RDP-only targets</li> <li>Red teaming — DuckyScript payloads over RDP instead of USB</li> </ul> <p><a rel="external" href="https://github.com/amrosia/LarpRDP">https://github.com/amrosia/LarpRDP</a></p>

SharpRDP runs commands on Windows over RDP by injecting keystrokes via mstscax.dll. It’s clever — RDP is a GUI protocol, and treating it as a scripting surface brings the same automation benefits that shell scripting brings to a terminal. But SharpRDP is Windows-only and limited to opening the Run dialog and typing one command. LarpRDP is a Linux-native rewrite in Rust wrapping FreeRDP3…