Pinned Tweet
Using AI agents a lot?
Worried about your data getting leaked?
Check this out: breachclaw.ai/
🦞🦞🦞🦞🦞🦞
I recently jumped on the @InfoSecCampus podcast to talk about my unconventional lifestyle as a digital nomad and about @BreachClaw, my AI agent data leak detection tool.
You can listen to the podcast here: lnkd.in/gPrEPugP
Or check out BreachClaw here: breachclaw.ai
Thank you @s4n7h0 for having me!
16
BreachClaw retweeted
As expected AI API keys will become a hot commodity in the future.
Already sought after on the dark web.
Only one of the reasons I built @BreachClaw.
It's for individual users only but should it monitor domains too?
Let me know in the comments.
gnom gnom 🙃
"You can run OpenClaw inside your company now." Annoucing our work with @Microsoft to bring OpenClaw to the Microsoft and Windows ecosystems. Claws now work securly in the enterprise.
1
65
How does the new secret lookup functionality work?
it hashes the secret in the frontend and then sends the hashed value, nothing gets stored anywhere.
For the paranoid ones, you can alternatively compute the hash on your laptop if you don't trust the frontend.
48
BreachClaw retweeted
I have addressed one of the major limitations of @BreachClaw that was on the roadmap for a while.
The issue being, it is often hard to link a leaked secret to an email address.
Making email lookups not a bulletproof way to check for breaches.
So I've implemented a new functionality where you can search for secrets directly. This is a use case for people who suspect they had a leak and want 100% confirmation.
How it works: it hashes the secret in the frontend and then sends the hashed value, nothing gets stored anywhere.
For the paranoid ones, you can alternatively compute the hash on your laptop and just submit the hash if you don't trust the BreachClaw frontend.
Hope you find this useful. Keen to hear your thoughts.
🦞 🔒️
🚨Feature alert - If you're suspecting that one of your AI agents has leaked one of your secrets, you can now directly check for that specific secret.
1
26






