Binance: $6.3B impacted. Early findings point to one engineer’s laptop and abuse of its withdrawal system. No key leak found.
We’ve long warned of this OpSec risk. Our assessments & training address it.
OpSec Academy: academy.oaksecurity.io
Talk to us.
Turns out the biggest barrier to quantum computing isn’t the $25k/quarter price tag. It’s that almost nobody actually knows how to use the thing it.
@cadillion of @quipnetwork: you basically need a PhD in quantum information science just to understand the question.
Worried quantum is coming for your bags?
@cadillion of @quipnetwork walks us through a quantum hack: ~26 days of compute for one shot at a key, roughly 50/50 odds. On average, 52 days to crack a single one.
Which means the first targets are the big holders.
‼️ Researcher Erica Windisch skipped coordinated vulnerability disclosure and published 11 unpatched Tailscale flaws.
In her lab, Tailscale SSH race conditions let one hacked device get root on other servers and add a rogue node.
🎙️ New CypherTalk: @cadillion and @ourcarback of @quipnetwork join us to talk quantum.
How much of the quantum threat is hype, and how much is real? Find out in this episode as we discuss the reality, threats, and opportunities.
🎧 cyphertalk.podbean.com/e/the…
3 auditors on every line of code, none of them seeing the others' findings until a consensus meeting. That is how Oak Security describes its process, and blinding is what makes the 3 count as 3 and not 1 repeated.
Dependency risk also includes ordinary bugs propagating across deployments. Review the version you run, the assumptions you inherit and the local changes you made.
Give upstream advisories a downstream owner. Track patch adoption and test the failure case in your own configuration. A fix in the upstream repository is only the start.
A dependency list tells you what you use. An authority map tells you what it can do.
For every vendor and upstream module: can it move funds, alter a trusted build, or change a security check? Who can revoke that authority?
About half of Q3's $1.07B in losses came from two supply-chain compromises.
Which vendor software can authorise transfers? Which build artefacts do users trust?
Our Q3 update: oaksecurity.io/research/blog…
ALT Oak Security Q3 2026 research: about half of the quarter's $1.07 billion losses came from two supply-chain compromises. External software modules connect to a custody chamber.
Map every path that can move funds: contract logic, signers, vendor software, release pipelines and dependencies. Give each path a review process and an owner.
Our State of Web3 Security report now includes Q3 2026: $1.07B lost across 20 incidents. About half came from two supply-chain compromises.
Read the report and explore the dashboard: research.oaksecurity.io/
Incident data: @RektHQ.
Alex @0xhalloc and Jan @JphFritsche currently in Singapore for @token2049!
Come to our booth at the Nexus Startup Area to talk about the future of private payments.
🎙️ New episode: Kyle Den Hartog (@PryvitKyle), security engineer on the wallet at @brave .
- Why your wallet address is the new tracking cookie
- The browser as an attack surface
- The limits of ZK proofs.
🎧 cyphertalk.podbean.com/e/the…
We have just published our audit report of
ZIGChain v5 for @ZIGFinance. Read all about our findings and recommendations in the report:
github.com/oak-security/audi…
Building on @arbitrum? The Arbitrum Security Program is open for applications, with audit subsidies for eligible projects.
Oak Security is an approved auditor. Name Oak in the form’s “Preferred auditor” field.
Apply: tally.so/r/3xzEzv
ALT Oak Security announces its approved auditor status for the Arbitrum Security Program. A yellow-to-magenta ribbon connects a modular block structure and an audit checklist. Applications are open.
~1,783 wstETH, about $6M, drained from a vault on Base today. The attacker got a malicious contract added to the vault's whitelist, then used it to borrow aBaswstETH debt tokens and pull the underlying wstETH out.