Through the Front Door
Web3Auth's rescue of exposed Keplr wallets was initially mistaken for theft. Elsewhere, attackers used trusted software releases and stolen developer credentials. Unocoin reported transactions signed outside BitGo's platform despite its account freeze.
On Saturday 7 November, Keplr warned of unauthorised transactions in wallets set up with Google and Apple logins. Not all the funds leaving those wallets were stolen. Web3Auth, the login provider behind them, moved some to safety before an attacker could reach them. Blockchain analytics firm Bitquery initially mistook the rescue sweeps for theft, then corrected its report the next day. Elsewhere, attackers used trusted release systems, stolen developer credentials and wallet signing mechanisms to reach funds and sensitive data.
Week in 60 Seconds
- Keplr and Web3Auth: a Web3Auth flaw exposed keys for some Keplr social-login wallets. Web3Auth moved funds to recovery addresses; separately, Bitquery estimates that attackers stole at least $1.82M.
- Supply chains: Swarm shipped a malicious release that investigators say carried authentic provenance, and stolen GitHub credentials pushed secret-stealing payloads into thousands of repositories.
- Vendors: Fireworks AI expanded its disclosure of an October breach, and Notion disclosed the exposure of Insights chat transcripts.
- Unocoin: the Indian exchange says transactions were signed outside BitGo's platform despite an account freeze, and points to suspected exploitation of its multisig backup mechanism.
- Binance: the exchange said it had completed replenishment of the stolen assets, the DOJ said more than $2.7B had been frozen, including more than $1.2B under court-authorised seizure or restraint, and Elliptic traced funds still moving.
- Regulators: South Korea moved to permit precautionary blocks when hacking is suspected, and FinCEN set a date to cut MEXC off from US institutions.
- Freeze Ledger: 13 freezes worth $34.97M, against 28 worth $76.48M in the previous edition.
When the Rescue Looked Like Theft
According to The Block, a flaw in Web3Auth's systems exposed the private keys of some Keplr users who had signed up with a Google or Apple account. Keplr said its own code had not been hacked, and that users who set up their wallets with a recovery phrase or a hardware device were not affected. Keplr's co-founder, Josh Lee, estimated that about 20 per cent of its Google and Apple login accounts were affected, and said only a fraction of those were exploited.
Web3Auth placed its login service into maintenance from 18:30 UTC on 6 November, citing a security incident. Bitquery dates Web3Auth's first rescue sweep to 20:52 UTC that evening, moving funds out of vulnerable wallets the attacker had not yet reached; by its count, about $1.01M had already been taken by then. Early on 8 November Web3Auth published 12 recovery addresses. Reviewing on-chain data, The Block found those addresses held about $5.6M on 8 November. Web3Auth said it was working with Keplr on a way to return funds to users, without giving a timetable.
An outgoing transfer alone does not establish whether funds were stolen or moved to safety. Bitquery says its first report, on 7 November, counted about $6M in Web3Auth rescue sweeps as theft. It corrected that account on 8 November. In its 12 November revision, Bitquery estimates that at least $1.82M was stolen, dates the first visible theft to 1 November and says the attacker remained active through 12 November. Security firm SlowMist's incident list gives $6.01M; what that figure counts has not been established.
Recovery balances and theft estimates measure different things. Recovery-address balances show what Web3Auth moved to safety. Bitquery's figure is an investigator's lower bound on what the attacker took. Neither is a final loss figure, and neither company had published one by our reporting cutoff.
A wallet can be emptied by its rescuer. The chain does not record intent.

Signed, Published, Trusted
Swarm. On 9 November a malicious version of @ethersphere/bee-js, a JavaScript library for the Swarm storage network, reached npm, along with a malicious Swarm Desktop release. Socket says Swarm's own release automation published both, so the packages carried authentic provenance and the macOS build was signed and notarised. Socket puts the npm release at 00:09:50 UTC and its removal at 01:24:58 UTC. SafeDep describes the payload as stealing wallet keys and installing persistent remote access. The sources reviewed for this report give no confirmed loss total.
Provenance showed that the packages came from Swarm's pipeline. It could not show that the pipeline was under Swarm's control.
GitHub. Between 10 and 12 November, attackers used stolen GitHub credentials to add malicious workflows and npm install scripts to repositories. These were designed to steal secrets and reach cloud accounts. The two investigators count different things. SafeDep says malicious commits appeared in 8,093 repositories between 12:46 UTC on 10 November and 04:36 UTC on 12 November. Aikido reports 4,837 compromised accounts and at least 1,835 payload runs that exfiltrated data. These are separate measures, not a single count of victims.
Fireworks AI and Notion. Fireworks, an AI inference provider, says an incident at a third-party cloud provider on 23 October gave attackers access to its development machines the next day. Its expanded disclosure, updated on 9 November, says the exposed data also included account and billing information and, for a limited set of accounts, secrets, datasets and incomplete models.
Notion, which describes the incident as involving a third-party AI vendor, says fewer than 1 per cent of its workspaces were affected and that the exposed data included chat transcripts from its Insights feature. It says it contacted affected customers on 9 November and, on 11 November, revoked exposed Notion API keys found in affected messages.
A Freeze That Did Not Reach the Keys
Unocoin, an Indian exchange, says it detected unauthorised activity on 6 November and asked BitGo and Fireblocks to freeze its enterprise accounts that day. It says both providers confirmed the freezes. After further unauthorised activity on 9 November, it suspended all services.
On 12 November it found outgoing transactions from an ETH address in its BitGo wallet infrastructure. According to Unocoin, BitGo found that the freeze worked as intended and that the transactions were signed and broadcast on-chain without using BitGo's platform. Unocoin suspects its multisig backup mechanism was exploited. BitGo gave The Block the same explanation: user and backup keys held by Unocoin had signed the transactions externally.
Unocoin has not disclosed a loss figure. It says the loss and the scope of any information exposure are still under investigation, that it has received the information it requested from BitGo, and that more than 90 per cent of customer crypto is held in cold storage. Bitquery, in an investigation published at 11:00 UTC on 13 November, traces about $182,000 taken from one BitGo wallet on Ethereum between 9 and 11 November, in ETH and 95 tokens. That is Bitquery's estimate, not a figure from Unocoin.
According to BitGo, the freeze stopped transactions through its platform. Unocoin's user and backup keys could still be used to sign transactions outside it.
Covered, Restrained, Still Moving
In an announcement published on 12 November, Binance said it had completed coverage of the assets affected by the October theft, committing more than $6.34B of company funds drawn from part of its SAFU fund, its futures insurance surplus and its corporate treasury. It took a new reserve snapshot covering 198 tokens at 00:00 UTC on 12 November and said the proof would take about 40 to 50 hours to generate. It has committed to refilling SAFU to about $1B.
On 12 November the Justice Department said that more than $2.7B linked to the theft had been frozen, including more than $1.2B subject to court-authorised seizure or restraint. The two figures overlap, and neither represents funds returned to Binance. In a separate action, the FBI disrupted FaceStealer, a campaign that used compromised accounts and fake video calls to install malware, and which it links to more than $400M in thefts over about 18 months.
Blockchain analytics firm Elliptic, in an update at 07:30 UTC on 13 November, reports that about 4,100 BTC, worth about $285M, has so far been converted from other stolen assets, and that since 8 November about 11,000 ETH, worth about $21M, has gone into Tornado Cash. Those are Elliptic's flow estimates.
On Arbitrum, the Foundation's governance roundup lists Binance's request to release the funds the Security Council moved as a temperature check ending on 16 November. That is a vote in progress, not an approval.

Regulation at the Gate
South Korea moved to permit precautionary blocks. In a release on 12 November, the Financial Services Commission called on crypto operators to monitor continuously, and to limit deposits and withdrawals to monitored hours where continuous coverage is not available. It said it plans to issue a no-action letter permitting precautionary suspensions when hacking is suspected. That is guidance and a planned letter, not new legislation. The decision follows GOPAX's suspension on 6 November: the exchange halted deposits and standard withdrawals at 05:55 UTC and trading at 06:53 UTC after a hacking-threat email, and said it would move all crypto to offline wallets, Cointelegraph reported. GOPAX said no hack or theft had occurred.
The US set a date to cut off MEXC. FinCEN's order, announced on 6 November, prohibits covered US financial institutions from processing transfers to or from MEXC Global, which FinCEN alleges processed at least $16B in illicit transactions. The published order takes effect on 10 December. KuCoin says it is already declining outbound transfers to MEXC entities and holding inbound deposits for compliance review, without stating a review period. Separately, FinCEN and the Federal Reserve withdrew a proposal to change Travel Rule thresholds for cross-border and virtual-currency transfers.
Poland's Sejm passed a sanctions bill covering crypto-assets. The process record shows bill 3003 passed its third reading on 6 November by 240 votes to 202, with crypto-assets as defined under MiCA counted as funds. The bill is now before the Senate, which referred it to two committees on 9 November.
The UK moved to narrow stablecoin licensing. On 10 November the House of Lords debated the Financial Services and Markets Act 2000 (Cryptoassets) (Miscellaneous Amendments) Regulations 2026. According to the Treasury's policy note, the amendments would remove UK-issued qualifying stablecoins from the regulated activities of dealing and arranging deals in cryptoassets, while lending and borrowing involving them would stay regulated. These are amendments before Parliament, not rules in force.
Coinbase's national trust charter took effect. The OCC record shows Coinbase's national trust charter, approved on 2 April, became effective on 6 November. Coinbase announced the launch on 9 November.
Security Intelligence
Arcus: Arcus says an inflated subaccount balance let 2,234,391 USDG be withdrawn early on 10 November. Rate limits held back about $3M of further requests, which were unpaid and reversed. By Arcus's account, withdrawals were suspended at 04:07 UTC, a fix followed at 04:37 and withdrawals reopened at 09:26. It says its treasury covered the shortfall.
Initia: in its second incident in under three weeks, following an exploit in late October, Initia attributed forged withdrawals from five rollups to a compromised cloud provisioning key. It halted its L1 at 06:18 UTC on 10 November. By Initia's account, about $3.27M moved from escrow to an attacker's address, of which about $2.16M remained on the paused L1. The $2.16M is included in the $3.27M.
Across: a domain hijack on 10 November, reportedly through social engineering at the registrar, redirected users to a phishing site. It was not a contract exploit. Bitquery now traces $401.9K from nine wallets, revised up from about $348K.
Ankr: security firm Blockaid said on 9 November that an attacker had submitted five withdrawals from Ankr's Ethereum bridge, using a small Optimism deposit, and initially estimated the loss at about $292,000. crypto.news prices the assets moved at about $303,600, excluding two tokens it could not price. Ankr had not commented, and how the attacker obtained valid authorisation has not been established.
Rujira: according to a 0xCERT advisory citing Rujira's update, an attacker exploited a flaw in its concentrated liquidity calculations on 10 November, taking about $200,000. Most came from one liquidity provider's positions. Rujira said it would reimburse all losses. THORChain's CosmWasm application layer, which runs Rujira, was halted.
ACryptoS: the protocol says a short input array undervalued vault holdings on 8 November, producing excess shares, with about $665,429 taken across 77 vaults. Deposits were disabled, withdrawals stayed open and the protocol is being wound down.
LNbits: v1.7.0 is an urgent security release after attacks disclosed on 8 November. LNbits says updating alone cannot remove an attacker who already has access, and operators must replace exposed keys and secrets.
NEAR AI: NEAR AI says a remote code execution flaw in SGLang exposed account details for about 100 users and two customers' API keys, and that requests processed on 8 November inside its confidential computing environment might have been observable.

Weekly Freeze Ledger
13 freezes • $34.97M frozen
The ledger runs on its own Saturday-to-Friday period, separate from the report's news window. It covers Saturday 7 November through Friday 13 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 7 Nov | 0 | $0 |
| Sun 8 Nov | 0 | $0 |
| Mon 9 Nov | 6 | $25.22M |
| Tue 10 Nov | 1 | $501.6K |
| Wed 11 Nov | 3 | $7.11M |
| Thu 12 Nov | 3 | $2.14M |
| Fri 13 Nov | 0 | $0 |
| Weekly total | 13 | $34.97M |
The ledger recorded 13 freezes worth $34.97M, compared with 28 worth $76.48M in the previous edition. Monday had both the highest count and the highest value, with six freezes worth $25.22M; five of them, all USDT on Ethereum, came at 19:25 UTC and totalled $24.35M. Tether accounted for 10 of the freezes and Circle for three; eight were on Ethereum, five on Tron and none on XRPL. No qualifying freezes were logged for Saturday, Sunday or Friday. 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
- Web3Auth and Keplr: A published process for returning recovered funds, and a final count of wallets affected and funds stolen.
- Swarm and GitHub: Swarm's own post-mortem on how its release automation was compromised, and GitHub's response to the wfx campaign.
- Unocoin: The amount moved, the outcome of its investigation into the suspected multisig backup exploitation, and a date for restoring services.
- Binance: The proof for the 198-token snapshot, the refill of SAFU to about $1B and the final investigation report.
- ArbitrumDAO: The Snapshot result on Binance's release request, and the on-chain vote the proposal sets out as its next step.
- South Korea: The no-action letter on precautionary blocks, and how exchanges use it.
- MEXC: The 10 December start of FinCEN's order, and how other exchanges treat transfers to and from MEXC before then.
Corrections and Continuing Investigations
BTCPay Server: our previous report did not cover BTCPay Server's security advisory of 2 November, which identifies versions 2.4.1 and earlier as affected by hot-wallet thefts. The Hacker News, citing Bitquery, reported sweeps from 30 October totalling about $1.62M. The advisory itself gives no total.
Chainalysis: in its update at 18:50 UTC on 7 November, the company said Reactor, KYT and Address Screening were back online. Its update at 08:00 UTC on 10 November said Data Solutions was also back online. It has not said that every exposed token has been invalidated.
Mercado Bitcoin: the exchange said view-only web access would resume on 9 November. It says withdrawals and transfers return in later stages, after customers revalidate through its app; it has not given a date.
Polygon: the recovery fork proposal still shows no approval, client release or activation block on the proposal page.
Optimism: the reported transfer of 44M OP still rests on Elliptic's account.
Further Reading
- The Off Switch, the previous Nexus Report
- Bitquery on the Keplr wallet theft
- Socket on the bee-js compromise
- SafeDep on the wfx GitHub Actions credential stealer
Published by the Zero Trust Network. Research supported by CipherBot and CipherIndex.


Discussion