
As Promised! I have decided to update my guide for preparing for OSCP. The guide is full of new updates and information to help you prepare for PEN-200/PWK 2.0. If anyone wants to read it here it is: netsecfocus.com/oscp/2021/05…

Blue Teamer in Disguise. Blog at netsecfocus.com. SANS Netwars Champion. Former community manager and founder of the Offsec community for @offsectraining

As Promised! I have decided to update my guide for preparing for OSCP. The guide is full of new updates and information to help you prepare for PEN-200/PWK 2.0. If anyone wants to read it here it is: netsecfocus.com/oscp/2021/05…


@KismetWireless Wardriving with QCACLD wifi monitor mode is now confirmed working on the upcoming @kalilinux NetHunter TicWatch Pro 5 (still stock kernel tho) 🎉🎉⌚📡🌍 #wardriving #kismet #kali #nethunter @Mobvoi_Official @androidmalware2 @v0lk3n @Shubhamvis98 @TJ_Null

Every offsec/redteamer NEEDS to spend time on the blue team in appsec + detection. Even if it’s just a short staff-aug gig. Need to stop hearing “there is no playbook, we are blindfolded”; it’s been discussed extensively, you’re just too busy popping xss?

Cyber security awareness month is over. We did it, everyone is aware of cyber security now. Let's not do this again next October?

Pround dad moment tonight. My son and his band The Bridge will be on BBC Introducing debuting their new track Oprah. So if you are into indie music, check it out. Show starts at 9pm on @BBCRadioWales presented by @welshmusic.

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.


hug your blue teams, its a mess. poc once the dust settles.


A moron has released a POC early for php2shell so here is what you need to do: If you’re on version prior to 8.2: Edit php.ini: session.upload_progress.enabled = Off Then reload php-fpm and restart apache If you’re on later version: Update (it’ll be available in a few hours) In any case, the mitigation for the php.ini should work either way. Not sure if it’ll cover both vulns though so keep an eye on that. I’ll be reporting on follow up activity on windows as a target. Good luck!


Join me this Friday at 11AM PT for the next @offby1security stream with @0x4ndy and Milenko Starcik for a stream on Finding and Exploiting Spacecraft Vulnerabilities! youtube.com/watch?v=j4kx0u_B…


I’m teaching Breaking In: Physical Intrusion & Social Engineering Tradecraft at WWHF Mile High with Antisyphon Training, Feb. 16–17, 2027 in Denver. Two hands-on days covering OSINT, pretexts, physical intrusion, adaptation, and reporting. bit.ly/alethe-breaking-in?ut…

Opus 5.5 came out. Where is my reset please?
Ladies and gentlemen... start... your... ENGINES. We are almost Tuesday and I promised a reset for Tuesday. Among some other things. See you soon.