Payy Network's Ethereum bridge drained of $1.83M USDC: what is confirmed
Payy says its Ethereum bridge contract was drained of its full balance and that the cause was not a compromised key, social engineering or its off-chain infrastructure. The root cause is still undisclosed, so here is what the public record supports and what bridge teams should check.
Key Takeaways
- On 24 September 2026 at 04:21 UTC, Payy's Ethereum bridge contract was drained of its full balance: 1,832,149 USDC, about $1.83M, per on-chain reporting.
- Payy has not published a root cause. It says the incident was not a compromised key, social engineering or an off-chain infrastructure exploit, which points at the on-chain contract logic, though that is inference, not confirmation.
- All Payy activity is paused (deposits, withdrawals, transfers and card transactions), and the company has notified law enforcement.
- 'Non-custodial' only holds if the contract's own verification logic holds. A pooled bridge contract is a single point of failure.
What happened
Payy Network, a stablecoin infrastructure company, disclosed that its bridge contract on Ethereum was exploited and drained of its full balance. Its statement placed the event at 04:21 UTC on 24 September 2026 and said the investigation was ongoing. Web3 Is Going Great logged the loss at $1.8 million.
On-chain reporting by The Crypto Times gives more detail. Blockchain investigator Specter flagged a transaction that called verifyRollup on Payy's contract and moved 1,832,149 USDC out. Almost all of it, 1,828,589 USDC, went to a single address, and two smaller transfers accounted for the rest. Specter's analysis, which that outlet notes is not independently verified, says the funds were then converted to ETH.
What Payy has and has not said
Payy stated that the loss was "NOT a compromised key, social engineering or exploit of our off-chain infrastructure". It has not said what it was. Cyber Security News notes that the company has not disclosed whether the cause was a smart-contract logic flaw, an authorization bypass, a compromised privileged key or another weakness. We do not know the mechanism, and we will not guess at one here.
Ruling out keys and off-chain systems narrows the field, but it does not identify the flaw. If the statement holds, the remaining suspects are in the on-chain code and its assumptions. That is a reading of Payy's words, not something Payy or an independent analyst has confirmed.
Why 'non-custodial' needs care
Payy described the stolen funds as users' non-custodial deposits. That label is a design claim, not a property of the pooled balance. Users can only withdraw their own funds if the contract correctly checks every state transition it is asked to accept. If one verification path can be satisfied by an input it should have rejected, the whole pool is reachable at once.
The public reporting shows the entire balance leaving through a call named verifyRollup. Whatever the root cause turns out to be, the outcome shows that one contract entry point held the whole pool. Payy also paused card transactions along with deposits, withdrawals and transfers, so the impact went beyond on-chain balances.
What bridge and rollup teams should check now
- Blast radius per call: can a single verification call move the entire pool? Consider per-transaction and per-window withdrawal limits enforced in the contract.
- Verification inputs: confirm that every proof, batch or state-root input is bound to the state the contract expects, and that nothing is accepted merely because an authorised role submitted it.
- Pause and circuit-breaker paths: test that monitoring can detect an anomalous outflow and that a pause actually stops it, and rehearse who can trigger it.
- Independent review of upgrades: re-audit any change to verification or withdrawal logic, not just the initial deployment.
- Incident readiness: pre-arrange contacts with exchanges, analytics firms and law enforcement so attacker addresses can be flagged within minutes.
What to watch next
The useful evidence will be a post-mortem from Payy or a reproduction by independent researchers naming the failing check. Until then, treat any claimed root cause as unconfirmed. Users with balances on Payy Network or Payy Wallet should follow the company's official channels for recovery and withdrawal status.
Frequently Asked Questions
How much was stolen from Payy Network?
On-chain reporting puts the outflow at 1,832,149 USDC, about $1.83M, from Payy's Ethereum bridge contract at 04:21 UTC on 24 September 2026. Web3 Is Going Great records it as $1.8 million.
What caused the Payy bridge exploit?
Payy has not disclosed a root cause. It says it was not a compromised key, social engineering or an exploit of its off-chain infrastructure. Whether it was a contract logic flaw, an authorization bypass or something else has not been confirmed.
Can a bridge holding user deposits really be non-custodial?
Only to the extent that the contract enforces who can withdraw what. Users do not hand keys to an operator, but a pooled contract with a verification flaw can still let an attacker withdraw everyone's funds at once.
Sources
- 1Payy Network bridge fully drained of $1.8 million — Web3 Is Going Great
- 2$1.83 Million in USDC Leaves Payy Network's Ethereum Rollup Contract — The Crypto Times
- 3Hackers Exploited Ethereum Bridge Contract to Drain Full Balance from Payy Network — Cyber Security News