Masad says a Claude Code extension installed backdoors
He is openly speculating about a link to the Binance breach, and Binance has only said a DevOps engineer's laptop may be involved.
Amjad Masad says an official Claude Code extension was compromised and installed backdoors on developer machines, and he calls the story massively underreported. In the same post he asks an open question, could it be behind the Binance hack, pointing at the fact that the Binance incident involves a DevOps engineer's laptop.
an official Claude Code extension was compromised and installed backdoors on developer machines
That is a question, not a finding, and it is worth reading it that way. Masad offers no evidence connecting the two events, and Binance has not named a cause.
What Binance has actually said
Binance's own statement says its initial investigation suggests 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. The company says it found no evidence of any wallet private key leak. It puts the estimated total impact at around $6.3B, with roughly $3 billion frozen on-chain so far through blockchain partners.
Binance says it has temporarily suspended deposits and withdrawals while security checks run, revoked the affected address authorisation, and engaged law enforcement and blockchain intelligence partners. It says it will cover all losses from the SAFU fund and company funds, and will publish a detailed technical post-mortem once the investigation is complete.
So the overlap between the two stories is one word, laptop. Everything beyond that is Masad connecting dots in public.
The part that is not speculation
The broader claim Masad makes is the one founders should sit with. He argues that coding agents running on employee or contractor laptops are a serious risk, and he says his team wrote a whitepaper on how to sandbox agents to maximise productivity and reduce risk. He has a product interest in that position, and it is still the practical takeaway.
If you hand a coding agent full access to your development machine, your supply chain stops being the packages you deliberately audited. It becomes every extension you installed once, trusted because it was official, and never thought about again. A compromised extension does not need to beat your firewall. It is already inside, running with whatever permissions your agent has.
The business read. A solo founder with one laptop, the production credentials, the payment keys and three coding agents has built a single point of failure that a company with a security team would never sign off on. Nobody in the sources has tied the Claude Code extension to Binance, and nobody knows yet whether that link exists. The sandboxing argument does not depend on it.
Coding agents on employee or contractor laptops are a massive cyber and national security risk
Steal the numbers, not the vibes
One email a day. Under three minutes. Real MRR, real pricing, real launches from founders building with AI.
