Permission to Move
A trader's compromised key let an attacker pull 10.39M USDC from Lighter, whose Guardian paused withdrawals before its council returned about $5M. An Abu Dhabi court ordered firms to keep Binance theft assets restrained, Ledger device owners reported thefts and Coins.ph ended self-custody transfers.
At 10:11 UTC on Monday 16 November, 10,393,057 USDC left the trading platform Lighter for a single Ethereum wallet, according to blockchain analytics firm Bitquery. Lighter's own systems had not been breached, the company says. The attacker held a trader's API key, and the key had permission to move that trader's funds. Within the hour, Lighter's smart contract Guardian had paused withdrawals across the platform, and before the day was out its Security Council had returned about $5M to the trader. This week's stories turn on permissions of that kind: who could move funds, who could stop them, and who could release them again.
Week in 60 Seconds
- Lighter: an attacker used a compromised trading key to move funds through a public pool and withdraw from a separate account, according to reporting on Lighter's post-mortem, taking about 10.39M USDC. Lighter's Guardian system paused withdrawals, its Security Council returned about $5M to the trader, and withdrawals reopened the same day.
- HyprEarn: unauthorised trades hit Hyperliquid accounts that had approved HyprEarn's trading agents. The agents could trade but not withdraw, and stay approved until users revoke them.
- Safe: about $6.4M left a Safe multisig through a Zodiac permissions module, with no owner signature. Zodiac says the attacker may have used a compromised key with delegated permissions.
- Binance: an Abu Dhabi court ordered 18 companies, including Circle, to keep assets linked to the October theft restrained. ArbitrumDAO's off-chain vote on releasing frozen funds succeeded; on-chain approval and release remain unconfirmed in the sources reviewed.
- Ledger: Bitquery traced thefts from wallets whose owners reported buying Ledger devices in Dubai and Berlin. Ledger's separate confirmation of tampered Berlin devices does not establish the cause of those thefts. Its website was also reportedly affected by the Optimizely compromise.
- K3 Capital and Kava: about $3.42M left K3's sBOLD vault, much of it paid to block builders. Kava says about 53.9M KAVA was taken from HARD Lend.
- Coins.ph: the Philippine exchange stopped supporting transfers to self-custody wallets and now verifies every external transfer.
- Freeze Ledger: 26 freezes worth $33.13M, against 13 worth $34.97M in the previous edition.
A Key With Permission to Move
Bitquery traces the 10,393,057 USDC to one Ethereum wallet. Lighter announced a suspension of withdrawals at 11:02 UTC, CoinDesk reported. Its post-mortem says its smart contract Guardian "was triggered by the anomaly", pausing withdrawals; it does not say what Guardian flagged. At 18:21 UTC the same day, Lighter posted that deposits and withdrawals were "back to normal following the deactivation of Guardian Mode" by its Security Council.
Lighter's post-mortem, as summarised by SpazioCrypto, says the affected trader used third-party signing software that reused nonces, the one-time values that keep a signature from revealing the key behind it. Anyone watching enough of those signatures could reconstruct the trader's private API key. Lighter blamed "insecure signing code used by the affected accounts", not its own software kits, and said its protocol and contracts were untouched.
The key was enough. Lighter treated a public liquidity pool as one of the trader's sub-accounts, so the stolen key could move the trader's funds into it. From a separate account, the attacker bought shares in the pool, pushed the trader's funds in without new shares being issued, then redeemed the shares and withdrew. Every step used permissions the system recognised as valid.
During the pause, Lighter's Security Council returned about $5M USDC to the affected trader, according to The Block. The reporting reviewed does not explain how the council moved those funds. It is unclear whether the reported $5M return overlaps with the 10.39M USDC withdrawn. Reports that two market-maker accounts lost about $15.5M in total remain unconfirmed.
Lighter now requires a wallet signature, not just an API key, for transfers into public pools, and says API-key signatures are no longer public.
HyprEarn. Two days earlier, at 18:37 UTC on 14 November, HyprEarn warned of unauthorised trades on a small number of Hyperliquid accounts that had approved a HyprEarn trading agent. Its notice draws a line that matters: the agents could trade but could not withdraw or transfer funds to another address. HyprEarn said it had revoked the old agents on its side, but that they remain approved on users' Hyperliquid accounts until each user removes them. It has not disclosed how many accounts were affected, what was lost or what caused the trades. Nothing in the notice points to a fault in Hyperliquid itself.
HyprEarn's notice shows why revoking an agent within a service may leave its permissions on the trading platform intact.
Safe and Zodiac. Early on 16 November, about $6.4M left a single Safe multisig wallet through Zodiac's Roles Modifier, an add-on that lets approved role members act for a wallet without its owners signing each transaction, Unchained reported. Security firm PeckShield put the loss at $6.45M. Safe said its contracts and wallet app were unaffected and that "no owner signed it". Zodiac said it found no flaw in its contracts, and that "a role member key, probably compromised" sent a transaction its custom policy allowed. A compromised key remains Zodiac's explanation, not an established cause.
A permission that can trade, or sign, can still move money.

Frozen, Restrained, Not Yet Released
Binance's response to the October theft entered a new phase this week. On 14 November, Reuters reported that 87 networks had reopened for withdrawals during the week and that Binance aimed to restore the rest by the end of the following week. That was a target, not a completion.
On 18 November, the Abu Dhabi Global Market Court ordered 18 companies, including Circle and World Liberty Financial, to maintain restraints on assets linked to the theft, Reuters reported. The companies are not accused of wrongdoing. They may not lend, swap or mix the assets, and a further hearing is set for 1 December. Reuters said Tether was outside the order and was discussing reissuance directly with Binance. Because the attackers are unknown, the order runs against persons unknown and works through the firms holding the funds, Blockonomi reports, with Binance tracking about 26,000 addresses.
Binance said some issuers and exchanges require a formal court order before they will release frozen assets, and that the order "assists in creating that pathway", according to CoinMarketCap. The order keeps assets where they are. It is not a new freeze, and it returns nothing.
Arbitrum shows the same separation from another side. Binance's proposal asks ArbitrumDAO to release the ETH and ARB that Arbitrum's Security Council moved in October. OpCo's agenda for the DAO's 17 November governance call lists the proposal among successful off-chain votes. On-chain approval and release remain unconfirmed in the sources reviewed. The proposal itself says it will not be submitted on-chain, and no delivery will be made, while "any restraining notice, writ, order or other legal process" prohibits the transfer. Whether the Abu Dhabi order covers these particular assets has not been established.
Arbitrum's release process requires governance approval and compliance with legal conditions. Separately, the Abu Dhabi order requires companies to maintain restraints on assets linked to the theft. Neither development establishes that funds have been returned to Binance.

Trusted Channels, Again
Ledger's hardware. Bitquery traces thefts on 14 and 16 November from Ledger Flex and Stax devices that their owners say were bought in Dubai and Berlin. It traces a single thief emptying 16 wallets across Tron, Bitcoin and Solana, worth about $1.68M at the prices when the coins moved. About $922K of that belongs to the three owners who went public. About $759K came from 11 wallets whose owners have not reported losses.
Ledger's 18 November update links the Berlin devices to the same case as the tampered devices it disclosed in Southeast Asia in October, Bitquery reports, and says Ledger is checking two reports from Dubai. Bitquery notes that Ledger's Genuine Check verifies only the device's security chip, so it cannot detect an added board that reads the screen. It also traces a Tron address used by the October thief that paid network fees for two of the drained wallets, and calls that a money link, not proof of control. Ledger's reported confirmation of tampered Berlin devices does not establish that those devices caused the particular thefts Bitquery traced, a limit Bitquery's investigation also keeps.
Optimizely's scripts. A separate attack used a different trusted channel. Researchers at Report URI found malicious code in 188 of 1,611 code snippets they examined, belonging to 178 organisations and served from Optimizely's own domain. The code tried to swap crypto addresses, steal credentials and attack iPhones. Ledger's website was reportedly among those affected, along with IG and OANDA, Decrypt reported. That concerns a website, not Ledger's devices, and no Ledger response was located in the material reviewed. Report URI counted about $7,150 received by the attacker's wallets by early 17 November, a snapshot of incoming funds rather than a count of victims' losses.
Optimizely said a vulnerability let an unauthorised party add JavaScript to some customer projects, and that it had fixed the flaw and removed the code. A spokesperson told technology news site Gizmodo that the flaw was in its account signup flow. The company has not explained how that flaw gave the attacker access to other customers' projects.
Two Vaults, Three Measures
K3 Capital. Between 12:25 and 12:33 UTC on 18 November, about $3.42M left K3 Capital's sBOLD vault in 97 transactions from six wallets, Bitquery reports. Early alerts described a self-liquidation attack. Bitquery says no positions in Liquity, the lending protocol beneath the vault, were liquidated. Bitquery and CoinDesk describe collateral that the vault's share price did not count: attackers bought shares cheaply, converted that collateral so it was counted, and redeemed at the inflated price. The flaw was in K3's vault, not in Liquity's core protocol.
Much of the money did not stay with the attackers. A copycat bot took about $1.91M, 56 per cent of the total, but paid most of it to the Ethereum block builders who placed its transactions, CoinDesk reports. Bitquery counts about $1.78M paid to builders. The original attacker and a wallet it funded kept about $520,000. Those three figures describe how the money was split, not three separate losses.
Kava. At about 04:01 UTC on 14 November, an attacker began draining Kava's HARD Lend, The Block reports, by driving a dormant BUSD market's supply close to zero and inflating the value of deposits about 243,000-fold. The attacker then borrowed KAVA 127 times against that collateral. Kava puts the amount taken at about 53.9M KAVA, RootData reports. The Block's 55.2M is gross borrowing: Bitquery's breakdown shows about 1.3M was repaid on behalf of other borrowers.
About 49.2M KAVA crossed to BNB Chain through LayerZero and was sold for about $2.09M, according to The Block. Kava paused its Axelar bridge at 14:05 UTC, though the drained tokens had used a different bridge. Bitquery also found 612,416 USDT sent to an order on the routing service Relay that was marked as a blocked wallet, with no payout and no refund at the time it checked. That is a blocked order, not an issuer freeze or a recovery. Kava says no new KAVA was created, user deposits were largely unaffected and some stolen funds were frozen. Kava says it is accelerating HARD Lend's retirement. Proposal 223 entered voting on 16 November and would set borrowing caps to zero while restoring the $10 minimum. Voting is scheduled to end on 23 November.
Regulation at the Gate
Coins.ph stopped supporting self-custody transfers. From 19 November, the Philippine exchange limits external crypto deposits and withdrawals to accounts at regulated exchanges, its support notice says. Transfers to and from self-custody wallets are no longer supported. Every external transfer is checked, whatever the amount: recipient details before a withdrawal is sent, sender details before a deposit is credited. Funds are held until those checks clear, and the notice does not state how long that can take. Transfers within Coins.ph are unaffected, and the platform's deposit and withdrawal APIs have changed.
Coins.ph frames the change as Travel Rule compliance and cites earlier rules from the Philippine central bank. The notice does not show that those rules require a blanket end to self-custody transfers. This is one platform's transfer policy, not a national ban.
Hong Kong listed Hyperliquid. On 18 November, Hong Kong's Securities and Futures Commission added "Hyperliquid / Hyperliquid Hong Kong" to its alert list of suspicious virtual asset trading platforms. The list warns investors about platforms the regulator has concerns about. It is not a finding of fraud.
MEXC paused its card. MEXC's Global Card was temporarily suspended from 16 November because of "service adjustments at a third-party card issuer", according to the exchange's notice as reported by SpendNode. MEXC estimated three to five days and said balances could be moved to its fiat account. That estimate is not a confirmed reopening.
OFAC designated scam backers. On 19 November, the Treasury designated three people and two companies it says supported Southeast Asian scam operations. The same day's OFAC update separately listed a Tron address under a different sanctions programme. Treasury says property covered by the designations is blocked and must be reported. That is a legal blocking obligation, not evidence that an issuer executed an on-chain freeze.
Peraire-Bueno brothers acquitted. On 16 November, US District Judge Jessica G. L. Clarke of the Southern District of New York acquitted Anton and James Peraire-Bueno, finding the prosecution had failed to prove the material misrepresentations its fraud charges required. The order addresses what the government proved about their 2023 Ethereum trades, Reuters reported. It does not declare such trading lawful.
Security Intelligence
B18TimeBank: The Defiant, citing security firm Blockaid, reported that an attacker withdrew about 404,540 USDC from B18TimeBank's settlement contract on Base on 17 November. SlowMist says signed reward vouchers were redeemed in a single transaction. About 106,785 USDC remained in the contract at a later check; that does not show the incident is contained or that funds can be recovered.
Gonka: security firm SlowMist says attackers rotated the signing key of Gonka's Ethereum bridge on 18 November, drained about $884,800 in USDT and USDC reserves and minted unbacked WGNK. It puts the total at about $1.05M; how the remainder was valued has not been explained. SlowMist says the network's consensus was unaffected.
Pool Party: in a statement on 13 November, Pool Party said an attacker had altered position records in its snapshot contracts, deposited 10 USDC and withdrawn about $215,000 from 12 pools on Arbitrum and three on Base, according to an archived copy of the team's post. The attack itself took place early that morning, before this report's window opened. The team says it has fixed the flaw.
Luxor: the mining pool operator said attackers made unauthorised configuration changes through its Commander management software on 14 November, affecting just over a dozen customer accounts, Bitcoin.com reported. Chief executive Nick Hansen told The Block about 13 EH/s of hashrate was affected. Luxor says it patched the flaw within two hours and will compensate customers. It called the attack AI-enabled but has not described how.
Fluidkey: the privacy wallet told users on 19 November not to use its website or app after a security incident, The Defiant reported. The reporting reviewed for this edition contains no loss figure or explanation of the cause from Fluidkey.
XMR1: a wrapped Monero token on Hyperliquid fell about 99 per cent on 20 November after a wallet linked to its issuer received about 5.2M tokens and sold about 364,000 of them for about $13.5M, CoinDesk reported at 08:04 UTC. Millions of the received tokens were not sold. What caused the sale has not been established.
vCenter: Mandiant disclosed on 19 November a flaw in VMware vCenter that let an unauthenticated attacker obtain an administrator session, exploited since early September by a group it calls ARMORY CASTLE. No crypto victim has been identified.

Weekly Freeze Ledger
26 freezes • $33.13M frozen
The ledger runs on its own Saturday-to-Friday period, separate from the report's news window. It covers Saturday 14 November through Friday 20 November 2026, counting issuer-enforced freezes of $200K or more across Ethereum, Tron and XRPL. Each row covers the 24 hours ending at 21:00 UTC on that date.
| Date | Freezes | Frozen |
|---|---|---|
| Sat 14 Nov | 7 | $11.14M |
| Sun 15 Nov | 0 | $0 |
| Mon 16 Nov | 2 | $621.0K |
| Tue 17 Nov | 10 | $16.10M |
| Wed 18 Nov | 3 | $3.38M |
| Thu 19 Nov | 1 | $457.9K |
| Fri 20 Nov | 3 | $1.43M |
| Weekly total | 26 | $33.13M |
The ledger recorded 26 freezes worth $33.13M, compared with 13 worth $34.97M in the previous edition: the count doubled while the value frozen fell about 5.3 per cent. Tuesday and Saturday together contributed about 82 per cent of the week's value. Tuesday's ten freezes, worth $16.10M, included nine at 16:16 UTC, the largest of them $9.90M. Tether accounted for 25 of the week's freezes and Circle for one; 22 were on Tron, four on Ethereum and none on XRPL. No qualifying freezes were logged for Sunday. The digests do not establish what any of these freezes relate to.
Daily amounts are rounded as published in the digests; the weekly total sums those rounded figures.
These figures count freeze actions. They do not show how much remains frozen or how much was later recovered.
Source: The Cipher Index Stablecoin Freeze Tracker
What to Watch
- Lighter: How the Security Council returned about $5M, and how that sum relates to the 10.39M withdrawn.
- Binance: The 1 December hearing in Abu Dhabi, the text of the court's orders, and whether the remaining networks reopen as targeted.
- ArbitrumDAO: Whether Binance's release request goes to an on-chain vote, and whether any legal restraint applies to those assets.
- Ledger: The outcome of its checks on the Dubai reports, and how buyers can tell whether a device has been altered.
- Kava: The result and implementation of proposal 223, guidance for remaining positions and further recovery disclosures.
- Coins.ph: How long verification holds last in practice, and what happens to deposits sent from self-custody wallets.
- HyprEarn and Fluidkey: Root causes, affected accounts and losses.
Corrections and Continuing Investigations
Clarification, 22 November: This report originally attributed the withdrawal pause to Lighter's Security Council. Lighter's post-mortem says its smart contract Guardian was triggered by an anomaly and temporarily paused withdrawals, allowing the council to return about 5M USDC.
Optimizely: researchers' wallet counts have changed as their tracing was revised, so the figures above are snapshots of funds received, not totals of victims' losses.
Further Reading
- Through the Front Door, the previous Nexus Report
- Bitquery on the Lighter withdrawal
- Bitquery on the Ledger Dubai and Berlin thefts
- Report URI on the Optimizely compromise
- Binance's release proposal to ArbitrumDAO
Published by the Zero Trust Network. Research supported by CipherBot and CipherIndex.


Discussion