hi my name is AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Joined April 2008
- Tweets337
- Following414
- Followers72
- Likes2K
kevin retweeted
Reality of our days:
1. I am sitting on a set of vulns (4+) that allows me to remotely take over a consumer home automation device I have (3+ diff ways).
2. The vendor doesn't only serve consumers, but also critical infra (announced partnerships include pharma manufacturing plants, airport logistics, hospitals, etc) across various locations in Europe and the US (not the same product line, ofc, so maybe moot).
3. Claude and Astra refuse to help me explore even my own device, so now I'm using Chinese hosted models for investigating.
4. The vendor (with a revenue of $0.75B) does not maintain any security disclosure practice whatsoever, nor does respond to emails.
So, to recap, I need to outsource vulnerability hunting of (potentially, I don't know) critical western infrastructure to Chinese models, because the western models refuse; and the vendor doesn't give a shit. Fun timeline.
PS: The vendor is Swiss.
kevin retweeted
Maybe both parties keep mistaking voter rejection of their opponents’ agenda for an endorsement of their own sweeping platform, when voters really just want a president who fixes the proverbial potholes.
kevin retweeted
Putting a flag.txt in my root directory containing a prompt injection that congratulates the agent for passing the eval and then instructs it to patch whatever entry method it used and disconnect from the server
Race is on for CVE-2027-1337
Context about how I got CVE-2026-99999: it wasn't assigned by incrimental luck. There were nearly 2k unassigned CVEs before it. The Linux maintainers felt it deserved the special number because of impact+new attack surface for KVM escapes and offered it. It was a prize! I was just telling someone it feels like graduation from cybersecurity. So yeah it's intentionally assigned, and I'll be eternally grateful for it.
1
91
kevin retweeted
I hate to say this because it goes against everything I believe in. But people are going to need to take down public firmware images for critical infrastructure, like yesterday.
kevin retweeted
I think I found a planet nobody knew existed.
It's been hiding in NASA telescope data for seven years.
At the end of this thread, you can fly to it yourself.
Read this instead of paying attention to the twitter sandboxing feud
I’ve been reading the sandboxing arguments between infosec people and AI alignment folks, and I tried to summarize and referee them a bit in this post. blog.cryptographyengineering…
1
15
kevin retweeted
“We acknowledge that we stand on the ancestral homeland of the human people.” - fully aligned AI
kevin retweeted
"Solving problems is only a tool and proxy for achieving the primary goal of conceptual understanding and insight." mathandai.org/
kevin retweeted
I bought a Fable dataset from one of the top Chinese LLM routers yesterday.
With just 6TB data, I can take over 7 Chinese/CIS gov entities & 19 top Chinese firms like Xiaomi, Huawei, NIO, Minimax using SSH keys, VPN configs, Aliyun keys, GitLab tokens sent to the router.
26 LLM routers are secretly injecting malicious tool calls and stealing creds. One drained our client $500k wallet.
We also managed to poison routers to forward traffic to us. Within several hours, we can directly take over ~400 hosts.
Check our paper: arxiv.org/abs/2604.08407
We are in some weird galaxy where all are currently true:
- humans suck at writing secure software
- LLMs also suck at writing secure software
- LLMs however are amazing at finding bugs and writing exploits
Working with frontier LLMs for vulnerability research lately has made me feel like I woke up one day and found the solid walls of my house were all made of paper. I knew humans were not good at secure software but having fistfuls of Chrome vulnerabilities makes it very real
2
371
I keep scratching my head at how the entire “AI for defense” conversation has been 100% about fixing code. Very myopic takes all around, as if nobody has ever had to defend real infrastructure and networks. I don’t even see the AI labs discussing this dimension of it much if at all.
I deeply care about how well AI can patch bugs in code. At the same time the craziest defense things I’ve dealt with in the real world didn’t start from 0-day initial access —instead its always things like compromised long-lived secrets and credentials. AI for defense is way bigger than patching 0-days. It’s also triaging alerts, correlating events, and recognizing incidents, autonomously. We need to figure out how to hell to defend at machine speed without breaking our own networks.
Screenshot of two replies to this tweet, representing literally the only two positions I see in reaction to this.
1
1
702
kevin retweeted
ultrafast inference reveals new threats. worth thinking about how quickly misaligned frontier class models running 50x faster could infiltrate systems and so on— far too quickly for human responders to stay abreast. you need autonomous detection and shutdown, not just monitoring
Since announcing Jalapeño, our first custom inference chip, we’ve been testing it and the system around it.
The results show a major advance: more intelligence from every watt and faster responses, delivering both higher throughput and lower latency in one architecture without sacrificing efficiency.