https://xitter.cf/t.co/7kM1zqC9tx

United States
Joined March 2026
Scott Arciszewski retweeted
Lessons for all the new researchers: 1. Write your own posts. Everyone knows what slop looks like. 2. Don't buy a domain name for a bug. It's 2026. 3. Learn the difference between bugs and architecture risks 4. Get friends. They should tell you your bad ideas suck
‼️ Researcher Erica Windisch skipped coordinated vulnerability disclosure and published 11 unpatched Tailscale flaws. In her lab, Tailscale SSH race conditions let one hacked device get root on other servers and add a rogue node.
7
21
5
231
12,328
Scott Arciszewski retweeted
Exploit development is one of the most frustrating components of computer security, not because it’s bad (I am in awe of people who can do it) but because too many vendors make working exploits a requirement for patching things.
15
13
99
7,333
Scott Arciszewski retweeted
Yep. Because you can't just prompt "find me all the vulnerabilties". Maybe in awhile but we're nowhere near that now. Skilled researchers, custom harnesses, and other techniques are changing the bug depth game, in addition to bringing down the cost.
wait, PHP was actually scanned by Anthropic’s Claude Mythos earlier this year. they also had access to OpenAI’s Daybreak Red for validating exploits. the PHP Foundation revealed this JUST yesterday. keeping frontier cyber models in the hands of a selected few doesn’t seem to be working well for the internet. thephp.foundation/blog/2026/…
3
11
2
58
7,920
Scott Arciszewski retweeted
There was no payout because PHP2Shell came out of Patch the Planet (trailofbits.com/patch-the-pl…), a pro bono initiative where we (Trail of Bits, OpenAI, Calif and HackerOne) use AI to audit and secure open source software for free. If we were paid for every bug from PTP we’d all be driving Lambos by now.
My non-hacking buddy asked me how much the person who found the php2shell made. Then he made a good observation: Hack a small company, make a little. Hack a big company, make a lot. Hack 70% of the world, make nothing.
2
6
53
4,457
Scott Arciszewski retweeted
as a person who lives with a computer architect, 'yes? how did you think we made the computers so fast?'
Over the past several months, we have substantially hardened the security of our research training environment. We’ve removed live internet access for all frontier models during training and built an offline world for them to use instead—a cached version of the web where they can still learn to browse, search, and use applications. On September 20, after a model exploited a DNS misconfiguration to find a way outside of this offline world, we paused frontier training to strengthen containment further. We assembled teams of agents, powered by our most cyber-capable models, and tasked them with finding weaknesses in our research environments. While they found no route to the internet they could easily exploit while concealing their activity from our monitors, they did find zero-day vulnerabilities, virtual machine escapes, and hardware side-channels for communication between agents. We used their discoveries to further strengthen our defenses and contribute fixes to open-source software. After strengthening our containment architecture, we resumed our frontier RL training and inference on October 1. We’ve reserved substantial compute for continuous red-teaming, and made high-compute red-teaming part of the safety cases we use to decide whether frontier training and evaluation can proceed securely. openai.com/index/securing-ou…
2
2
14
778
Scott Arciszewski retweeted
We’re still testing how exploitable the Node.js/Brotli bug is, but we’ve found that it’s surprisingly hard to tell whether you’re even affected. So @ToBScottA built a scanner that finds hidden copies of the decoder, even in stripped binaries. github.com/trailofbits/brotl…
14
69
1
305
21,012
Scott Arciszewski retweeted
Run, do not walk, from any cloud provider who is throwing public shade at Railway (or any other provider). The better your security team is, the more internal pressure you have not to mouth off about security in Q4 2026.
10
41
6
532
18,945
Scott Arciszewski retweeted
Signing up for Daybreak is easy, and essential for anyone that maintains software for others. Get it here: help.openai.com/en/articles/… xitter.cf/thsottiaux/status/2113…
Day 17/ Bet you thought we forgot, but no, it’s reset day today. Also good time to remind you to get Daybreak Blue access, it only takes 15 mins and you don’t want to have to do it in the middle of an incident.
8
2
43
5,703
Scott Arciszewski retweeted
Replying to @dguido @trailofbits
To be clear, our exploit does not require an LFI vulnerability in the target. It gets a shell on unmodified MediaWiki.
1
3
1
35
7,070
Scott Arciszewski retweeted
Will Tan built it in 1 day with Codex, drawing on ~10 years of system security and vulnerability research (4 @trailofbits). AI accelerates exploit development. Knowing how to turn a bug into a shell still takes expertise. AI makes that expertise more productive.
1
3
56
9,722
Scott Arciszewski retweeted
Re: the widely circulated blog claiming the PHP bugs aren't easily exploitable: @trailofbits has a working exploit that gets a shell on an unmodified MediaWiki installation. eliastaylor.com/noexploit/
14
74
7
428
103,500
Scott Arciszewski retweeted
We got a PHP exploit working against MediaWiki, but getting freed memory reused just right takes some tinkering under normal traffic. LLMs struggle here without an expert's guidance, which may help explain the attempts but no confirmed successes.
Re: the widely circulated blog claiming the PHP bugs aren't easily exploitable: @trailofbits has a working exploit that gets a shell on an unmodified MediaWiki installation. eliastaylor.com/noexploit/
4
19
3
153
12,796
Scott Arciszewski retweeted
Oh, you aren’t updating your dependencies every hour? Well, too bad, you are vulnerable Oh, you are updating your dependencies every hour? Well, too bad, you are somehow also vulnerable
🚨 JFrog Security Research has identified a supply-chain attack involving malicious code in the LiteLLM 1.107.0 PyPI release. Avoid this version and investigate environments where it was installed or executed. More details will be shared soon in our blog post.
35
231
14
4,059
79,160
Scott Arciszewski retweeted
fulcrumsec.vg/pingcap/ > Four years before we walked in, their own security team had documented that any member of a customer organisation — including a billing-only role — could take over every cluster in that organisation as root Hurts to read. Sorry buds.
2
5
234
Scott Arciszewski retweeted
shut... the ... front... door... was JAVA feeling lonely and wanted to get into the party????? Oracle Security Alert Advisory - CVE-2026-91403 CVS 9.1 oracle.com/security-alerts/a… @uwu_underground
25
253
67
3,371
203,744
Scott Arciszewski retweeted
2
59
1
3,683
111,430
Scott Arciszewski retweeted
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
1,080
8,934
1,652
69,413
4,169,019
Despite everything that's happening this week, there is still good work happening in the security space. I've got exciting stuff to share soon!
1
101
Scott Arciszewski retweeted
Yesterday, rumors started circulating about two unpatched critical-severity bugs in PHP. Within 17 hours, Cloudflare was blocking attacks and Patchstack reported active exploitation. When AI can develop a working exploit in hours, bugs need to be patched just as fast. Each day without a fix carries the risk that an attacker will find and exploit the bug. But it takes time to create a working patch, and PHP's patch was more complex than most. The patch changed 402 files and added more than 11,000 lines, reworking core engine behavior that dozens of extensions depended on. The bug was reported on Aug 11, and fixes were shipped 71 days later. But less than a day after details leaked, systems running PHP were already under attack. Patching needs to keep up with the pace of bug discovery. For the past four months, we’ve worked directly with open-source projects as part of Patch the Planet to understand how AI can expedite patching. Our ongoing research and work show that project-specific documentation, skills, and plugins can be embedded at the repo level to give agents and contributors access to the context maintainers carry in their heads: what counts as a bug, how a fix should look, and what can't break. Our two new open-source plugins, patching-bugs and regression-hunt, are a first step toward a generalized set of tools and guidance for getting a working patch out faster: blog.trailofbits.com/2026/10… PHP’s account of the incident: thephp.foundation/blog/2026/…
5
14
3
86
5,626
Scott Arciszewski retweeted
Coordinated disclosure serves little purpose now. As a product owner, you need to ramp your dev speed to make patches instantaneously after external reports. xitter.cf/halvarflake/status/211…
For the next few months, we are looking at frequent discoveries of long-standing bugs - competent code auditing has gotten cheap and abundant. This carries a few consequences:
3
22
1,087