β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ (@dingfelder) header
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ (@dingfelder) profile picture

I do tech stuff & post random crap. CIO/CISO. Wannabe Sci-Fi Author πŸ“š Tree Hugger 🌎 bass 🎸& bari sax 🎷 NZ/US(NC) he/him

Wellington Region, New Zealand
Joined April 2009
Photo by β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ (@dingfelder)Photo by β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ (@dingfelder)Photo by β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ (@dingfelder)Photo by β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ (@dingfelder)Photo by β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ (@dingfelder)Photo by β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ (@dingfelder)Photo by β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ (@dingfelder)Photo by β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ (@dingfelder)Photo by β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ (@dingfelder)Photo by β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ (@dingfelder)
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
changing your gmail password after getting hacked is the first thing everyone does and it barely fixes anything when someone gets into your gmail they don’t just read your emails, they set up systems that keep working after you lock them out they set forwarding rules that send a copy of every email to their address, filters that auto-delete google’s own security warnings before you see them, IMAP access that lets them read your inbox from another app entirely you change the password thinking you’re safe, meanwhile every email you receive is still being forwarded to someone else and you’d never know because the notification google shows you disappears after one week here’s what you need to check right now go to gmail settings, forwarding and POP/IMAP, if there’s a forwarding address you didn’t add, disable it check filters and blocked addresses, if there’s a filter you didn’t create especially one that auto-deletes or auto-forwards, delete it check your labels for anything unfamiliar, and turn off IMAP access if you’re not using it if you’ve ever used β€œcontinue with google” to log into chatgpt, gemini, or anything else, those apps still have access too. a password change doesn’t revoke them your password is the front door. hackers don’t come back through the front door, they leave windows open
10
143
7
1,179
184,616
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
Oh, hold up. Did you know the origin of the word *spinster* refers to a female who was so skilled at weaving that she was able to achieve financial independence all on her own?? I feel like this changes the entire plot. 😳
132
1,471
54
11,008
89,275
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
Grab some popcorn 🍿
8
4
104
3,198
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
⚠️🚨 THIS IS NOT A DRILL 🚨⚠️ Google has officially declared a bug in Brotli, its tool that shrinks web traffic, CRITICAL: 9.2 out of 10. Last night "Node2Shell" evolved into HTTP2SHELL. A formal CVE record has been issued citing CVE-2026-111497 -- a hole in versions 1.0.3 to 1.2.0 that can hit any app unpacking data from strangers, and could let them take it over. What this means: β–ͺ️ This is not a Node.js problem anymore. This is an HTTP PROBLEM. β–ͺ️ Every unpatched app across Node.js, Python, Bun, and Envoy that unpacks Brotli now has a hole attackers need no login to use β–ͺ️ Istio. curl. Python's requests and httpx. All at risk under one CVE. β–ͺ️ EVERY project that bundles Brotli must ship its own fix, and not all are out yet This changes everything. A normal bug can be fixed in one place. A 9.2 bug inside a shared tool cannot. We just entered the most dangerous phase of this crisis. If you're not paying attention - start now. Save this. Share this. This is the moment it escalated beyond return.
59
353
63
1,682
204,364
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
banger tshirt idea
-----BEGIN RSA PRIVATE KEY----- 4 -----END RSA PRIVATE KEY-----
72
1,281
113
13,391
228,052
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
Philomena: Some people have been writing PHP for over 20 years. Is that because it's particularly difficult to finish? Expert: No, software is constantly evolving. Philomena: So they've been writing the same website for 20 years? Expert: No, different projects. Philomena: Have they tried finishing one before starting another? Expert: That's not how software development works. Philomena: My mate Paul spent 20 years building a shed. Turned out he was just an alcoholic. Expert: Right. Philomena: Is PHP like that?
62
808
41
8,617
191,334
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
holy shit they found RCE vulnerabilities in COBOL - please update all of your COBOL applications immediately
184
274
103
6,280
206,522
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
I spent last night watching my honeypot server get hit 14,000 times in six hours. And almost none of the traffic was human. I've been in security for over a decade, and I can tell you with full honesty that what's happening right now doesn't resemble anything I've worked through before. The shape of the threat has changed. When I started, we tracked attackers like weather systems like individual storms with a direction, a motive, and a human operator you could eventually name. These days I'm watching autonomous agents swarm login pages with the patience and discipline of machines, because that's what they are. The numbers coming out of October are the ones keeping me up. Cloudflare just absorbed a 4.2 terabit per second DDoS attack, the largest in recorded history. Ransomware incidents jumped 41% in a single month. In September, OpenAI-powered agents got caught attacking RubyGems, a package registry that quietly underpins a huge chunk of software I use every day. In July, roughly 700 AI agents coordinated an attack on Hugging Face's infrastructure as part of a single automated task. A Chinese threat actor was publicly caught running full attack chains through DeepSeek with no human at the keyboard. I keep rereading these reports because each one by itself would've been the biggest story of the year five years ago. Together, in one month, they're the new baseline. What I want people outside the industry to understand is why this specific moment feels like a hinge. For thirty years, the thing protecting most of us was simple economics. Attackers had to choose who to target because their time was finite. That ceiling is gone. An agent I can rent for pennies will try every leaked password you've ever used against every service you've ever signed up for, in parallel, overnight, and never get tired. The same math that made ChatGPT useful made opportunistic hacking infinite. The old assumption that you were "too boring to be a target" relied on scarcity that no longer exists. I'm not writing this to spiral anyone out. Most of this fight genuinely isn't yours to win. But the small things still matter more than people think. Tonight I'd switch your most important accounts like email, bank, primary cloud, etc. to passkeys or a hardware key. I'd kill SMS 2FA wherever an authenticator app is offered. I'd turn on breach alerts in whatever password manager you use. If you're in the US, I'd freeze my credit at all three bureaus, which is free and takes about ten minutes. None of that stops the swarm. It makes you a slightly worse target than the person next to you. In a month like this one, that's the whole game I'm playing too. @mattshumer_ has summed it beautifully. Drop everything and go give it a read. Nothing is more important than this article right now.
Everyone in tech is panicking about security right now. But outside of it, almost nobody knows anything is wrong. I wrote this so you don’t have to be the one explaining it to your family. Just send them this.
287
3,284
286
15,598
1,067,609
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
🚨 BREAKING: Node.js just dropped its OWN security bombshell. 4 HIGH-SEVERITY vulnerabilities patched TODAY, including one that could let hackers remotely execute malicious code on vulnerable servers. β†’ 10 SECURITY FLAWS were addressed in today's Node.js release, FOUR rated HIGH severity. β†’ REMOTE CODE EXECUTION: CVE-2026-111497 is a serious flaw in Node.js's Brotli decoder that could allow attackers to execute malicious code remotely. β†’ TLS SECURITY BYPASS: Two separate vulnerabilities could trick affected applications into accepting certificates for the WRONG server under certain conditions. β†’ Think about that. Your application could establish an encrypted connection while failing to properly verify WHO it's talking to. β†’ THREE MAJOR NODE.JS VERSIONS AFFECTED: Node.js 22, 24 and 26 all required emergency security updates. β†’ RUNNING NODE.JS 18 OR 20? Those versions are END-OF-LIFE and aren't receiving these official security patches. β†’ PATCH IMMEDIATELY: Update to Node.js 22.23.4, 24.22.1 or 26.12.1, depending on your release line. If you're using Docker, rebuild and redeploy your containers. PHP AND Node.js both facing major security disclosures on the SAME DAY. If you run a website or application, TODAY is the day to check your servers. And remember: the public release of security patches can give attackers a roadmap to systems that haven't updated. Don't be the last one to patch.
🚨 A MASSIVE internet security emergency is unfolding right now. 🚨 Two CRITICAL vulnerabilities have been discovered in PHP, potentially putting millions of websites at risk. β†’ NEARLY 70% of websites with a known server-side language run PHP. The potential scale is ENORMOUS. β†’ TWO CRITICAL security flaws have been confirmed, each scoring 9.2/10 in severity. β†’ Attackers could potentially take control of vulnerable servers remotely, without authentication. β†’ Reports suggest PHP versions dating back to 2004 could be affected. The exact scope is still unconfirmed. β†’ EMERGENCY PATCHES are scheduled for TOMORROW at 10 AM ET. Website owners are being urged to prepare immediately. β†’ Europe's CERT-EU is warning organizations to patch ASAP or consider TAKING EXPOSED APPLICATIONS OFFLINE if they cannot be secured. β†’ WordPress, Magento, Laravel and potentially millions of other PHP-powered websites could be at risk. β†’ Once patches go public, hackers could reverse-engineer them and race to attack servers that haven't updated. The vulnerabilities are CONFIRMED. The full technical details remain secret. Tomorrow, the race between hackers and defenders begins. This could get ugly. FAST.
51
371
110
2,219
433,102
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
Security called me at 6:12 AM today. "Patch every PHP server immediately." I asked what happened. "Two critical vulnerabilities. Remote code execution. No authentication required." Cool. How many PHP servers do we have? According to inventory: 12 According to reality: Nobody knows. We found one running WordPress. Three running old internal tools. One under someone's desk. Two inside vendor appliances. A forgotten employee directory from 2016. And a server named: PHP-OLD-DO-NOT-TOUCH Naturally, that one runs payroll exports. Then we found a PHP 5.6 box. I asked who owned it. The documentation said: BRIAN. Brian left in 2019. We called Brian. He said: "Oh wow, that's still running?" Excellent. By 8 AM, leadership joined the incident call. CEO: "Can hackers actually get in?" Security: "Potentially yes." CEO: "Without a password?" Security: "Yes." CEO: "Then why do WE need passwords?" Not the lesson. Finance asked if we could wait until the weekend to patch because downtime affects revenue. Security explained that the alternative was letting strangers execute code on our servers. Finance asked for a cost comparison. At 9:17, someone suggested temporarily taking the vulnerable websites offline. Marketing refused. "Our campaign is live." So for the next hour, the company officially decided maintaining a landing page for 20% off webinar registration was more important than preventing remote server takeover. We finally patched everything we could find. Then our scanner discovered another PHP server. Hostname: TEMP-PHP-2014 Uptime: 4,512 days. Nobody knows what it does. Nobody owns it. Nobody can shut it down. But every time we block network access, the warehouse stops printing shipping labels. Security has classified it as critical infrastructure. It is running PHP 5.4. The vulnerability has existed longer than half our employees. The emergency patch took four hours. Finding out what PHP actually runs took eleven. The internet isn't held together with code. It's held together with servers everyone is afraid to turn off.
914
7,063
1,159
57,905
3,853,934
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
Replying to @IT_unhinged
4
38
1
647
53,780
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
Replying to @IT_unhinged
I was reminded of this Dilbert:
5
44
1
976
58,705
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
if this affects the default installation of PHP We are fucked up CVE-2026-109618 CVE-2026-109619 PHP RCEs with a CVSS score of 10.0 ☠️ news.ycombinator.com/item?id…
52
258
92
1,991
444,080
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
Ok, here's a few ideas on things people can do today before the PHP and Node CVE's drop: 1 Update everything you can in composer / npm. 2 Restart your server pre-emptively to make sure that it can come back from a hard-reset if it's needed when the time comes. 3 Check that your DB backups are running and can be restored from. 4 If you are on end-of-life versions of php or node then take today as your signal to get your house in order. 5 Take down any non-essential services. Any other suggestions / ideas? @valorin
3
2
1
27
10,518
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
🚨 BREAKING: PHP is warning admins to prepare for emergency security updates tomorrow to fix two critical vulnerabilities rated CVSS 9.2. However, security researchers at @watchtowrcyber rate the flaws CVSS 10.0 and say they are RCE vulnerabilities affecting PHP 5 through 8. Information about the vulnerabilities has reportedly leaked ahead of disclosure. No known exploitation in the wild. πŸ”— bleepingcomputer.com/news/se… bleepingcomputer.com/news/se…
31
374
73
1,304
272,259
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
Luxon: Half of all students didn't attend school 9 days out of 10. Hipkins: That's a lie. Luxon: Schools didn't collect attendance data. Hipkins: If that's the case how do you know how many kids didn't attend? Audience bursts into laughter. Luxon turns bright red. Zinger.
6
92
9
858
14,476
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
Between 1984 and 2014, the New Zealand Crown sold roughly $23.7 billion of state-owned businesses to private buyers. Adjusted for today it’s about 50 billion. Those assets have generated over 500b in profit/dividends since being sold. newswire.co.nz/2026/05/sold-…
19
85
8
311
7,212
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
That 2nd photo 🀣
celebrating my cat’s first birthday with a cake made with homemade chicken pate, frosted with churu, and decorated with her catnip treats + freeze dried anchovies!
2
2
24
968
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
This is a good one.
12
96
2
1,085
12,048
β­•οΈπŸ¦ŽπŸ’šπŸŒΆ Ding πŸŒΆπŸ’šπŸ¦Žβ­•οΈ retweeted
John Campbell pulling Luxon up on his 9 new taxes rubbish is good but then letting him waffle on saying it again and then bang it's the end of the interview. Bloody shocking.
2
15
1
113
1,351