⚠️ WARNING: Things to avoid with your iPhone Duo. • Don’t rub keys or coins against the inner screen • Don’t dig your fingernails into the inner screen • Don’t scrape the titanium frame with a knife • Don’t rub chainmail armour against the display • Don’t peel off the screen protector • Don’t pour dirt into the hinge or ports • Don’t bury it in the sand • Don’t force it closed if something is stuck • Don’t fold it 10,000 times just to see what happens • Don’t put it in a freezer at -20°C and repeatedly fold it • Don’t hold a lighter up to the screen • Don’t sit on it when it’s unfolded • Don’t bend it backwards • Don’t twist the phone to test its strength • Don’t drop it down a flight of stairs • Don’t run over it with your car Or if you do, make sure you have AppleCare+ 😆

The iPhone Duo has failed my durability test. The inner display started to fail after rubbing it in diamonds, ketchup, and a bathtub of dog urine. I cannot in good conscience recommend this product

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.

NEWS! Kids to dress as PHP in most terrifying Halloween ever newsthump.com/2026/10/22/kid…