holllyyyyyyyyyyyyy fffffffffffffffffff

I'll be in London speaking at Scale or Die - if you're around, would love to meet! luma.com/scale-or-die-26

We’re disclosing HEIF Heist, a months-long investigation into libheif that allowed us to hack OpenAI, Slack, Meta, GitHub Ent, Rails, Next.js, ImageMagick, and many more. It was literally xkcd #234, one obscure image library beneath a huge number of apps. 🧵

We found some stuff. Actually, quite a lot of stuff. Back in July, our team @rootxharsh, @S1r1u5_, and @iamnoooob managed to compromise multiple OpenAI employees’ ChatGPT accounts. In theory, any ChatGPT connector can be affected. This includes Slack, github, email, and other services. 🧵

really scary find from @S1r1u5_ and team, hacking into OpenAI's monorepo! great writeup from the @WSJ

On July 25, we hacked OpenAI. Two bugs let us take over ChatGPT/Codex accounts of OpenAI employees (+some unaffiliated users) and reach connected services: Outlook, Slack, GitHub, etc. We proved it with a PR in OpenAI’s internal codebase . It took us <72h. 🧵

Anchor v1.2.0 is here, including `lang` and `spl` fixes that missed the last release. What's new: • Better zero-copy support and CPI fixes • Newer Rust toolchain for smaller binaries • And much more... Shoutout to @clubby789 and @madduswaroop for pushing this through!

1/ We found a full collision for the Poseidon1 Collision Prize instance and submitted it on July 31. Two different messages, identical 16-word output after all 28 rounds, verified on the Initiative's official implementation. The technical breakdown and full story ⬇️

Acctual is joining Altitude to bring invoicing into the global operating account, alongside a deeper bill pay experience. We’re bringing more of how businesses get paid, pay bills, move money, and run finance into one connected system. Invoicing, now in your Altitude account.

Great panel with @claudijd, @_mwc, and @amandatums on how security coordination can help inform smarter policymaking Thanks to @SolanaInstitute for hosting!

I’ve joined @thinkymachines to work on safety & alignment. The default trajectory is that as AI gets more powerful, control over it will concentrate in the hands of a few. I’d rather build safety systems that let control over AI be shared widely. Longer thoughts below.

Solana is the most battle-tested network. Each stress test on Solana has been met with major improvements by the core engineering teams and further improved the network resiliency time over time. Solana's resiliency isn't just about surviving the worst days, but also making ambition for a better future possible. thestreet.com/crypto/innovat…

📌 AI made finding bugs cheap, but it didn’t make responsible disclosure optional. Finding and exploiting vulnerabilities has never been easier. A few hours of prompting now does what used to take a skilled researcher weeks. Unfortunately, defenders no longer enjoy the asymmetry they relied on. Security is still a cat-and-mouse game, but with many more cats, the user suffers. Which is exactly why the process around disclosure matters more than ever. How it works, and it is not complicated: ➤ A researcher finds a bug and contacts the vendor privately. ➤ The vendor reproduces, acknowledges, and both sides agree on a timeline. 90 days is the common default, more or less depending on severity, capacity to fix... ➤ During that window both sides keep it secret while the vendor fixes and ships. ➤ Once users are protected, both sides publish. The ecosystem learns. The researcher usually gets paid. The issue now is the barrier is so low that anyone can surface a finding with no security background, and some skip straight to the audience: ❗Presenting a reproduction of an already-fixed bug as a live compromise. ❗Full disclosure of a bug that is not fixed yet. ❗"Critical vulnerability found" teasers, dripping details for engagement. Call it what it is: attention farming with someone else's risk. When the bug sits between a user and their funds, this is reckless. Especially in crypto, where there is no chargeback. But the damage doesn't require live funds to be at stake. Manufactured panic causes harm of its own, because it drives people away from self-custody, and that damages the whole ecosystem. So I have three asks: 1️⃣ For users: software and hardware have bugs, always. The single most effective thing you can do is stay updated and follow basic security hygiene. That has never mattered more than today. The time between releases and malicious actors exploiting the vulnerabilities have shrunk dramatically due to LLMs and that one can't afford to be passive and postpone security updates any more 2️⃣ For new researchers with a fresh model and a real, validated finding: welcome, we need you. Use the vendor's disclosure process. That is not bureaucracy. It is the difference between making the ecosystem safer and putting users in the crosshairs for a few likes. Remember that security communication must be accurate and proportionate. State the severity, affected versions, and fix status in the first sentence, not the tenth. 3️⃣ And to everyone building in this industry, vendors and researchers alike: let's make coordinated disclosure the norm we defend out loud, not the fine print. Reward the researchers who do it right. Refuse to amplify the ones who trade user safety for reach. This is how we win, together. Some of the actors already support the initiative. @Ledger @Trezor @FoundationHQ @AnchorWatch @_SEAL_Org and others Spread the message.

@0x10n found a cool thing in v8.

simple fixes go a long way

I'll be in DC on the 14th, if you're around come say hi! luma.com/DCSummit

we're looking to grow the design team a bit! you'd get to work with @enscribe, super talented at what he does

here we go again..