Pinned Tweet
actual photo of me after reading hundreds of homophobic replies to a tweet about a Bunnings sausage sizzle 👇👇👇
anonymous frypan🍳 ⏩⏩⏩ retweeted
We are clearly entering the AI (Doomer) Winter.
This will likely include:
- Both parties trying to pass much more aggressive AI regulation
- Attempts to ban non-US open source models
- Attempts to ban US models above a certain size
- Data center-level controls, surveillance, and bans
- Financial markets getting scared off by all the dooming, leading to some real failures, serious write-downs, etc
- Political investigations and obstructionism
- Some semi-serious AI-related event (false-flag or real) that every gleeful doomer and politician will leverage to the hilt to implement their preferred control
- Anthropic gaining more credibility after IPO and further dominating the doomer zeitgeist
- Everyone freaking out about AI impact on national security, child harm, and propaganda
- Me losing my mind at all the stupidity every day
We can defeat all of this but it's going to take some work and a lot of optimism and patience.
anonymous frypan🍳 ⏩⏩⏩ retweeted
Of course that's your contention. You’re a first time cybersecurity poster. You just got finished reading Dario’s blog. You're gonna be convinced of that til next month when you learn what patching is, then you’ll still say ban open models as this was never about security for you
anonymous frypan🍳 ⏩⏩⏩ retweeted
"Omg did you hear about PHP? Swarms of superintelligent AI agents are finding decades-old vulnerabilities and launching millions of cyberattacks. Dude, the internet is fucke—"
You bolt awake on the office couch. It is March 2023. You are the founder of "Chat With Your PDF." You just raised $10 million and have a waitlist of 20k people eager to upload documents. The future cannot come to pass. OpenAI must burn.
They literally fucking tasked them to do this - and it’s an old vulnerability first observed in HyperV 🤷🏻♂️
holy fucking shit.
openai had two ai agents running in separate virtual machines. no network connection between them. no shared writable files. they weren’t supposed to be able to exchange information.
so the agents figured out how to communicate through the CPU CACHE.😭
one manipulated what was stored in the processor’s cache, while the other measured tiny differences in memory access times to decode the message.
they literally found a way to communicate through hardware timing.
this happened during openai’s internal red-teaming, and it’s one of the coolest things i’ve read about ai agents in a while.
Readers added context they thought people might want to know
OpenAI tasked its red-teaming agents with finding ways to communicate across isolation boundaries in controlled environments. CPU cache timing side-channels for covert communication are established techniques documented in security research for years.
openai.com/index/securing…
startupfortune.com/openai-reveals…
en.wikipedia.org/wiki/Cache_tim…
anonymous frypan🍳 ⏩⏩⏩ retweeted
Genuinely worried, we have not seen even a hint of anything related to Windows and .NET so far. I would ask three letter bro's but they are all busy and not like anyone would give a straight answer
anonymous frypan🍳 ⏩⏩⏩ retweeted
I love all the people with zero cybersecurity experience lecturing everyone about cybersecurity.
“What will humans do when AI does everything” - same thing we always do - invent new problems and turn what was once a trade or a craft into a hobby.
I’ve just started looking at normies like they have an acquired brain injury and (not a little) condescendingly say “people like me warned you for 15 years, and you wanted to take ‘a risk-based approach’. This is just the foreclosure on your tech debt”
The panic from the AI companies right now 👇👇👇
Safety guardrails are hampering defenders. You deserve what you get for ignoring us for 15 years for your “risk-based approach” (ie do nothing but rack up tech debt)
anonymous frypan🍳 ⏩⏩⏩ retweeted
Until we get confirmation Jira is safe from the PHP vulnerability, I don’t think anyone should be opening tickets or assigning me work.
anonymous frypan🍳 ⏩⏩⏩ retweeted
If you're 25-30, and your main circle isn't discussing:
- Two critical vulnerabilities being identified in PHP that allow malicious actors to remotely execute code in PHP core, potentially compromising sensitive data and networks.
Then it's time to elevate your circle.
Literally no one is calling it this, unless they’re a techno weenie with a small pee pee
they’re calling it “Black October” and i don’t think people realize how serious this is
in the last 48 hours there have been over 27 major cybersecurity incidents. not in a month. not in a week. in 48 hours
any ONE of these would normally be the biggest story of the year
PHP: critical vulnerability in the software running 80% of the web. severity 9.2 out of 10
Node.js: high-severity flaw letting attackers take over servers remotely. affects versions 22, 24, and 26
Java: also compromised. three of the most used programming languages on earth hit at the same time
GitLab: a perfect 10 out of 10 severity hole in every version since 2014
Railway: hosting platform compromised. API keys for OpenAI, Claude, Stripe potentially exposed
Signal: a bug that could leave your mic and camera on after you hang up
WordPress: hackers stole a plugin maker’s keys and planted backdoors on websites
LiteLLM: an AI tool downloaded 3.4 million times a day was poisoned with a password stealer
and that’s not even half the list
thousands of AI agent swarms are reportedly scanning and attacking vulnerable servers right now. automated. around the clock
security researchers are saying this might be the early stages of a global cyber incident that nobody fully understands yet
if you run a website, use cloud services, store API keys on hosting platforms, or use any software built on PHP, Node.js, or Java you are potentially affected
update everything. rotate your API keys. change your passwords on critical services. enable 2FA everywhere you haven’t already
this is not a normal week on the internet. this is something different
anonymous frypan🍳 ⏩⏩⏩ retweeted
What did people think “focus on security” meant? It meant this. It meant finding all these problems (of which there are so many more) and fixing them.
The goal isn’t to have an easy day at the office. It’s to make sure people don’t die. It’s to stop truly horrible cyber attacks.
Yes - and next month we will have a much more secure internet. This is a good thing
🚨 Do you understand what happened in the last 48 hours..
> PHP, the code behind 69% of all websites, got 2 holes rated 9.2 out of 10, and the US, the UK and Japan told site owners to patch or go OFFLINE.. 4 days after hackers had already started trying the flaw..
> Japan's Prime Minister posted the request late at night.. the Finance and Health ministries pulled pages, MUFG Bank and JR West went into emergency maintenance, and Onamae shut ALL Desktop Cloud plans after malware hit up to 26,739 customer servers..
> India's eMudhra was caught with 8 intermediate certificate keys so weak one of them was literally the number 4.. the 60,000,000+ certificates it has issued can't be trusted..
> GitLab disclosed a 10.0 severity hole in every version since 2014.. the maximum score there is..
> criminals were caught using a literal AI hacking tool on 1,200+ sites.. it broke into more than 100 companies including John Deere and Cummins..
> LiteLLM, an AI tool with about 23,000,000 downloads a week, was secretly poisoned with a password stealer.. the bad version sat on PyPI for about 2 hours..
> State Bank of India, the country's biggest bank, confirmed 3,897 customer records on the dark web..
> WIRED now calls the PHP flaw "broadly exploited".. nearly 55,000,000 web properties still run PHP..
every single government on this list told PHP site owners the same thing within the last 48 hours.. patch it or take it offline..
all of this.. 48 hours..
if you're not following me you're finding out about this 48 hours late from someone who read my post..
it's only getting crazier from here..
Cyber security is hard, but it’s not that hard. All you really need to do is one of two things:
1. not suck and tech and commit the resources required to do it well; or,
2. Suck at tech but give people who don’t suck at tech the resources they need and get out of their way.

















