Across Protocol Security Incident: What Users Should Do11 min read2,283 words

Across Protocol Security Incident: What Users Should Do

Across Protocol has warned users to avoid its app amid reports of lost funds. Learn what is confirmed, what remains unclear and how to protect your wallet.

Across Protocol security incidentAcross ProtocolDeFi bridge securitycrypto wallet safetyUSDC wallet drain
Across Protocol Security Incident: What Users Should Do

Across Protocol's Security Warning: A Practical Response for Users

When a DeFi protocol tells people to stay away from its app, the first thing to focus on isn't who to blame. It's reducing your chance of getting hit again. Across Protocol has told users not to access its app, connect wallets, or sign transactions and approvals while it investigates a potential security incident involving its domain.

The warning came after user reports that they lost funds after interacting with the platform. One person said they lost $9,000 in USDC. Another reported losing 7,053 USDT0 across seven transactions on Plasma. Those claims haven't been independently verified, and Across hasn't publicly said what went wrong or confirmed whether its website was compromised.

That difference matters. A domain problem, a malicious approval, a compromised wallet, or a protocol vulnerability can all lead to losses - but they call for different next steps. This article separates what we can reasonably say from what's still unclear, explains how a website can create risk even if the blockchain is functioning normally, and lays out a practical checklist you can follow without making things worse.

What happened at Across Protocol

Across is a crosschain bridging protocol that lets users move digital assets between Ethereum and other blockchain networks. On Tuesday, it advised users not to access its app or connect wallets while it investigated a possible security incident involving its domain. It also told users not to sign transactions or approvals until further notice.

The message was intentionally broad. Across didn't identify what it believed failed, didn't say whether its website had been compromised, and didn't confirm whether the bridge contracts were affected. In the short term, notices like this are usually about containment: stop interacting so the team can investigate and figure out what happened.

What users reported - and what is not confirmed

Multiple users posted claims of losses after using the platform. One said they lost $9,000 in USDC. Another reported losing 7,053 USDT0 across seven transactions on Plasma. A third claimed their wallet was drained after using the bridge multiple times and said the website had been compromised.

Across asked for transaction details to help with the investigation. The reports haven't been independently verified, and the protocol had not provided additional details to the news outlet at the time of reporting. A user report can be a useful early warning, but it doesn't, by itself, prove what caused the losses, how widespread the problem is, or whether other users were affected.

What you should not conclude yet

A warning about a domain isn't proof that the bridge's smart contracts were exploited. And a reported loss doesn't automatically mean every user who used the app is at risk. Other explanations are plausible here, including a compromised website, a malicious transaction or approval, a separate wallet compromise, or an issue in a third-party component. None of those are confirmed - you should treat them as possibilities, not findings.

The safe approach is to take the warning seriously without treating guesses as facts. Until Across provides a clearer update, users should avoid the app and any request that claims to be part of the investigation. If someone asks for a seed phrase, private key, or remote access to your device, that isn't legitimate recovery.

Why a domain incident can put wallets at risk

A blockchain transaction is hard to undo once it's confirmed, but the interface you use to create that transaction isn't the blockchain. A DeFi app's website helps assemble transaction data and send it to your wallet. If the site, its domain, or supporting infrastructure is compromised, an attacker might be able to mislead you with fake instructions or route you to a malicious page.

That doesn't automatically mean the attacker can take over every wallet that connects. Wallet software generally prompts you to approve or sign specific actions. The real risk is that users can be shown something that looks routine while authorizing an action they don't fully understand - like granting a token allowance or interacting with an unfamiliar contract.

Why approvals deserve attention

Token approvals let a contract spend a specified amount of a token from your wallet. Some apps request a small, limited allowance; others request a larger or effectively unlimited allowance for convenience. Either way, the approval is a separate on-chain action, and it can remain active even after you stop using the app.

So connecting your wallet and signing an approval aren't the same thing. Connecting typically lets a website see your public address and request actions. Signing the transaction or approval is what changes what's allowed on-chain. If something looks suspicious, don't assume "all interactions were the same." Find the exact transaction, then check which contract received permission and for what amount.

The interface and the contracts are separate layers

A helpful way to think about DeFi risk is to separate three layers:

  • The interface: the website, domain, scripts, and services that present the app.
  • The transaction: the call or approval your wallet asks you to sign.
  • The protocol: the smart contracts and infrastructure that execute or support the operation.

A problem in one layer doesn't automatically prove a problem in the others. A website issue can lead to malicious transaction requests even if the protocol contracts never changed. And a clean-looking website can't make a vulnerable contract safe. Incident updates are most useful when they specify which layer was affected, which assets or chains are in scope, and what users should do next.

What users should do now

If you used the Across app recently, take the warning as a reason to pause and double-check - not a reason to rush into random recovery steps. Don't visit the app, connect a wallet, or sign transactions until Across publishes a clear "all good" update through a channel you can verify independently. Skip search ads, unsolicited DMs, and copied announcements - attackers often take advantage of uncertainty by pretending to be support.

A practical response checklist

  1. Stop interacting with the app. Don't "test" whether it works, don't retry a failed bridge, and don't sign a message just to check your wallet. Even if a request sounds like a diagnostic step, treat it like any other authorization.
  2. Don't share secrets. Never give a seed phrase or private key to a person, website, or "support" account. Don't install remote-access software someone asks you to use for "recovery." A real team shouldn't need your recovery phrase to investigate a transaction.
  3. Review wallet activity through a trusted route. Open your wallet directly or use a blockchain explorer you already trust. Look at recent transactions, including approvals, and note the network, token, recipient or spender address, transaction status, and timestamp. Avoid links sent by strangers "to inspect activity."
  4. If you see an unfamiliar approval, double-check it. Revoking a token allowance can reduce future exposure, but revoking itself is a transaction and may cost network fees. Use your wallet's built-in controls or an allowance-management service you reach independently. Confirm the chain and the spender/contract before signing anything.
  5. If funds are missing, save proof. Record transaction hashes, affected addresses, token amounts, networks, and approximate times. Share those details through a channel the protocol has publicly identified. Don't assume transfers can be reversed - on-chain transfers are usually final.
  6. Protect any remaining assets that might still be exposed. If you think your seed phrase or private key was exposed, moving remaining funds to a new wallet created on a secure device may be appropriate. Don't import the suspected compromised phrase into another wallet and call that "clean recovery." If the issue seems limited to an approval, first confirm what was authorized and on which network.

Why blanket revocation is not always the right move

Revoking every approval immediately can feel safer, but it can create avoidable problems - extra fees and the risk that you end up interacting with a fake "revocation" page or signing on the wrong network. If you're acting, focus on approvals you don't recognize, those tied to the affected app, and those that grant broad spending permission.

The right response depends on what you actually signed. A wallet with no relevant transaction-history changes is different from a wallet that approved a spender or submitted a transfer. If you can't interpret what happened, pause and ask for help from a trusted security professional or your wallet provider using verified contact details. Don't hand over custody of your wallet just to speed things up.

What the incident says about DeFi security

Across's warning points to a real friction in how people experience DeFi: users often treat the interface as "the product," even though it's only one part of the system. You see a familiar brand and a wallet prompt. You may not know whether the request is actually coming from the intended site, whether the transaction is going to the contract you expect, or whether an earlier approval still leaves an opening.

That's where protocol security and user security diverge. A team can audit smart contracts and still leave risk in places like domain management, software supply chains, deployment permissions, or transaction flows users interact with directly. And even if users follow good wallet hygiene, they can still get hurt by a real contract or infrastructure failure. There's no single control that removes all risk.

What a useful incident update should clarify

For users trying to decide when it's safe to return, the update should answer specific questions instead of offering vague reassurance:

  • What part was affected: the domain, app interface, contracts, infrastructure, or multiple layers?
  • Which networks, tokens, and time window are in scope?
  • Were malicious transactions or approvals identified, and what should affected users review?
  • Has the issue been contained, and what evidence supports that?
  • What is the recommended next step for users who interacted during the incident window?

These details let people make decisions based on their own transaction history. "The issue is fixed" is less helpful than a bounded explanation of what changed and how to check whether you were exposed.

Keep separate incidents separate

The same report also described a separate security disclosure from NEAR AI. That company said attackers exploited a remote code execution vulnerability in the SGLang AI inference engine, accessing internal systems and other infrastructure. NEAR AI reported exposure of account details for about 100 users and data from 18 AI agents, and said two customers' API keys were exposed. It also said the team patched the vulnerability, revoked exposed credentials, and restored cloud access.

That incident involves AI infrastructure, not the Across bridge. There's nothing in the report that links the two events. Still, the comparison can be useful in a general sense: security issues can hit different layers of a technology stack, and good disclosure should clearly state what systems were affected, what data (if any) was exposed, and what remediation occurred. Treating unrelated events as one story can confuse readers instead of helping them assess their own risk.

Key takeaways: Across advised users to stay away from its app and avoid signing transactions or approvals while it investigates. User loss reports are claims until independently confirmed. Don't interact with the app until you see a verified all-clear, and base your actions on the transactions and approvals you actually signed.

Conclusion

Across Protocol's warning is enough reason to pause, but it's not enough information to determine what caused the incident or how wide the impact is. The disciplined approach is simple: avoid the app until a verified all-clear appears, don't sign unfamiliar requests, and review your own transaction and approval history before taking further action.

For users, the important distinction is between a report, a confirmed technical finding, and a recommended remediation. Keep those separate, save evidence if you were affected, and don't let urgency push you into another risky interaction.

Frequently Asked Questions

No. Across warned users about a potential security incident affecting its domain, but the available report did not confirm that the website was compromised or that the protocol’s smart contracts were exploited. Users reported losses, but those claims were not independently verified. Treat the warning seriously while waiting for a specific incident update.
No. Across advised users not to access its app, connect wallets, or sign transactions and approvals while the investigation continues. Check wallet activity through a route you already trust, such as your wallet’s transaction history. Do not follow unsolicited links or sign a message simply to test your account.
Review the transaction on the relevant network and identify the token and spender address. If the approval is unfamiliar or grants broad spending permission, consider revoking it through a trusted wallet control or allowance service reached independently. Revocation is an on-chain transaction, so verify the chain and request before signing.
On-chain transfers are generally irreversible, so a completed transfer usually cannot be undone by the sender. Preserve transaction hashes and wallet details, report them through a verified protocol channel, and secure any assets that may still be exposed. Be wary of anyone promising guaranteed recovery in exchange for upfront payment or wallet secrets.

Related articles