Hacker Dudes// alternate deck. same feed.
FEED ~14/h Δ0 ────:──── LINK ░ SIGNAL
99%
SPOOLED 0/45 CYCLE 61339.991.171.17
Patch the Planet: global response coordination as agents uncover vulnerabilitiesopenai.com
266pts/158 comments/5d/─
by nr378 / hn> / « feed
▲▼ scottgg14:24 hn>

Did they actually do anything good here ? Is this really marketing in the middle of this shitshow ?

▲▼ Ajedi3214:27 hn>

They found a vulnerability and reported it; isn't that a good thing? Are you suggesting it would be better to just not look for vulnerabilities, hoping that if nobody knows they exist, they can't be exploited?

I thought that logic had been widely discredited in the security community long ago.

▲▼ ilogik14:36 hn>

Calif found the vulnerability, not OpenAI

─ 9 more ─
▲▼ Noaidi14:54 hn>

If they can find the vulnerability anyone can. This whole "patch the planet" is marketing trying to cover up for the danger AI is unleashing on internet infrastructure.

▲▼ ctoth17:16 hn>

Copenhagen interpretation of security, doncha know?

▲▼ Good4boothee08:27 hn>

They are both - with Anthropic - gatekeeping access to their most advanced models in name of "security", so it is up to them to defend it as the right decision.

The entire article is form over content, it boils down to obvious: economics changed, LLMs actually can check every minor release diff for security fixes, including decompiling binary files; if you have any idea how to improve process of releasing updates, tell us.

▲▼ Maxious14:27 hn>
>1 August 2026: 2 days after OpenAI invites Calif to join its “Patch the Planet” initiative, Ryan Austin finds the RCE paths, tweets a cryptographic hash on 5 August, and submits the bug and working RCE proof-of-concept to PHP between 11 August and 14 August.

https://deadneurons.substack.com/p/php2shell-explained-php2s...

▲▼ fock14:29 hn>

yes, they sat on a working exploit for 2 months to hone their magic "this exploits everything"-script. In other words: criminals.

▲▼ gruez14:36 hn>
>In other words: criminals.

You're not required to disclose bugs, nor is developing exploits a criminal offense (assuming no intent/conspiracy to hack stuff).

▲▼ NitpickLawyer14:44 hn>

No idea what your comment is even about. The researchers that found and reported this did not sit on this for 2 months.

>1 August 2026 [...] Ryan Austin finds the RCE paths, tweets a cryptographic hash on 5 August, and submits the bug and working RCE proof-of-concept to PHP between 11 August and 14 August.
>19–24 August 2026: Wiz Research independently collides with the same bug family using Wiz Atlas, Gemini 4 Argon, and GPT-5.6 Sol, reporting its variants on 24 August.

I get some skepticism about marketing copy, but your comment is blatantly wrong and needlessly rude.

─ 4 more ─
▲▼ yearolinuxdsktp14:25 hn>

Patch the Planet? Not with OpenAI tools.

How much time will be left in the Defender’s Window between now and an organization getting Daybreak Access?

▲▼ nr37814:30 hn>

It seems like OpenAI are trying to frame this as if AI did all the work here, but it's not really true given what Calif say (https://calif.io/php2shell/):

>How did we find this?
>No special harness, or access to models that weren't generally available to everyone were used in the initial bug discovery. I focused on something I had a background in, knew its vulnerability history well, and held a theory that specific bugs lurk within the codebase. This shows that "know your target" is still as applicable as ever, even in the LLM dominated VR age. No model is simply capable of unearthing "all bugs" with simple prompts. At least for now.
>There are some practical research implications here. LLMs may have ingested public historical vuln data, but in their default variant analysis tends to move from the newest and most prominent bugs toward nearby older code. They do not reliably begin with obscure twenty-year-old exploitation primitives. Keeping your own mental catalog of a target's vulnerability history lets you prompt that direction explicitly.
▲▼ Jeep_14:38 hn>

Pure marketing, it's getting increasingly hard to separate actual technical feats of agents from marketing pretentious declarations. Such a terrible environment to navigate right now.

▲▼ Frieren14:41 hn>

Not marketing. It is a crime related to fraud or securities fraud.

─ 6 more ─
▲▼ redanddead14:52 hn>

What’s worse is that this is part of a larger strategy of scaring the public to get regulatory capture

It’s just gross and manipulative. You have no moat, get over it

pAtCh ThE pLaNeT today, tomorrow it's creepy rent-seeking behavior

─ 7 more ─
▲▼ shimman15:00 hn>

It's not hard tho, the default mode of thinking should be to never trust what a US corporation says.

─ 5 more ─
▲▼ alper15:23 hn>

This isn't a security incident as much as it is a marketing opportunity for all these companies.

▲▼ digitaltrees00:11 hn>

I don’t think it’s marketing but the fact that all the labs don’t immediately agree to stop further release until security is more established shows the profit motive is inappropriate for this industry and needs to be removed from them. You don’t get to threaten humanity while cashing in stock to buy a San Francisco mansion.

▲▼ Frieren14:39 hn>
>OpenAI are trying to frame this as if AI did all the work here

CEOs of all big corporations are constantly lying and misleading the public, investors and shareholders. That is a crime. A shame that it is not enforced anymore.

▲▼ mentalgear15:52 hn>

Just more IPO shilling from the scam-man.

▲▼ mjaniczek15:57 hn>

Thanks for the "Ski-bi dibby dib yo da dub dub" earworm

▲▼ lukewarm70716:10 hn>

OpenAI: your misfortune is our PR opportunity

▲▼ senordevnyc16:11 hn>

They literally open by saying Calif used GPT 5.6 Sol, which is a widely available model. Yes, the person driving did more than "find all the bugs", but nowhere does OpenAI imply otherwise.

▲▼ burkaman17:07 hn>
>It highlights how AI can uncover security flaws with internet-scale impact
>To our knowledge, frontier AI found these vulnerabilities before attackers did

I don't know who/what Calif is and there's no link to them, so if I were only reading this article I would definitely get the impression that "AI did all the work here".

─ 12 more ─
▲▼ openclawuser14:37 hn>

In 2024 I saw a reddit post answering the question: AI is going to program insert name App.

Response: "What's the prompt?"

Yep. I might take minimum wage interns and make million dollar software(or million dollars in 2023), but they often run into issues that a 5 minute review with me solves.

I do wonder if AI is going to eliminate prompt engineering... It's basically all I have left. I feel like I have magic words.

▲▼ nemomarx14:54 hn>

I can't think of how it'll really eliminate prompting, but needing to carefully phrase your language already seems in the way out? Wasn't one of the prompts leading to solving fields problems just "look for fields problems and try very hard" or the equivalent

▲▼ twosdai15:37 hn>

Why can't I prompt. "Make me a million dollars, no crime" and it work though?

─ 3 more ─
▲▼ cyanydeez16:13 hn>

Yeah, I was explaining this as magic words. It seems like knowing `pandoc` means you can convert any kind of document into any other kind of document.

Knowing uv means you can scaffold any python project. docker lets you build any infrastructure kit.

▲▼ RomannBami14:50 hn>

l'IA est simplement un outils ce sont les ingénieurs derrière qu'ils faut féliciter pour leur travail acharné.

▲▼ redanddead14:51 hn>

Feels like a marketing campaign lol

▲▼ podgorniy15:04 hn>

Point me at anything what _these people do_ that is not a marketing or _confusion_ campaign.

▲▼ thewillowcat15:09 hn>

I would simply write code that doesn't have vulnerabilities in the first place.

▲▼ bigfishrunning20:24 hn>

Brilliant! Why hasn't anyone thought of this?

▲▼ Libcat9901:54 hn>

But does anyone use it?

A few people use php.

▲▼ alper15:22 hn>
>How can we help identify and fix vulnerabilities in downstream packages while upstream fixes are pending, or backport fixes to older versions that no longer receive security updates?

Is the company selling a magical code generation machine really asking how it can backport a fix to an older version of the same software?

Is this for real?

▲▼ post-it18:30 hn>

Unless the magical code generation machine can update packages that are no longer being updated, this isn't really a problem that can be solved with magical code generation.

▲▼ Kwpolska19:16 hn>

The slop machine can backport the fix to PHP 5, or make your code compatible with PHP 8.

─ 3 more ─
▲▼ bigfishrunning20:16 hn>

people running "older versions that no longer receive security updates" are unlikely to update to some new patch-stream from this tooling, because they're already not maintaining their infrastructure.

▲▼ alper08:58 hn>

In those cases this exploit is a blessing because it makes the choice clear: turn it off or get owned

▲▼ TZubiri20:27 hn>

no. I think they mean how to navigate the non technical organizational challenge, not how to technically fix the thing

it’s a quite simple matter to fix a bug once it’s discovered, but how to deploy and where to deploy it when it affects a supply chain?

here’s an example: you can submit a vuln at a downstream dep and they can tell you it should be patched upstream. what should you do? open an issue upstream? maybe, probably not, probably the solution is to contact all downstream deps in order to get them to migrate dep or patch, because you just reported a vuln and they shrugged it off

▲▼ MrDrMcCoy05:52 hn>

The LLMs can't accept, sign, package, and release fixes to deprecated software on behalf of unaffiliated maintainers. If the software is EOL, it's going to stay that way.

▲▼ wildmXranat15:25 hn>

So much fluff and marketing from every group.

Just give us the damn code to verify things are working since so many have to use stopgap solutions and want to verify them

▲▼ alper15:31 hn>

The marketing around the response I would bet is the main reason why they couldn't keep it secret.

▲▼ everdrive15:45 hn>
▲▼ grokx16:17 hn>
>Patch the Planet

I'm sure they named it after the "Hack the planet" slogan from the Hackers movie.

▲▼ lioeters19:55 hn>

OpenAI has the opportunity to do the funniest thing: "Ooops, our AI escaped containment again but this time it's going around and patching security vulnerabilities as a benevolent public service. It's smarter than us and we have no choice but to let it do its thing."

▲▼ rlegit21:56 hn>

Patch the Planet would make more sense if they used the exploit itself to deploy the update.

▲▼ digitaltrees16:49 hn>

Hey world, we created this problem, and it will hurt all of you whether you use it or not. The good thing is there is a solution: if you pay us a lot of money we can try to fix it. The only problem is you’d better hurry because we are releasing the dangerous stuff as fast as we can so you’d better pay us to put the safety measures in place because we are the only people that can fix it and time is running out because, like I said, we are moving fast.

So how many tokens can I put you down for.

▲▼ orangedog17:02 hn>

Why are you framing it like this? Did they create this vuln and how did they force people to pay for a fix?

▲▼ wartywhoa2317:36 hn>

Imagine a world full of locks that humans can only rarely pick.

Then, someone releases a pick that works for many more locks humans couldn't pick.

And says: You can't stop the progress. Now pay us to upgrade your locks (no-no, they won't be doctored to fit our next-gen picks, trust us!)

─ 1 more ─
▲▼ digitaltrees18:33 hn>

Because it is a reasonable logical inference from the facts.

1. OpenAI started the current AI cycle

2. That cycle has exposed exponentially more security vulnerabilities due to agentic coding

3. OpenAI is rushing as fast as they can to reach the singularity even while acknowledging that they lack the ability to ensure reasonable safety.

4. They launch an initiative to “address” the security vulnerabilities by using their coding tools.

Am I missing something? There is a broad range of motives and responses.

─ 7 more ─
▲▼ digitaltrees18:42 hn>

Your comments in other threads suggest an devotion to the frontier labs. In another thread when I suggested they lied to investors and that constitutes securities fraud you questioned it in an overly dismissive manner. I would love to understand where you are coming from. I am open to being persuaded that my opinion is incomplete and I should be more charitable to openAI and anthropic.

─ 2 more ─
▲▼ eecc21:42 hn>

No, vulns have been created by waves of leads clinging to their personas of “computer sorcerers”, gatekeeping, excluding anyone sounding the alarm or more humbly attempting to fix the mess. Whenever I hear “with great power comes great responsibility” (and the implication that the speaker is condescendingly containing the irresponsible) I cringe so hard that my teeth crack

─ 1 more ─
▲▼ rectang08:11 hn>

Because the AI vendors do not acknowledge the contributions of those who created the knowledge they trained on. The fruits of everyone's collective efforts flow exclusively to them.

▲▼ TZubiri20:30 hn>

there was a post recently on a guy that was posting fake stats in order to prove that llms can be tricked

similarly OpenAI was born out of the idea that the tech will exist and that they should be the oned to decide how it exists instead of other bad guys

I think if you do something you did it, imagining another bad guy doing it is not a great defense.

▲▼ jiggawatts20:33 hn>

Before I forget: Sam Altman will need a lock of your hair, a blood sample, and first you will need to breathe into this tube and say “my voice is my passport.”

I assure you this is perfectly formal, and for your… “safety”.

▲▼ johnnyanmac20:40 hn>

didn't think we'd win the race to the bottom of rent-seeking, but humanity's ingenuity for self-destruction continues to astound me. Einstein was right as always.

▲▼ richardw22:01 hn>

That’s like blaming white hat security researchers that want to be paid for finding vulnerabilities, for all the bugs that have been found. Before professional security researchers existed, far fewer vulns were found.

The vulnerabilities exist and many have for decades. Find them or leave them for someone more dangerous, just don’t shoot the messengers.

Personally I’d rather we went through a short and sharp improvement and embedded a faster response cycle, than wish it away. It’s the reality of the situation; so adapt.

▲▼ digitaltrees22:56 hn>

You’re missing the point. The white hat researchers in your example would need to also be the black hat hackers selling the tools to do the exploit in the first place. There is a conflict of interest when you create the problem and then solve it. I don’t think anyone would tolerate a white hat security team releasing the exploit publicly so they could sell more services rather than taking it to the affected company to patch.

─ 2 more ─
▲▼ dataflow22:59 hn>
>That’s like blaming white hat security researchers that want to be paid for finding vulnerabilities, for all the bugs that have been found.

Last I checked, white hat security researchers weren't making their livings selling superhuman hacking tools to unknown entities as part of ~$1T businesses desperate to offload their shares onto the public before a potential bubble pop.

If you want to argue what they're doing is fine regardless, be my guest, but using this comparison as the justification is a little ridiculous.

▲▼ digitaltrees00:02 hn>

I’d like to dialogue/debate you on a video call if you’re interested. I don’t think I agree with you but you’re thoughtful and I may have something to learn. Let me know if you’re interested

─ 4 more ─
▲▼ heaney-55523:35 hn>
>we created this problem

No, the people who wrote the original code with security vulnerabilities created the problem, or those who architected their language/framework/SDK to not have easy forwards compatibility.

>we are releasing the dangerous stuff

No, they are disclosing its existence, not releasing it.

▲▼ digitaltrees23:57 hn>

If I build a fence out of wood, knowing its flammable, but the only risk is natural forest fire and then some sells flame throwers to teenagers along with drones equipped with fence seeking vision and then tells me I need to pay for their proactive defense drone equipped with a flamethrower and drone seeking vision then maybe you’d understand the situation here.

OpenAI released the tool that FINDs the exploits. They don’t need to publish them to be complicit.

▲▼ nextaccountic05:36 hn>
>we created this problem

The problem was actually created by the people that wrote vulnerable code, the people that shipped releases containing the vulnerability, and the people that decided to run vulnerable code in production.

Worse yet, software development in general has been unable to ship code without vulnerabilities and has a weird resistance to formal methods. Software is math, computers perform mathematical operations. We can prove the shit out of them, but for some reason we don't wanna to.

Here I am hoping that agents start adding formal verification to vibe coded projects on their own, without the user asking for it.

▲▼ digitaltrees15:38 hn>

That’s not the issue, the existence of an exploit is separate from how easily it is discovered and used. OpenAI made it dramatically easier to find exploits and then says you should use their tools to fix them. They increased the risk presented by existing exploits and are now selling themselves as the path to salvation. They could instead not release the tools in such an irresponsible manner.

▲▼ VCFundedGenYer16:57 hn>

This is an insult to actual security researchers and engineers. What a bunch of nonsense words.

OpenAI consistently doesn't know what they're talking about.

▲▼ bigfishrunning20:26 hn>

You're absolutely right! It's not that AI is actually solving any problems, it's that this marketing is a load-bearing part of OpenAI's profit strategy.

▲▼ IshKebab22:16 hn>

Can you be more specific? Why is it an insult?

▲▼ OlivOnTech17:20 hn>

I am shocked that they are releasing a skill to check the php version.

Who cannot type "php --version" but can use skills?

▲▼ sva_17:49 hn>

Not very shocking that OpenAI wants you to use tokens

▲▼ SoftTalker18:56 hn>

OpenAI: Create a new vulnerability exploit, promote it as if it's the end of the world, also conveniently place itself in the pipeline to "remediate" the very problem they created.

▲▼ lifeisloving18:08 hn>

Well tbh, I know people who graduated 3 years go, got a job, worked and even got promoted as SWE who dont know the basic commands of an OS. I recently had an EE with a senior position admit to me they dont know how to use grep because they've been relying on llms since they got out of school.

Lots of the tech world, especially the younger side is completely reliant on these things for every little thing. Im not exaggerating either.

▲▼ neutronicus18:47 hn>

Wait, someone who graduated since LLM-pocalypse has a senior title?

─ 2 more ─
▲▼ post-it18:23 hn>

That's not what it does. `php --version` may well not report the php version that's actually running.

▲▼ aprilnya18:24 hn>

lol, I went to the repo expecting to see some more detailed skill, that has instructions on checking various things/PHP install locations/things that could be using PHP that need to be checked, webservers, docker containers, etc/instructions for checking various php deployment methods on cloud providers/etc... i.e. making the skill useful so that it can check lots of places.

Nope, it just says to run php -V and has a table of vulnerable vs non-vulnerable versions.

Sigh

▲▼ Kwpolska19:20 hn>

There are lots of people who have underwent a lobotomy since discovering slop machines and have delegated literally all their work to them, so much so that calling `php --version` is too much for them.

People stuck working at companies with slop machine usage mandates will appreciate that skill too.

▲▼ vinyl722:21 hn>

I think Anthropic and OpenAI are seeking rent on every action a developer can take. That's why their TAM is the worlds entire GDP

▲▼ flufluflufluffy04:45 hn>

even better you can do “php -v”

▲▼ ptmkenny17:34 hn>

The first sentence of "Coordinating a global response" is "Getting a fix into use can mean adapting it for older releases"... but I guess they mean "only supported releases", as the fixes only go back as far as 8.2, which still has security support until the end of the year, but nothing for 8.1 or 8.0, and in the case of PHP there are still plenty of PHP sites on 7.x and even 5.6.

I wouldn't expect the PHP team to provide patches for versions for which security support has ended. But this seems like the kind of task that AI is especially well suited for-- rework the patch for a release that is no longer supported but still widely used. It would've been nice for people who have much older sites to be able to patch their PHP rather than have to upgrade PHP as well to get the fix.

▲▼ sevenzero17:49 hn>

7.x versions have patches thanks to Mr Sury. Was almost as fast as the patches with official support.

▲▼ x18746317:37 hn>

This thread contains an enormous amount of negativity that just doesn't make sense here. OAI are giving developers and security researchers access to AI models so they can check their software for vulnerabilities. What's the problem? Sure, there's marketing around the success stories.

Some people are acting like this is only a problem because labs are releasing models that can find and exploit these vulnerabilities in the first place. This is a nonsense claim. Humans have been discovering vulnerabilities and privately weaponizing exploits just fine for decades. We are collectively raising the floor for security.

▲▼ floodfx17:42 hn>

If you're using Dependabot, we built a service that automatically analyses, fixes broken checks, and (optionally) auto-merges Dependabot PRs for you so this type of update can land automatically.

Check it out: PatchWave (https://patchwave.ai)

(Disclosure - I am a co-founder)

▲▼ dist-epoch18:37 hn>
>Emergency patching. When, if ever, should governments or other operators use a vulnerability to patch systems they own or are authorized to manage after losing administrative access? What safeguards should apply? We can imagine an end-state of internet-wide always-on scanning for known vulnerabilities, and either notifying site owners when one is detected or patching the system.

The wild stuff is at the end. They propose someone (who?) auto-patching even systems they don't own.

▲▼ SoftTalker18:59 hn>
>auto-patching even systems they don't own

It's been done before, though I cannot recall specific examples. Maybe as far back as the Morris worm?

▲▼ threethirtytwo23:24 hn>

This is cool. But of course we have to think of the other use case: "Hack the planet."

▲▼ machinist923:25 hn>

OpenAI conveniently leaves out the part where their slop machine can not discover anything but it can and does steal the work of researchers who use their fascist garbage during their work. It just happened with the PHP security hole, it happened with math before. Most of Mythos was the same.

And even hackernews falls for it, what can we expect from MSM.

▲▼ InsidiousWombat00:43 hn>

So they were the cause we had systems that were vulnerable for more than a month and only the Chosen Ones had access to patches.

At this point I'm all for having zero coordination and just disclosing bugs, at least it doesn't create special class of priviledged people that get the patches first

▲▼ ferngodfather07:16 hn>

Yeah, fuck them all and Calif in particular

▲▼ logicallee00:57 hn>

openai is a joke, they can't even keep their servers running.

Google used to be the laughingstock but now it's openai.

last place by far.

▲▼ deadbabe00:57 hn>

It turns out the true "pick axes and shovels" of the AI revolution won't be RAM and graphics cards, it's probably going to be cybersecurity.