What is confirmed

Across said an attacker gained control of its domain through a social-engineering attack on Namecheap at about 18:45 UTC on 10 November. The genuine address then served a phishing interface. Across says it learned of the incident within 15 minutes, took the frontend and API offline, and restored normal operation at 01:16 UTC on 11 November.

The project says third-party integrations and API users were not affected. That is an attributed claim pending the promised technical post-mortem.

The loss estimate is independent, not official

Bitquery traced roughly $348,000 taken from nine wallets on Ethereum, Arbitrum, Base, BNB Chain and Optimism between 19:02 and 21:53 UTC. One wallet accounted for about $305,000. Across has promised to make affected users whole but has not published its own victim count, final loss number or reimbursement process.

The attacker used signed token permissions rather than breaking the bridge contracts. That distinction matters: a phishing approval can remain usable after a website is restored.

Practical implications: what users should do

  1. If you connected to Across during the incident window, review token approvals and signed permits on every chain you used.
  2. Revoke permissions you do not recognise using a trusted block explorer or a wallet security tool reached from a saved bookmark.
  3. Check outbound transfers and preserve transaction hashes, timestamps and screenshots before contacting support.
  4. Do not follow reimbursement links in replies, direct messages or search ads. Across has not announced a public claim page.
  5. Hardware-wallet users should remember that the device confirms a signature; it cannot make a malicious permission safe.

Risks and what to watch next

The unanswered questions include how the registrar account was taken over, which controls failed, whether every malicious approval has been identified, and how compensation will be verified. The post-mortem should also explain domain-lock, transfer-lock and account-recovery controls.

Across says normal operation has resumed. Readers should treat that as the project’s operational status statement, not proof that every victim-side approval has been removed.

EVIDENCE LEDGER

Sources you can open

01
Across restoration noticeProject status, compensation commitment and promised post-mortem.
OPEN ↗
02
Across incident noticeAttack time, registrar attribution and affected-service boundary.
OPEN ↗
03
Bitquery on-chain investigationWallet count, chain coverage, timing and loss estimate.
OPEN ↗
04
Unchained incident reportIndependent chronology and distinction between project and third-party estimates.
OPEN ↗
Phishing warning

No reimbursement or wallet-connection page is linked here. Never provide a seed phrase, private key or authenticator code to recover funds.