The full run cost $1,213,430 in API credits—about $1,279 per distinct local privilege escalation vulnerability.
For context, applying historical Pwn2Own and TyphoonPWN bounty rates gives a hypothetical value of $18.9M–$66.3M.
This demonstrates the relative efficacy of using AI models for securing software—defenders should proactively analyze software to make cyber attacks cost-prohibitive.
haha, so apparently OpenAI are about to start training on your Daybreak Blue sessions, with no way to opt out.
Literally stealing people's private work, as they do it, is cartoonishly evil.
It also will presumably kill Daybreak usage by security researchers. Or at least, it should. The thing OAI have had to swear they are not doing to math researchers, they are now explicitly about to start doing to security researchers.
Yet another reminder of the importance of open models.
Man, I'm genuinely starting to wonder whether Kim Jong Il was Satoshi Nakamoto.
Last known Satoshi contact, April 2011, Kim Jong Il dies later that year and North Korea spends the next 15 years using Bitcoin as a replacement for taxes.
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.
The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.
As an immediate precaution, Binance has:
- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.
https://t.co/ywB2mKFy0p
@LinxzSec He makes half of a good point. "Personal" AI is not a good way to utilise resources.
AI on your desk and proprietary AI are not the only two options though, open source models self hosted but on server hardware is the sensible middle ground for most business cases I think
Verified! The 1st full win the the Wellness category has Interrupt Labs (@InterruptLabs) using an OOB Read and an OOB Write to exploit the Garmin Index BPM. They win $20,000 and 2 Master of Pwn points. #Pwn2Own
Managed to get @opa334dev to talk about the TSS bug on chITchat 👀 You can listen on most platforms but here is the link to Spotify. Will upload to youtube as well. https://t.co/7uWdlmJxgj
It was DOOMsday for the Lexmark CX532adwe printer as Interrupt Labs (@InterruptLabs) claimed victory and earned $5k & 2 Master of Pwn points! #Pwn2Own#DoomHack
Wow - the setup took a while (and included Starlink!), but Interrupt Labs (@InterruptLabs) successfully exploited the #Samsung Galaxy S26. They're off to the disclosure room to provide the details. #Pwn2Own
a lot of people dont appreciate the difference in required effort for a 1% reliable mem corruption exploit vs 10% vs 99% . this post https://t.co/NJ8qS1XFX3 by @natashenka expresses this well. the truth is that often a 10% reliability exploit is *no progress to full reliability*
We reported the bug to Discourse and OpenAI. OpenAI fixed the SSO issue roughly 14 hours after our initial submission.
Discourse received our separate report Saturday, replied Sunday, and had a fix Monday.
OpenAI awarded us $6,500.