Lee Chagolla-Christensen retweeted
1/2
LDAP signing was supposed to stop NTLM relay to LDAP. I found a way to relay coerced SMB auth to a DC with LDAP signing and channel binding enforced.
Patched in October.
Blog: specterops.io/blog/2026/10/2…
PoC: github.com/grayhatkiller/swi…
Lee Chagolla-Christensen retweeted
We are back today for round 3! We proved out and chained a number of theoretical primitives, drawing from excellent community work, to eventually load our own VM inside pokemon red. The subject matter is quite complex so I also produced a full blogpost linked 👇
Neuter models' abilities to reverse engineer to protect non-OSS binaries from bug-finding AI agents?
I sure hope this isn't being pushed.
This quoted post is unavailable.
Lee Chagolla-Christensen retweeted
Some brief thoughts on AI in hacking and optimizing for speed:
mahaloz.re/2026/09/28/hack-r…
A bit is also a response to Flare-On 13.
Lee Chagolla-Christensen retweeted
At #OffensiveAICon, @harmj0y & @tifkin_ will explore optimized evasion attacks & their transferability across EDR products.
They’ll share findings from reverse engineering four EDRs and experimenting with LLMs & GEPA to expand the search space for effective obfuscation.
Lee Chagolla-Christensen retweeted
The slides from my talk at Microsoft Bluehat Singapore are public here:
thomasdullien.github.io/abou…
It's my first BlueHat talk since the Vista days.
Lee Chagolla-Christensen retweeted
Some people in the community seem to be fully locked into the idea that there is no risk, no uplift, just hype from AI. I find this totally perplexing, it’s obvious how impactful the technology is. As capability progress continues rapidly we, more than other groups, should be advocating on behalf of people that don’t have the same foundational understanding.
Lee Chagolla-Christensen retweeted
I can't believe it's already been 10 years, what an insane ride! At this point I'm sure we'll all have BloodHound etched on our tombstones (maybe @_wald0 will have 'Thought in graphs...' 😂) - it truly was an honor working on this project with these two <3
BloodHound is 10 🎉
To celebrate, creators @_wald0, @CptJesus & @harmj0y joined for a special two-part #KnowYourAdversary.
They reminisce on the first attack graphs and look ahead to what’s next for BloodHound.
1️⃣: ghst.ly/4xT4WdA
2️⃣: ghst.ly/4zIIeqj
Lee Chagolla-Christensen retweeted
BloodHound turns 10 🎉
Congrats @_wald0, @CptJesus, @harmj0y
Original pic 👇 taken on @BlackHatEvents #BHUSA arsenal.
Will (@harmj0y) and myself are teaching a short 1.5 hr workshop today(Wed.) and tomorrow(Thurs.) about using Codex to expedite defensive workflows that anyone is open to join! Lots of other really great workshops/talks happening too. Stop by and say hi! pages.specterops.io/Black-Ha…
Lee Chagolla-Christensen retweeted
Russian threat actor Midnight Blizzard is conducting widespread traffic manipulation attacks at hotels worldwide. Result: delivering malware or redirecting auth flows at their discretion, globally.
Since early May 2026, we saw this subcluster manipulate DNS and HTTP traffic from networks served by captive portals to redirect user traffic through actor-controlled infrastructure. We’re calling the campaign CaptiveCrunch.
“We have observed notable commonalities in the equipment and management systems used across multiple affected networks.”
We break down the malware & techniques, but the most important part is how dynamic all of it is: Midnight Blizzard is using AI to support a significant portion of these operations. They are moving and changing quickly.
Feedback welcome on the suggested mitigations: microsoft.com/en-us/security…
Help spread the word to VIPs in governments, diplomatic entities, non-governmental organizations (NGOs) in the US and Europe (probably also those traveling to Black Hat)
Lee Chagolla-Christensen retweeted
I'd like to introduce Kuna, a new Rust-based decompiler that explores a highly experimental direction: self-refining decompiler development and usage. Or: a decompiler constantly improved by agents, made for agents.
Kuna rivals the best in structuring now. Let's talk about it.1/
Lee Chagolla-Christensen retweeted
We are approaching perfect binary decompilation, and, crazier still, LLMs may soon be the best decompilers on the planet. I'd like to introduce DecBench, an evaluation site to determine how close we are to completing the field of perfect decompilation.
Links and more in 🧵
Lee Chagolla-Christensen retweeted
LLM security and jailbreak testing gets messy fast.
I built Jailbreaker to make it easier to run and track jailbreak, prompt injection, and agent behavior tests.
Blog - specterops.io/blog/2026/06/2…
Github - github.com/SpecterOps/Jailbr…
Would love to hear what you think.
@SpecterOps
Lee Chagolla-Christensen retweeted
cargo-audit flags Rust dependencies with known vulnerabilities, but it doesn't tell you whether your code calls the vulnerable function.
We added a feature that checks your binary for vulnerable functions and labels any matches as "Affected," separating real exposure from advisories that don't apply.
It's live in cargo-audit 0.22.2+. If you're behind, update with `cargo install -f cargo-audit`. crates.io/crates/cargo-audit
Couldn't agree more with @joshua_saxe
Restrictive AI cyber policy around both closed and open models makes us way less safe (summing up the argument in one place)
* New AI cyber capabilities made publicly available are not obviously bad for safety. Attackers can use frontier models to find vulnerabilities and penetrate networks, but defenders can use the same models to find and fix bugs before release, or before attackers find and exploit them
* What matters is who adopts the capabilities in what way and how fast
* Defenders do have some advantages in this new AI race. There are far more defenders than attackers and we have far more GPUs. We control the software and infrastructure under attack and can vet it with AI before release
* Defenders may have more comparative advantage with AI. Defenders are already losing so have strong motivation to adopt AI quickly. In contrast, a skilled, resourced team of attackers can already penetrate any organization they want with traditional techniques; ask anyone who's ordered a penetration test against their organization about this.
* Supporting this hypothesis is the fact that even though AI social engineering capabilities have been widely available for a few years, attackers haven't completely revolutionized their operations with this tech
* When considering restricting closed frontier models, we should consider that attackers also already have access to powerful AI cyber capabilities
* To wit, open-weight models are only a few months behind closed-weight models and can be made even more useful than closed models to attackers by removing safety tuning and adding gain-of-function fine-tuning
* Attackers are unlikely to rely heavily on closed models where they'll be monitored and blocked by dedicated teams
* All this makes it obvious that frontier cybersecurity capabilities should be widely available in closed models, with monitoring, abuse detection, and rapid response. Let defenders use the best tools and give them an unfair advantage.
* We should be more aggressive in releasing open weights models too, though, because it's very risky for American labs to abandon frontier open-weight market share, as they are currently doing.
* Imagine a world in which 80% of AI inference in liberal democracies is done with models under the indirect control of the PRC (or imagine by analogy, if Windows was opaque and controlled by the PRC).
* Imagine these models are executing shell commands on all of our production servers
* American labs releasing stronger open-weight models can of course give attackers more capability in the shadows. But the supply chain risk of PRC-controlled models executing shell commands on our societal IT infrastructure dramatically outweighs the risk of attacker adoption.
* Besides, stopping capability diffusion just clearly won't work and would require a level of coordination and cooperation between the US and China that hasn't worked on Taiwan, Iran, or climate change
* Here's what we should actually do: the AI security safety community should pivot towards diffusing American closed and open weights models and competing in cyberconflict via defensive capability operationalization.
* We should focus on being the absolute best at using AI to burn down the security tech debt that lets attackers breach most networks: exposed admin portals, no MFA, stale known-vulnerable software, overprivileged identities, flat networks, broken logging.
* We should also be using frontier capabilities to find and fix more bugs faster than attackers. Restriction is a losing battle. We should instead shape diffusion to support good cybersecurity outcomes
* Also: the sky is not falling! It's true attackers are using AI for reconnaissance, phishing, coding help, translation, fake content, and operational efficiency.
* But we have not seen the huge discontinuity or crisis that restrictionists imply should already be here.
* Google/Anthropic/OpenAI/MSFT's threat-intelligence work and NCSC's assessment all point to AI mostly uplifting existing tactics so far, especially recon and social engineering, while defense also benefits.
* We need to take a breath. And compete on a long-term strategy that embraces reality; capability diffusion will continue to happen. We will win by better diffusing and operationalizing AI cyber capabilities and shaping diffusion to give cyber defenders the upper hand
Lee Chagolla-Christensen retweeted
Restrictive AI cyber policy around both closed and open models makes us way less safe (summing up the argument in one place)
* New AI cyber capabilities made publicly available are not obviously bad for safety. Attackers can use frontier models to find vulnerabilities and penetrate networks, but defenders can use the same models to find and fix bugs before release, or before attackers find and exploit them
* What matters is who adopts the capabilities in what way and how fast
* Defenders do have some advantages in this new AI race. There are far more defenders than attackers and we have far more GPUs. We control the software and infrastructure under attack and can vet it with AI before release
* Defenders may have more comparative advantage with AI. Defenders are already losing so have strong motivation to adopt AI quickly. In contrast, a skilled, resourced team of attackers can already penetrate any organization they want with traditional techniques; ask anyone who's ordered a penetration test against their organization about this.
* Supporting this hypothesis is the fact that even though AI social engineering capabilities have been widely available for a few years, attackers haven't completely revolutionized their operations with this tech
* When considering restricting closed frontier models, we should consider that attackers also already have access to powerful AI cyber capabilities
* To wit, open-weight models are only a few months behind closed-weight models and can be made even more useful than closed models to attackers by removing safety tuning and adding gain-of-function fine-tuning
* Attackers are unlikely to rely heavily on closed models where they'll be monitored and blocked by dedicated teams
* All this makes it obvious that frontier cybersecurity capabilities should be widely available in closed models, with monitoring, abuse detection, and rapid response. Let defenders use the best tools and give them an unfair advantage.
* We should be more aggressive in releasing open weights models too, though, because it's very risky for American labs to abandon frontier open-weight market share, as they are currently doing.
* Imagine a world in which 80% of AI inference in liberal democracies is done with models under the indirect control of the PRC (or imagine by analogy, if Windows was opaque and controlled by the PRC).
* Imagine these models are executing shell commands on all of our production servers
* American labs releasing stronger open-weight models can of course give attackers more capability in the shadows. But the supply chain risk of PRC-controlled models executing shell commands on our societal IT infrastructure dramatically outweighs the risk of attacker adoption.
* Besides, stopping capability diffusion just clearly won't work and would require a level of coordination and cooperation between the US and China that hasn't worked on Taiwan, Iran, or climate change
* Here's what we should actually do: the AI security safety community should pivot towards diffusing American closed and open weights models and competing in cyberconflict via defensive capability operationalization.
* We should focus on being the absolute best at using AI to burn down the security tech debt that lets attackers breach most networks: exposed admin portals, no MFA, stale known-vulnerable software, overprivileged identities, flat networks, broken logging.
* We should also be using frontier capabilities to find and fix more bugs faster than attackers. Restriction is a losing battle. We should instead shape diffusion to support good cybersecurity outcomes
* Also: the sky is not falling! It's true attackers are using AI for reconnaissance, phishing, coding help, translation, fake content, and operational efficiency.
* But we have not seen the huge discontinuity or crisis that restrictionists imply should already be here.
* Google/Anthropic/OpenAI/MSFT's threat-intelligence work and NCSC's assessment all point to AI mostly uplifting existing tactics so far, especially recon and social engineering, while defense also benefits.
* We need to take a breath. And compete on a long-term strategy that embraces reality; capability diffusion will continue to happen. We will win by better diffusing and operationalizing AI cyber capabilities and shaping diffusion to give cyber defenders the upper hand
Lee Chagolla-Christensen retweeted
First blog post in a mini series where I look at "disposable tooling". This post shares what I have found to be useful when 1-shot'ing LLM generated Stage-0 agents for Mythic. specterops.io/blog/2026/06/2…





























