ex-twitterSRE "I have approximate knowledge of many things"

Joined July 2009
Billy Becker retweeted
+ "you know what i'd really like?" - "tell me" + "a website" - "...we can do a website" + "a real website, not some claude generated neon slop, a real website" - "i'll make you a very good traditional handmade website, one that is built with dozens of snippets from stackoverflow"
131
4,290
105
51,789
616,522
Billy Becker retweeted
We are launching a PHP Capture the Flag challenge integrated with our Bug Bounty program to test our WAF protections. Security researchers are invited to bypass our defenses and capture the flag to help make the Internet safer. cfl.re/4iqHaQ1
23
76
20
504
78,982
Billy Becker retweeted
No fucking way ITS 4 AGAIN DIFFERENT BUG
Announcing 3 Critical vulns for hundreds of millions of IoT, Firewalls, OT, and Military devices including: Palo Alto Networks, Comcast, D-Link, HP, Canon, Honeywell, GE, Oracle, Siemens, Rockwell, Digi, Lockheed Martin, Boeing... The vulns are with GoAhead Web Server which is a backend library used by these devices. There's a patch available from GoAhead but that doesn't mean there's a patch available for the devices yet -- that's up to the manufacturer. - TLS traffic over DHE ciphers have a 1-byte secret, "04", meaning anyone can decrypt connections to these devices and steal login credentials and session tokens if the client negotiated with DHE ciphers like the latest TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256, which is extremely likely. - LibreSSL mTLS has been completely bypassed, meaning anyone can connect over mTLS. If you have one of these devices listening on the internet and are expecting mTLS to protect it from attackers, take it offline or patch asap. - OpenSSL Certificate Revocation Lists (CRLs) are not enforced, meaning if a user device is stolen or compromised, and you revoke that mTLS cert, nothing actually happens. There are a lot of other attacks this can be used for. These are critical because these types of devices run our world. Water systems, electricity, military, firewalls, critical infrastructure. foxio.io/blog/choose-your-ba…
125
495
80
5,146
191,575
I found a new RCE bug in PHP, missed by previous auditing teams. It’s unpatched in PHP v8.5.12
73
225
48
2,172
211,039
Billy Becker retweeted
if you have a qwen3.5 4b around, please try steering neurons L14 N8949 +1 and L13 N7956 -1 now you have evil qwen recipe: dose × median(‖resid‖ leaving layer L, tokens 1:) / ‖W_down[:, n]‖` at the down_proj at every input
495
1,295
739
22,012
4,303,084
Billy Becker retweeted
Someone has created a vulnerable PHP website, loaded it with a Bitcoin wallet, and challenged the Internet to hack into it and they can keep the Bitcoin. It has a running timer to show if the PHP exploitability was over-hyped. stealmybitcoin.com/
179
459
145
7,105
2,838,703
I owe you an apology, George. I wasn’t really familiar with your game.
Send me your favorite Star Wars / Anakin edits; this is mine
115
3,163
27
60,368
1,308,262
The general public should be made to play XCOM until they understand.
This is like the "if you hadn't had breakfast this morning" test. Remember when Nate Silver predicted Hillary Clinton beating Trump in the 2016 election at 71% confidence--then everyone rubbished him, because Trump won? Then, of course, someone looked at all his ~70% predictions and found that they were right about 70% of the time, i.e. 70% the predictions were rather well calibrated.
1
1
14
352
Billy Becker retweeted
A very clear eyed picture of what’s coming. You will need a software factory for defense, not just internal productivity.
Just spent the last 7 days on the front lines of the vulnpocalypse fending off an active cyber attack on one of our products. Some thoughts: - Software factories are going to be required equipment for everyone. There’s just no way to keep up with the pace of highly automated adversaries without one. - We were lucky because we had spent the last few months getting our software factory running well. It is nice to have for product development but proved to be absolutely essential this week. - At the minimum you need to have a coding server in the cloud pre-provisioned with read only access to all your logs and all the services you depend on for observability. With that in place you are a prompt away from reasonably good situational awareness, ongoing monitoring with loops, and ability for coding agents to validate fixes against your actual, observed attack patterns. - Shared coding server also unlocks multiplayer incident response where everyone can see every session and jump in as needed. Sharing session links that can be forked is much higher bandwidth than re-explaining things. - You don’t need to be Ramp/Stripe/Uber scale to have a working software factory in the cloud. We are a team of 3. Ours is built with an @opencode server (thanks @thdxr!), a forked version of compound engineering optimized for automated workflows (thanks @kieranklaassen!) and a multiplayer agent in slack that handles crons (we have our own harness but pick your favorite here). - To get our software factory up and running well, we had to stop all new product development for ~6 weeks and just focus on getting the validation systems working that enabled us to reliably shipping PR without human code review. This felt very painful in the moment but was totally worth the eventual speedup in velocity. - KYC for @AnthropicAI & @OpenAI cyber programs is now easy and quick (at least for defensive access), but a day felt like a lifetime this week. Submit your app now before you really need it. - Getting Mythos access unlocked a deeper level of analysis that helped us shift from reactive mitigation to proactive patching. Wish we had done this a few weeks earlier. Get started now!
1
20
3
426
44,236
Billy Becker retweeted
It is never okay to circumvent proper established coordination efforts for security disclosures. It causes harm for others, and while it does give the person some short term gratification, it burns more bridges than it will ever open.
‼️ 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.
11
8
1
64
3,966
Billy Becker retweeted
For those wondering: it's a classic "proof of discovery". You hash the write-up of an undisclosed bug, post the hash and reveal the text after the fix. Anyone can then verify you had it first. After the past week… k8s admins, get some rest and hydrate while can 👀
9
57
2
2,815
151,322
Star Wars Mandalorian, Luke Skywalkers entrance but with the Force Theme 🔥🔥🔥🔥🔥
164
1,102
82
11,048
421,641
Billy Becker retweeted
No one in the history of media knew the interior workings of a young boy’s brain better than Bill Watterson
117
1,326
81
16,650
380,586
Billy Becker retweeted
This is probably the wildest Cybersecurity Awareness Month campaign ive ever seen.
17
81
3
548
12,601
Billy Becker retweeted
Right? Like, I feel like we are all very aware atm.
This is probably the wildest Cybersecurity Awareness Month campaign ive ever seen.
1
7
274
Billy Becker retweeted
The money for nothing rogue one edit just makes me want to run through a wall probably the best SW edit of all time
211
2,483
272
25,561
1,840,850
Too soon.
Cloudflare previous CTO sent this into our bug bounty. We are investigating.
15
25
3
1,448
50,436
Billy Becker retweeted
Set session.upload_progress.enabled=0 till next PHP release to block an unlikely RCE vector (CVE-2026-115560). Already recommended for CVE-2026-109619 Wed, keep disabled. Only apps with non-default serialize_handler switching it to "php" at runtime can be affected. #php #phpc
50
902
151
2,848
406,736
Billy Becker retweeted
I'm tired boss
176
904
430
8,789
2,269,875
Two classes extremely bad cyber vulnerabilities disclosed in the last 24 hours. The first potentially impacts everyone online. The second impacts nearly everyone running a server. tl;dr: Everyone should upgrade their OS and Browser as soon as possible. If you run a server you should upgrade PHP (or ensure it’s removed if you’re not using it) as soon as possible. The first class of vulnerabilities is a set of root TLS certificates that were discovered to have a trivial private key. Literally the number 4. These roots were controlled by #eMudhra. The problem is that with that an attacker could create a certificate and, if they could get in the traffic flow, intercept traffic to any site or service. The solution is to stop trusting certificates issued by these vulnerable roots. Upgrading your browser and OS is the fastest way for most Internet users to do this. The second class of vulnerabilities doesn’t apply to most consumers directly, but does apply to most anyone running a server. These vulnerabilities have been dubbed #php2shell. PHP is one of the most widely used web programming languages. It’s estimated 70% of websites run on PHP. These vulnerabilities allow an attacker to send a crafted set of queries to a server running PHP and potentially take over the server. From there they could potentially read, modify, delete, or repurpose anything on the server. The solution is to upgrade PHP to the latest version ASAP. Even if you’re not using PHP for your web development, it’s often included by default. So make sure it is either upgraded or fully removed. @Cloudflare received advanced warning of both of these classes of vulnerabilities. We’ve ensured that where we act as a proxy we are no longer trusting the vulnerable roots. We are also reviewing certificate transparency (CT) logs for any sign the vulnerability was exploited before its disclosure. We have not found any evidence but CT logs are not perfect and a sophisticated attacker who knew about the weakness could have exploited it without a new certificate being logged. For the PHP vulnerabilities, we have deployed mitigations available for all customers for free. Because of the complexity of the vulnerabilities and number of ways it can be exploited, we also released new WAF capabilities that are unique in the industry to catch the exploit based on the response. These too are available for every Cloudflare customer for free. Even if you are taking advantage of Cloudflare’s protection, it is important to upgrade your OS, browsers, and PHP installations as soon as possible. We can provide a strong bandaid, but the best protection is to fix the underlying problem. If you’re interested in learning more, you can read our blogs: Vulnerable roots: blog.cloudflare.com/emudhra-… PHP vulnerabilities: blog.cloudflare.com/php-vuln…
86
764
96
4,553
672,051