
building and breaking @SpecterOps | opinions are my own
/
Joined August 2021
- Tweets2.8K
- Following417
- Followers7K
- Likes25K
Pinned Tweet
‼️new tradecraft release: I am publishing Blacklight with @SpecterOps, an open-source toolkit and blog for mapping and analyzing the local attack surface created by AI agents on endpoints
local agents are becoming apart of everyday workflows and they leave behind a growing set of endpoint artifacts: session history, configuration, auth material, rules, and other evidence that can matter during an assessment
Blacklight started with one question: what can we learn about AI agent usage from the endpoint itself?
it grew into a two-stage toolkit for safely scouting those artifacts, selectively collecting what matters, and reconstructing agent activity for deeper security analysis
would teams for people to try it, break it, and send feedback
links to blog and GitHub below ↓
Blacklight 0.2.5:
- Scout now maps @Muse Code, Kiro CLI, @opencode harness, @cognition's Devin CLI, and Strands Agents
- Session Analysis now reads Grok chat history
- Added progress bar & performance improvements on local session analysis
Full changelog in replies; new features coming soon
the @WHOOP app & band has been the worst user experience I have had in a while, this should not be the case for a ~$200/yr product
syncing takes forever, the app takes around 5 mins to be useable if syncing from data 12 hours ago? this stuff should be computed in the background and still allow the user to start an activity
will definitely be switching once this year is if no changes happen
very honored to have @letsdatascience feature Blacklight in their latest exclusive! I answer some basic questions about the project and how defenders can use Blacklight to protect their orgs from this new AI surface, take a look at the repo and article in replies!
article: letsdatascience.com/news/spe…
repo: github.com/SpecterOps/Blackl…
⭐️ "you need to assume X can eventually be broken and build the surrounding system around that assumption."
it’s not impossible, but it’s also not easy. it requires a lot of work.
existing tech like firecracker has held up very well against current models, including gpt-6/mythos level models. completely blocking egress is relatively straightforward. things get much harder when the task requires constrained internet access, which is what led to most openai sanboc bypasses, but even then, it’s possible.
BUT, the mistake would be assuming firecracker will also hold against something like gpt-7 or gpt-8, its literally the kind of assumption is how you end up with much more catastrophic hugging face style incidents.
you need to assume firecracker can eventually be broken and build the surrounding system around that assumption. also, you need to assume a lot of controls we thought would hold will fail and build around it. and, lots of sandbox escape auditing with models and humans before you do large scale training or evals.
it is never easy, if security or developer could anticipate every vulnerability beforehand and design things, security would be a solved problem, and there is a reason its not
Gavin K retweeted
A quick article showing how the Jev OPSEC ranker works, and looking at how Jev can be used for identifying potentially sensitive file paths and content at speed.
New Release Havoc Professional 0.8: Leviathan 🩸
- Introducing Kaine User-Defined C2
- Expanded Linux post-ex capabilities
- Refactored port forwarding and sleep masking
- Enhanced .NET/PowerSafe execution
- In-Memory PE Execution and BOF-PE support
- HTTP/s Server Name Indication (SNI) Spoofing
- License Updates / Air-gapped licensing
- Havoc client UI overhaul & cross-platform support
Release Link Below🔗
Gavin K retweeted
A fresh new look is coming to Ghostwriter. 👻
v7.3.0 brings a redesigned dashboard, new engagement bar, customizable sidebar, accessibility improvements, and a UI refresh across the application.
@cmaddalena unpacks what’s new. 👇 ghst.ly/46xaley
this is amazing @forefy! nice work, I am going to use this to set up some workflows i've been wanted to test out... send multiple http requests 😏
Replying to @atomiczsec @forefy
this is the burp extension:
github.com/forefy/reburp
Incredible read. Dozens of headline stories packed into a single report.
It shows how Claude is being used not just for hacking, but to build missile guidance & drone swarms, biological research, build large scale surveillance systems, run influence ops, etc
Even the model theft section is wild. PRC, PLA, & Russian defense agency unknowingly sent sensitive material (even live creds) to Anthropic because Moonshot & DeepSeek were relaying customer traffic into Claude! 😂
This part of Anthropic is far more mature than I think a lot of people give them credit for. I hope they keep publishing these. I don’t think most people are ready for the immediate future.
We're publishing our most detailed threat intelligence report to date.
It covers how people tried to misuse Claude—for cyberattacks, influence operations, surveillance, biology, and building weapons—and how we found and stopped them.
We disrupted every operation in the report, and used the lessons from them to strengthen our safeguards. Where appropriate, we also shared what we found with authorities and other AI companies.
These cases are not typical: we’re highlighting some of the most sophisticated misuse we’ve seen. But they’re especially important to discuss, because they show us where AI misuse is headed, where our safeguards work, and where they need to improve.
We’re publishing this report so others can spot the same activity on their own platforms, and so we can give the public a clearer view of how emerging threats develop.
Read the report: anthropic.com/threat-intelli…

















