Pinned Tweet
The Part 2 article is now up (link below). It shows using the exploit we examined in Part 1 to target Chrome and other adjacent processes to pull interesting artifacts out of memory.
medium.com/@andy99998/using-…
I now don't feel quite so much like I'm missing out, but still...
Current information I have on php2Shell:
- The RCEs requires the attacker to obtain memory addresses which are typically protected by ASLR.
- I suspect the original author (lcfr_hax) likely has a reliable exploit which leads to stable code execution.
- Most of the PoCs being posted are completely non-functional AI slop.
- There is at least 1 working non-slop exploit being passed around, but it's reliant on bruteforcing for ASLR bypass, so not particularly impactful.
- Rumor of ITW exploitation are patchy. There are attempts being seen using the non-functional leaked RCE, or variants that are config / system specific.
- Some rumors point towards a known-working exploit being used by threat actors (I've personally confirmed this specific exploit works, but the ASLR bypass technique is unreliable at best and massively limits the potential impact).
- I'd expect heavy ITW exploitation in the next few weeks based on how many people are looking at this. Though, success rates will vary heavily based on the specific exploit chain.
Lol
Leaving this here, PHP 8.5.12 security patch is incomplete. ( needs further validation )
Readers added context they thought people might want to know
Unvalidated AI output (author admits in replies: omp with glm5.3 + ds4), not a lab result. Its screenshot says both CVEs are fixed; the 'surviving paths' need unserialize() of attacker data or an app LFI. Patch per php.net: php.net/archive/2026.p…
I go on holiday and the biggest vuln of the year drops...while fortinet also throws out a load of big bulky patches...
It's my cyber wet dream week. Aw man.
Someone catch me up when I'm back please.
Andy Swift retweeted
Have seen some posts on this that contain an (understandable) misunderstanding of probability.
If you use an RNG (true or pseudo), the chance of generating any number is the same as the chance of generating any other.
If you ask for 2 6-digit random numbers and you get 123456 and 000000, your RNG isn't necessarily broken.
As humans, we see patterns in everything. But patterns can occur by chance. The chances of generating 123123 and 111111 and 428946 are exactly the same.
In fact, if an RNG never generated "pattern" numbers, it would actually be less secure than one that did.
Even the quoted post is wrong when it says "Each key should be a 116-digit number, but one was just 4."
Technically, the key that was "just 4" was a 384 bit number with 381 preceding zeroes.
Many keys, when randomly generated, will have preceding zeroes. Many will have preceding ones.
The "value" of the key is 4. The length of the key is still 384 bits. The value isn't what gives the key its strength. The key of value 2^384 - 1 isn't the strongest key, for example.
However, that doesn't mean a key of value 4 isn't insecure, but it's for a very human reason.
When we brute force keys, we need a starting point. While we could theoretically choose any number, we tend to just go with what is easier: starting from 0.
So yes, you'd brute force one of these keys on the 5th attempt, and the others would fall soon after.
But if you started from the other end of the key space, from 2^384 - 1 and decremented instead of incremented, you might also find a key on the 5th attempt.
That would still be bad.
You could choose an arbitrary starting point, and get lucky. That would also be bad.
All said, that doesn't mean the key generation process they used was good. The fact it produced a bunch of easily brute-forceable keys is very, very, bad.
ukdefencejournal.org.uk/firm…
Just gimme the firmware.
Andy Swift retweeted
Episode 47 - Cars, Cats, and Clankers with dawgyg!
@0xTib3rius & @SwiftSecur1 are joined by Tommy DeVoss (@thedawgyg) to talk about his cars, his cats, and his AI hacking.
Links below!
HEY! YOU!!! do you like....cats?!?!? do you like.....cars!??!?!?!
WELL! come join me, @0xTib3rius, the one and only @thedawgyg while we chat about cats and cars....oh and a lil bit of hacking stuff I dunno....
Spotify: open.spotify.com/show/3PeV2F…
Apple Podcasts: podcasts.apple.com/us/podcas…
Amazon Music: music.amazon.com/podcasts/cf…
YouTube: youtube.com/channel/UC5L2Q76…
Ahhh CrestCon it was genuinely a huge privilege to present to you today! Great turn out and some awesome conversations with a lot of really cool people!
See...I will miss this sort of thing, our old reporting system at work has comments like 'sorry wrote this function while drunk' in it 😂
So many github 'pocs' at the moment whose title is a recent cve yet code within is for a different...in some cases much older/unrelated cve 😂
github.com/murrez/CVE-2026-1…
This one's readme even states a different cve before you even read the code 😂
I like a cheeky McDonald's so not sure I want to read this 😂 but I will lol
#31 - McDonald's
I Read The Policies So You Don't Have To;
medium.com/@ItsNotNicole/i-r…
Andy Swift retweeted
Crawlers are a normal part of the web. Yandex runs a search engine; of course it generates bot traffic.
Bot traffic from Russia does not automatically mean Russian propaganda bots. Yet people here, including journalists, keep treating the two as interchangeable.
That Cloudflare chart shows automated web requests from Yandex’s network. Where’s the data showing that propaganda accounts stopped posting?
Journalists in particular need to understand this distinction. Precision matters when a misread traffic graph becomes the basis for a political narrative.
Suddenly dawning on me how close this is and I probably need to start rehearsing my performan...I mean...presentation🤣
For crest companies and crest members...I believe you get free tickets!
crest-approved.org/event/cre…
I said it before, ill say it again... some things we have already peaked in design...we have tactile switches in racing cars because a touchscreen is somewhat suboptimal to operate travelling at 100+mph. Im not a pilot but I cant imagine touchscreens making much sense here either?
Touchscreen cockpits display units are here.
The new Touchscreen Control Display Unit (TCDU), featuring an AMLCD screen, is now available for retrofit on the 737 MAX and NG, while also being rolled out on new MAX aircraft as an optional feature.
Pilots will probably say: “I can’t stand touchscreens in the cockpit. There’s nothing wrong with the FMC we have. Give me my buttons.”
Fair point. We used to say the same about cars—now most of us have adapted to touchscreens.
But from a maintenance perspective? We actually love them.
Usually, maintenance replace FMCs because of loss of tactile feedback from worn-out buttons.
For dispatch, an inoperative FMC may be deactivated by opening and collaring its CB, but it must be replaced because it may affect ETOPS/EDTO operations.
For the flight crew, when operating with one FMC inoperative, the FMC Source Select Switch is selected to the operational FMC (BOTH ON L or BOTH ON R) to accomplish all Flight Management Computing tasks.
This has me so conflicted. One hand photoshop has screwed the user base over the years. On the other...decompiling others work and rebuilding it feels a bit crappy too.
The price of professional software esp in cyber has gone through the roof in recent years too...wonder whats next...





























