@christopherkunz
I also tested another PoC and it was even more fake. i.e. it didn't even create a CLDAP structure that made sense.

I get that PoC||GTFO is a thing, but we've clearly entered a phase where it needs to be Verified PoC||GTFO. 🤦‍♂️

I don't get out much these days but here's a talk I gave at the North American OSS Summit recently: https://www.youtube.com/watch?v=ZquMucBZnaQ

For 19 years, GPS satellites have secretly broadcast a “numbers station” in their public signals. We decoded 12M messages: a 2011 flash where 31 of 32 satellites flipped in hours, “ghost” substrings repeating years apart, and a “TEXT” prefix spreading now. https://lsc-pagepro.mydigitalpublication.com/publication/?i=865273&p=62&view=issueViewer

🚀𝐎𝐟𝐟-𝐁𝐲-𝐎𝐧𝐞 𝟐𝟎𝟐𝟔 CFP looking for the research that will shape the conversations, techniques and tooling of tomorrow's offensive security community.
CFP closes on 1 July 2026, 18:00 SGT.
The next great OFF-BY-ONE talk might be yours!
https://cfp.offbyone.sg

A friend reported a LPE to Microsoft and in the advisory Microsoft fucked it and wrote a wrong description saying the vuln was in MMC.

Consequence: people wasting hundred of dollars on AI trying to analyze the wrong files just to get a fake PoC because AI brainwashed them 😂😂😂

"A working PoC" and the AI released a supposed MotW bypass. The real vuln was a LPE to System.

What a clown circus 🤡

One principle I’d like to be enshrined in law:

If you create incentives that reward a behaviour, you can (and will) be charged as an accessory in any case where someone is doing something illegal as a result of optimising for that behaviour. An affirmative defence would need to demonstrate that you had safeguards in place to effectively disincentivise that behaviour.

For example, if you are running a delivery company and you set targets that mean people are paid more if they drive or park illegally, you are automatically charged as an accessory to however many counts of dangerous driving your drivers are charged with. If you are a city councillor and vote to close all of the public toilets so that there’s nowhere for taxi drivers to relieve themselves, you can be charged as an accessory to a few hundred counts of public urination.

Part 2 of the custom PE resources series: how to embed any binary as a resource in Visual Studio and extract it at runtime.
https://trainsec.net/library/windows-internals/how-to-embed-and-extract-custom-pe-resources-in-c-findresource-loadresource-makeintresource/

Windows Kernel Programming, Second Edition by Pavel Yosifovich is on sale on Leanpub! Its suggested price is $37.95; get it for $24.21 with this coupon: https://leanpub.com/windowskernelprogrammingsecondedition/c/LeanPublishingDaily20260601 @zodiacon

20 years from now someone's Media Studies dissertation is gonna be titled "Parodies of Elon Musk in min-2020s popular culture"

#CultureStudies #academia #TV #cinema

Somebody wrote about Bring Your Own RWX Region DLL (BYORWXDLL).

Which, being a post-exploitation technique, is already something not terribly interesting to me personally, being a vulnerability analyst and all.

Stage 1: Realize that the provided script doesn't run, as it has a non-UTF-8 character in it (a 0x97 em dash). Since keyboards don't have an em dash key, this is a clear indicator that the script is AI slop. Also, who publishes something without even first attempting to run the very thing you have provided? 🤔

Stage 2: Realize that Intel(R) Extreme Tuning Utility, which comes with Intel graphics drivers by default comes with multiple libraries that have YOLO RWX memory sections.

Personally, BYORWXDLL isn't that terribly interesting to me. If somebody is injecting an arbitrary DLL on your system, they already own your system. However, I will admit that knowing which things on your system by design provide RWX memory sections is probably a good way to flush out the software that you don't want to have on your system.