Trail of Bits

This account is verified. Learn more

@trailofbits

We help secure the world’s most targeted organizations and products. We combine security research with an attacker mentality to reduce risk and fortify code.

New York, NY trailofbits.com Joined March 2010

267 Following 40K Followers 4.4K Posts

Latest posts 5

Pinned post

Trail of Bits @trailofbits Oct 29

October Trail of Bits Tribune: Releasing a PHP exploit demo, new plugins for patching, and package-integrity research. Plus Brotli-checker, SequenceHash, and six new public security reviews.

Read the Tribune: mailchi.mp/trailofbits/oc…

Trail of Bits @trailofbits 2d

Attackers can drain wallets by abusing a signing service, even without stealing private keys. Our 4-step post-Binance hack guidance helps wallet teams test what their signing systems can authorize and what limits the damage if signing is compromised.

blog.trailofbits.com/2026/11/06/aft…

blog.trailofbits.com After Binance, check what your signing systems can approve Four steps to strengthen wallet security after Binance: restrict signing access, control delegation, limit losses, and detect changes in wallet authority.

Trail of Bits @trailofbits 5d

A cryptographically verified tally doesn't mean every vote is legitimate. Paper ballots still matter: they provide an audit record independent of software. We explain how electronic voting works, and how cryptography can make paper-based elections more trustworthy. blog.trailofbits.com/2026/11/03/the…

blog.trailofbits.com The cryptography behind electronic voting (and why paper ballots are still essential) Cryptographic techniques can help protect ballot secrecy and prevent manipulation in electronic voting systems, but paper ballots are still essential.

Trail of Bits @trailofbits 6d

We’ll be at Devcon in Mumbai from Nov 3–4 at booth Starter 06 (3rd floor). If you’re building smart contracts, blockchain infrastructure or cryptographic systems, come chat with our engineers.

Trail of Bits @trailofbits 6d

Stable software often ships with known bugs because the fixes are never backported. That backlog is now an easy target for cyber-capable agents.

We used Codex to cut time per backport from days to ~30 min, with 149 Linux kernel CVE fixes applied so far.
blog.trailofbits.com/2026/11/02/bac…

blog.trailofbits.com Backporting security fixes at scale with Codex We’re using Codex to reduce the backporting process time from days to hours per fix, empowering human patch reviewers to rapidly submit fixes for critical software.