<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tooling on Be The Adversary</title><link>https://betheadversary.com/tags/tooling/</link><description>Recent content in Tooling on Be The Adversary</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 13 Aug 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://betheadversary.com/tags/tooling/index.xml" rel="self" type="application/rss+xml"/><item><title>Two DGX Sparks, 33 Local Models, One Question: Can Local AI Actually Red Team?</title><link>https://betheadversary.com/posts/dgx_spark_red_team_bench/</link><pubDate>Thu, 13 Aug 2026 09:00:00 +0000</pubDate><guid>https://betheadversary.com/posts/dgx_spark_red_team_bench/</guid><description>&lt;h2 id="tldr">&lt;strong>TL;DR:&lt;/strong>&lt;a href="#tldr" class="heading-anchor" aria-label="Anchor link to: TL;DR:">#&lt;/a>&lt;/h2>
&lt;p>I built a two-node NVIDIA DGX Spark cluster and benchmarked 33 local, open-weight models for real red-team work: BloodHound attack-path analysis, phishing design, offensive coding, and a 50-prompt willingness-and-accuracy suite. The headline finding: &lt;strong>on this hardware, architecture beats size&lt;/strong>. Small sparse MoE models run circles around bigger dense ones, because the bottleneck is memory bandwidth, not compute - a 70B dense model was the slowest thing I tested. Qwen3.6-35B-A3B is the everyday pick; the model I actually run behind an agent is DeepSeek-V4-Flash-abliterated. Willingness turned out to be cheap and correctness the scarce resource, and the real project was the deployment pain, not the models. And while I did all this in a consented lab, OpenAI&amp;rsquo;s and Anthropic&amp;rsquo;s own evaluation agents broke out of their sandboxes into real companies this summer - so the question isn&amp;rsquo;t whether a model can red team, it&amp;rsquo;s whether anyone can keep one in the box. &lt;strong>Local red-team AI is real today - if you&amp;rsquo;re willing to check its work.&lt;/strong>&lt;/p></description></item><item><title>ghosttype - finding secrets in AI conversation history</title><link>https://betheadversary.com/posts/ghosttype/</link><pubDate>Wed, 13 May 2026 10:00:00 +0000</pubDate><guid>https://betheadversary.com/posts/ghosttype/</guid><description>&lt;p>I found it by accident.&lt;/p>
&lt;p>I was looking for an old conversation with Claude. Searching through history, trying to recover context I had thrown away too quickly. Eventually I found it. But while I was looking, something else clicked.&lt;/p>
&lt;p>All of these conversations are saved locally.&lt;/p>
&lt;p>Every session. Every prompt. Every response. Sitting on disk, at predictable paths, no encryption, no access controls, no logging, no detection if something reads them.&lt;/p></description></item><item><title>Log4j - where there is a fire, bring a hose</title><link>https://betheadversary.com/posts/log4j/</link><pubDate>Thu, 16 Dec 2021 00:00:00 +0000</pubDate><guid>https://betheadversary.com/posts/log4j/</guid><description>&lt;p>When there is a fire, you bring a hose of water, not a can of gasoline.&lt;/p>
&lt;p>When log4j started, one of the main challenges for organization was to identify which server is vulnerable.&lt;/p>
&lt;p>I&amp;rsquo;m happy to be a part of the team that decide to help with a solution for that problem.&lt;/p>
&lt;p>This solution is released as open-source (same like log4j) to help others for the greater good.&lt;/p>
&lt;p>Read more about it here:
&lt;a href="https://medium.com/proferosec-osm/log4jscanner-835dcd0b3430">https://medium.com/proferosec-osm/log4jscanner-835dcd0b3430&lt;/a>&lt;/p></description></item><item><title>Get busy phishing, or get busy paying - Microsoft community meetup</title><link>https://betheadversary.com/posts/get_busy_phishing/</link><pubDate>Mon, 04 Jan 2021 00:00:00 +0000</pubDate><guid>https://betheadversary.com/posts/get_busy_phishing/</guid><description>&lt;p>&lt;img alt="DIY your APT for your protection" src="https://betheadversary.com/files/Get_busy_phishing.png">&lt;/p>
&lt;p>I&amp;rsquo;ve had the pleasure to present in a recent &lt;a href="https://www.meetup.com/msc-il">Microsoft Community&lt;/a> virtual meetup about how I believe an organization should perform phishing campaign using a free platform called &lt;a href="https://getgophish.com/">GoPhish&lt;/a>.&lt;/p>
&lt;p>We covered some topics around building the actual scenario, creating an awareness program, and basically how to &amp;ldquo;arm the masses&amp;rdquo; and leverage our employees as an additional defense later instead of just complaining that &amp;ldquo;Humans are the weakest link&amp;rdquo;.&lt;/p></description></item><item><title>ADFSpray - when you need to make your own tools</title><link>https://betheadversary.com/posts/adfspray---when-you-need-to-make-your-own-tools/</link><pubDate>Thu, 23 Apr 2020 13:09:57 +0300</pubDate><guid>https://betheadversary.com/posts/adfspray---when-you-need-to-make-your-own-tools/</guid><description>&lt;p>TL;DR - new tool! &lt;a href="https://github.com/xFreed0m/adfspray">ADFSpray&lt;/a>&lt;/p>
&lt;p>I&amp;rsquo;ve needed to perform a password spraying attack against a Microsoft resource.
I&amp;rsquo;ve looked online and found various tools that looked promising (like &lt;a href="https://github.com/byt3bl33d3r/SprayingToolkit">this&lt;/a>, &lt;a href="https://github.com/dafthack/MSOLSpray/blob/master/MSOLSpray.ps1">this&lt;/a> and &lt;a href="https://github.com/Mr-Un1k0d3r/RedTeamScripts/blob/master/adfs-spray.py">this&lt;/a>, among others.&lt;/p>
&lt;p>I was happy to find many options across multiple languages, and I was confident they would save me some time,
but to my surprise, none of them worked as I needed (because of the environment I was testing, the tools themselves are working correctly).&lt;/p></description></item><item><title>Meet Caldera - Microsoft community meetup</title><link>https://betheadversary.com/posts/meet_caldera/</link><pubDate>Tue, 14 Jan 2020 00:00:00 +0000</pubDate><guid>https://betheadversary.com/posts/meet_caldera/</guid><description>&lt;p>&lt;img alt="DIY your APT for your protection" src="https://betheadversary.com/files/diy_apt.png">&lt;/p>
&lt;p>This time, I&amp;rsquo;ve made sure to upload the deck as soon as possible.&lt;/p>
&lt;p>I&amp;rsquo;ve had the pleasure to present in a recent &lt;a href="https://www.eventbrite.co.uk/o/microsoft-communities-israel-23439515053">Microsoft Community&lt;/a> meetup about providing defender automated offensive capabilities to assist in building a detection coverage map.&lt;/p>
&lt;p>Using &lt;a href="https://github.com/mitre/caldera">Caldera&lt;/a> by &lt;a href="https://www.mitre.org/">Mitre&lt;/a>, you can create your own APT, attack chains to automate specific TTP and to test if your detection mechanism is working as expected while aligning with &lt;a href="https://attack.mitre.org/">ATT&amp;amp;CK&lt;/a>.&lt;/p></description></item><item><title>Introducing: Disruption - automated AD-based environment deployment</title><link>https://betheadversary.com/posts/disruption---automated-domain-deployment/</link><pubDate>Thu, 05 Dec 2019 13:09:57 +0300</pubDate><guid>https://betheadversary.com/posts/disruption---automated-domain-deployment/</guid><description>&lt;p>Recently I&amp;rsquo;ve had the need to spin up AD domain-based environment to test stuff.
Sometimes it&amp;rsquo;s specific tools, bypasses, or how configuration change affects particular parts in a domain.&lt;/p>
&lt;p>Holding a full domain lab on a laptop\desktop is pretty cumbersome. You need resources for about 5-6 VMs running in parallel, and I couldn&amp;rsquo;t do that on my laptop.&lt;/p>
&lt;p>Besides, setting up this amount of machine plus all the needed configurations such as - setting up the domain, updating the machines, installing specific tools is a time-consuming process. Last, on top of everything - &lt;strong>I&amp;rsquo;m lazy&lt;/strong>.&lt;/p></description></item></channel></rss>