I find the “patch the planet” initiative quite inspiring. openai and others are spending huge sums of money on updating and securing all modern open source software infrastructure. it will be a continual effort to make the world more robust
This is the "upcoming cyber model" from yesterday. Besides 948 Linux vulns, it found 111 renderer RCEs in Firefox, among which, 81 were novel. 30 were exploits for bugs known to developers that were thought to be unexploitable.
We are using this technology to scan more OSS projects and secure the Internet infrastructure.
This is just a start.
Trail of Bits retweeted
Read the interview about how we approached our audits with @trailofbits @OpenZeppelin and @spearbit
Auditing such a novel software stack like Miden comes with interesting challenges. Trail of Bits has written some nice tooling even to make their lives easier
Miden’s product marketer Gaylord Warner ( @zkGaylord) had a chat with cryptography engineering lead François Garillot ( @huitseeker) and protocol engineer Marti Górny ( @mmagician)
Our security researchers built an autonomous cyber vulnerability discovery, exploitation, and patching pipeline.
In a single run with an upcoming cyber model, it validated and generated patches for 948 local privilege escalation vulnerabilities in the Linux kernel at a total API cost of $1.2 million.
Trail of Bits retweeted
fresh fuzzy echidna, anyone? 🦔
Echidna 2.4.0 is out 🎉
🤖 MCP support for interactive fuzzing
🔬 considerably improved symexec via @argotorg hevm
⛓️ library autolinking with crytic-compile
🐛 fixes, reduced mem usage, and more
👉 github.com/crytic/echidna/re…
🍺 also on brew by now
Very interesting work by the OpenAI Cyber team
Stronger models needing less orchestration is also something we quickly realized while building our main auditing harness at Trail of Bits (Auditron)
Instead of strong constraints from the harness, that were needed with previous models, we now focus on four things: using different model families, coordinating their work, enforcing persistence, and providing the right tools/skills at the right time rather than fixed recipes
Our security researchers built an autonomous cyber vulnerability discovery, exploitation, and patching pipeline.
In a single run with an upcoming cyber model, it validated and generated patches for 948 local privilege escalation vulnerabilities in the Linux kernel at a total API cost of $1.2 million.
Trail of Bits retweeted
THORChain just inadvertently delayed the laundering of a significant amount of funds stolen from Binance.
The reason? An Ethereum reorg.
One happened this morning and caused THORChain to incorrectly issue a double refund to someone who had deposited 10 ETH.
This triggered an “emergency pause” on THORChain, preventing all users, including DPRK’s money launderers, from using cross-chain swaps.
Until the service comes back online, neither the hackers nor anyone else can swap through a majority of THORChain’s bridges.
Trail of Bits retweeted
We're aware a number of domains at name.com were improperly redirected late Friday as part of a plan to access visitors' crypto wallets. The affected domains have been restored. We're investigating and will update this thread as we learn more.
Update following the Binance incident:
All markets are now unfrozen across Aave V3 and V4.
They were frozen as a precaution after initial reports, which paused new deposits and borrows while withdrawals and repayments continued as normal.
Aave contracts were unaffected by the incident and positions remained fully collateralized.
Trail of Bits retweeted
We identified a security incident affecting a modified Claude Code VS Code extension accessed through our Cursor IDE extension marketplace, impacting at most 5,000 users. This malicious version of the extension was not developed by Anthropic. It does not impact other extensions downloaded from the cursor.com/marketplace, Grok Bot, Grok or our other SpaceXSI products.
In response, we took down our extension marketplace this afternoon, worked with relevant providers to neutralize the malware, and have reinstated the marketplace after confirming there is no further risk.
If affected, please review instructions in this blog post to understand how to find the malicious package and establish a path to mitigate any potential impact. We are asking all customers update to Claude Code for VS Code version 2.1.314: cursor.com/blog/claude-code-…
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.
binance.com/en/support/annou…
Update: Our PHP exploit is now production-grade.
* stock php.ini-production, display_errors=off, normal memory_limit, multi-worker, ASLR, under load
* ARM64 + x86-64 targets
* MediaWiki, WordPress, phpBB, Laravel
* Apache/mod_php and nginx/php-fpm -> root
teapawt.net/dguido/status/21131291…
Re: the widely circulated blog claiming the PHP bugs aren't easily exploitable: @trailofbits has a working exploit that gets a shell on an unmodified MediaWiki installation.
eliastaylor.com/noexploit/
Trail of Bits retweeted
We have completed our investigation into the attack chain behind the v1.107.0 release. Read it here: docs.litellm.ai/blog/securit…
Trail of Bits retweeted
wrote about "Black October," the PHP vulnerability, and the AI-fueled dread and panic I'm seeing among almost all of the cybersecurity experts I've ever known:
404media.co/php2shell-black-…
Five ways to keep safe online in the wake of AI-supercharged hacking reut.rs/4kdEF5T reut.rs/4kdEF5T
Attackers have agents hunting for bugs. We need agents writing patches just as fast. @trailofbits is doing the work to make this happen reliably:
teapawt.net/trailofbits/status/211…
Finding bugs is the easy part. Shipping fixes that hold up is harder.
We analyzed thousands of Codex sessions from our work on Patch the Planet with @OpenAI and built patching-bugs, a plugin that writes a fix, proves it, and checks it for regressions.
To prove a fix, the plugin checks that the original code fails, the patch passes, and reverting the patch brings the bug back.
patching-bugs hands each fix to regression-hunt, our second new plugin. We ran it on the patches behind 21 known regressions, and it reported 25% fewer false positives than a baseline Codex agent.
Both plugins work best when your repo has a THREAT_MODEL.md and a PATCHING_GUIDELINES.md. blog.trailofbits.com/2026/10…
Trail of Bits retweeted
Giving AI access to your money? Start by limiting the blast radius.
@anishrnaik, Principal Security Engineer at @trailofbits, on giving AI agents access to wallets, code and infrastructure.
00:00 Meet Anish from Trail of Bits
02:46 Patch the Planet
05:06 Package managers and hidden dependencies
09:34 Dependency alerts and package selection
12:27 Limiting an AI agent’s blast radius
15:47 Can AI fix bugs without creating new ones?
21:54 Hardware wallets and the wider security stack
26:43 AI attackers and defenders
28:53 OpenAI reports and what comes next
We're staring down the vulnpocalypse we predicted earlier this year. What matters now is how fast you can react to it. @trailofbits is developing key capabilities to dramatically increase how fast fixes can go out.
teapawt.net/trailofbits/status/211…
Finding bugs is the easy part. Shipping fixes that hold up is harder.
We analyzed thousands of Codex sessions from our work on Patch the Planet with @OpenAI and built patching-bugs, a plugin that writes a fix, proves it, and checks it for regressions.
To prove a fix, the plugin checks that the original code fails, the patch passes, and reverting the patch brings the bug back.
patching-bugs hands each fix to regression-hunt, our second new plugin. We ran it on the patches behind 21 known regressions, and it reported 25% fewer false positives than a baseline Codex agent.
Both plugins work best when your repo has a THREAT_MODEL.md and a PATCHING_GUIDELINES.md. blog.trailofbits.com/2026/10…
Trail of Bits retweeted
Google tried to keep a quantum weapon secret using zero-knowledge proofs. It lasted 63 days.
In March, Google Quantum AI published a new version of Shor's algorithm aimed at secp256k1, the elliptic curve that protects every Bitcoin and Ethereum wallet. It needs roughly 1,200 logical qubits, a dramatic improvement over everything before it.
Then Google did something no one had done before. It didn't publish the circuit. It published a zero-knowledge proof that the circuit exists, which certifies the attack is real without revealing the attack.
Then the experiment started to break.
Six weeks later, @trailofbits found memory bugs in Google's Rust prover. They forged a valid proof for a circuit that claimed zero Toffoli gates, an attack that cannot exist. It passed verification with the same key as the original. Google patched it.
On day 63, André Schrottenloher of Inria published his own circuits, rebuilt independently from Google's public papers. They matched Google's qubit counts and needed fewer gates. The hidden weapon was now open source, and slightly better.
Google researcher Craig Gidney confirmed the match and wrote: "We should just publish openly."
Zero-knowledge proofs were built to hide your balance, your identity, your vote. Here, a cryptographic tool was used to hide a weapon against cryptography, and both the hiding and the secret failed within one quarter.
The lesson isn't that ZK is broken. A proof is only as honest as the code that checks it. And in mathematics, a secret doesn't stay a secret just because it's hidden: once the world knows an answer exists, someone finds it.
The only thing still protecting Bitcoin from this attack isn't secrecy. It's hardware, and hardware gets better every year.
Trail of Bits retweeted
We've been taking security very seriously at OpenClaw for a while now. We just completed a Trail of Bits audit, publish our security advisories unlike every other agent product, and have alot more coming in this department!
openclaw.ai/blog/openclaw-tr…
You’d expect a lockfile to make a dependency immutable. But often it doesn’t: a hacked repository can swap in malicious code for the **same package and version**, and most package managers install it anyway.
teapawt.net/trailofbits/status/211…
We tested 25 package managers against a simulated malicious repository. Without a lockfile, only Go and vcpkg verified every download in our tests. With a lockfile, it's fewer than half.
blog.trailofbits.com/2026/10…





























