Socialk@s retweeted
Details on how @AnthropicAI 's OSS-SCAN vulnerability reports were handled in the last release of radare2 trufae.substack.com/p/myths-…
Socialk@s retweeted
David Craddock’s next book, But Can It Run DOOM, is on Kickstarter. I wrote the book’s foreword! Check it out if you’re interested in reading about how we made DOOM with porting in mind, and all the ways people have ported the game over the years. kickstarter.com/projects/gab…
Socialk@s retweeted
CTFs ain't dead!
We organized a speed pwning CTF at @Bsideslisbon. No AI, human-only.
Congrats to the winners!
1st- s1gn3rs
2nd- h11p13
3rd- tmv11
Completely agree here - You should patch PHP but the sky is not falling yet. The issue here is going to be all the IOT Crap that just does not ever get updated. There still is time to patch.
If you want to see the state of things, find a cyber range (I prefer HackTheBox). Go look for a bunch of old PHP Boxes and try the exploit out on them. Right now I think you are going to have a tough time finding a retired box that you can exploit with PHP2SHELL.... Atleast I hope you do because I am having a hell of a time doing it and both love/hate to learn how much of a noob I am at times.
AI is really good at making crap look good. I know the POC that shows a POC of <?php echo("OK") ?> being exploited sounds scary. But when you look deeper there are a lot of hard-coded offsets that make it only work on that target.
I'll be the first to admit I'm mediocre at exploit development, but I am in contact with enough extremely talented exploit developers to say this for certain:
Anyone claiming they were "easily" able to generate a working php2shell exploit with AI is either:
a) a world-class exploit developer with an extreme case of imposter syndrome.
b) currently looking at some very confident-sounding but wrong LLM output.
I'm rather certain it's the latter based on the number of AI-hallucinated exploits I've seen posted on GitHub. Threat actors are also blasting my honeypot network with "php2shell" exploits that not only don't work, but aren't even within 10,000 miles of anything to do with how the exploit actually works.
I've seen the same technique from the attached image in multiple alleged "php2shell exploits", including one on GitHub with over 100 stars. Problem is, it's not php2shell, nor is it even a vulnerability at all. It's a technique known as "session poisoning", which can be leveraged to exploit local file inclusion (LFI) vulnerabilities in PHP apps (not PHP itself).
The only thing it has in common with CVE-2026-109618/CVE-2026-109619 is they both use the "PHP_SESSION_UPLOAD_PROGRESS" feature. And mitigation advice for both issues reference setting "session.upload_progress.enabled" to "Off".
People are shoving loose details of the vulnerability into LLMs, the LLMs are keying in on the "PHP_SESSION_UPLOAD_PROGRESS" string, then generating session poisoning code that has nothing to do with the actual CVE. And because the people doing this have absolutely no idea what they're doing, they're confident enough to post their "proof of concept exploit" to GitHub and share it on social media.
So if you see people talking about "session poisoning + LFI" it's likely their LLM hallucinated an exploit based on a 2018 blog by Orange Tsai talking about a local file inclusion attack vector.
What's even worse is that "security researchers" are then using LLMs to triage these exploitation attempts, falling victim to the same hallucinations, then confirming there is ongoing mass-exploitation (there currently isn't).
The actual real exploit is very difficult to exploit, and so far I've not seen anyone successfully get it working on more than a handful of PHP version with highly-specific configurations.
LLMs are useful tools in the hands of skilled professionals, but for others, they're often just a Dunning-Kruger accelerator.
Socialk@s retweeted
Worried about the last vulnerabilities in #PHP? 😱 Throw some oneliners and patch the module in your servers with me! substack.com/@trufae/note/p-…
Socialk@s retweeted
Recap por si te lo perdiste:
> RCE crítico en PHP
> RCE en Node.js (Brotli)
> Railway hackeado
> GitLab: CVSS 10.0
> LiteLLM comprometido (otra vez)
> PingCAP/TiDB Cloud hackeado
> GoDaddy revoca 400k certificados
> eMudhra: llaves de CA comprometidas
Todo en ~72 horas.
🤖 Made with AI
Socialk@s retweeted
For those running older PHP versions, either switch to packages.sury.org or ppa:ondrej/php's, those all have backported fixes for those old versions
Concerning the php2shell crisis; I have proof and logs that the attack started, at least, on 16/10 . Just one day before @amazon telemetry.
64
Socialk@s retweeted
🚨 Nightmare day for cybersecurity
Multiple major security incidents, active exploits, supply chain compromises...
If you run production systems, start patching NOW.
PHP: Two critical unauthenticated RCEs. Attackers already exploiting them. Patch NOW
LiteLLM: v1.107.0 on PyPI and Docker is BACKDOORED. Steals cloud, SSH, and AI credentials. Pin 1.106.2. Rotate secrets.
eMudhra: A certificate authority's keys were crackable. Update your browsers, systems, and trust stores.
Node.js / Next.js / React: Security releases for Brotli RCE, TLS bypasses, and TWO critical Next.js RCEs.
TiDB Cloud: PingCAP breached through stolen credentials. Customer information and other sensitive data exfiltrated. Read the attacker's release, fun stuff.
Plex2Shell: Weaponized within HOURS of the PoC. Attackers already deploying cryptominers and proxy backdoors.
BeyondTrust / Ivanti: Actively exploited zero-days added to CISA's KEV catalog. BeyondTrust attacks linked to a China-nexus campaign.
And that's not even the full list.
Patch. Audit. Rotate. NOW.
Contra todo pronóstico y sin aviso previo, Ondřej Surý ha aplicado los parches CVE-2026-109618 y CVE-2026-109619 tanto para PHP 5.6 como para PHP 7.4. En el log aparece: "Backported from 8.2.35". Nos ha salvado el culo a los que tenemos servidores Debian/Ubuntu.
Socialk@s retweeted
Vulnerabilidades de Apache HTTP Server podrían permitir ejecución de código
La Apache Software Foundation lanzó la versión 2.4.69 de Apache HTTP Server el 1 de octubre de 2026 para corregir 20 vulnerabilidades
blog.elhacker.net/2026/10/vu…
Socialk@s retweeted
0 days since the last "OpenAI dev shows you the RIGHT way to use a coding harness" thread. it's always 0 days.
Socialk@s retweeted
Cloudflare shipped their own version of ngrok to expose localhost to the internet.
The problem: those tunnels are getting indexed by Google.
Anyone with site:trycloudflare.com can browse random people's exposed local dev servers right now, no login, no tunnel URL needed.
Socialk@s retweeted
Excited to finally share my recent research, where I managed to hack Chrome, Comet, Edge, Opera and Claude in Chrome using one single browser extension
2 CVEs & $20,000 in bounties 🙂
Introducing - BragJack!
forever.security/blog/bragja…
Socialk@s retweeted
Fem una crida a tothom amb certa influència: creadors, periodistes, empresaris, esportistes, artistes…
Unim forces per impulsar una gran manifestació ciutadana, pacífica i transversal contra la inseguretat.
Sense sigles. Sense egos. Només el dret a viure tranquils.





























