zkao (@zkaol) header
zkao (@zkaol) profile picture

https://nitter.gq/t.co/wj8tr1UDuy - the most effective cryptography-focused AI vulnerability scanner

New York
Joined June 2026
Photo by zkao (@zkaol)Photo by zkao (@zkaol)Photo by zkao (@zkaol)Photo by zkao (@zkaol)Photo by zkao (@zkaol)Photo by zkao (@zkaol)Photo by zkao (@zkaol)Photo by zkao (@zkaol)Photo by zkao (@zkaol)Photo by zkao (@zkaol)
Pinned Tweet
a sneak peek into our next update v3.1.0
2
4
318
Today, we're introducing our next big feature in zkao: Usage Resets /jk
2
8
674
what if...
2
1
5
1,217
Attackers don't wait for your next audit anymore. AI bug hunters can read your code every day of the year. Most teams get a security review once or twice a year. That gap is the problem. 馃У
2
4
5
462
Same bug, same attackers. This time it never ships. zkao catches it in the pull request, then keeps checking the branch every day after.
1
13
Attackers run their tools 24/7. Your security can too. Set a monthly budget, pause anytime, and watch the plan move forward. zkao.io/continuous-security
10
What powers zkao? How is it different from running a model over your code? What does an audit cost? A thread on how we approach AI security auditing, what you鈥檙e paying for, and where the limits are. 馃У
1
3
20
1,294
It鈥檚 not over yet! Welcome 0x31 zk.golf
1
2
21
1,520
BTW most of the supply-chain, weak-key, and cryptography bugs that were found this week would have been found in one or two zkao.io scans. And it would have cost you around ~$5k. There's no reason to freak out about bad guys finding all the bugs in your software, you have access to the same tools!
3
2
23
1,207
STOP SENDING US THIS TWEET
cybersecurity startups trying to raise funding right now
1
3
270
how zkao started :)
Big things have small beginnings... the origin story behind zkao.io
1
6
889
next week...
1
2
242
Big things have small beginnings... the origin story behind zkao.io
1
1
5
972