← Radar

Incident case file

Sign in to watch

Triple-A Multi-Chain Hot Wallet Compromise

Incident date July 27, 2026Last updated Aug 1, 2026

5 views

RecoveringEthereumTRONPolygonArbitrumSolanaTONHot wallet compromiseCluster: TRIPLEA-HOTWALLET-2026-07

Estimated loss

$11.8M

Victims identified

more than ten victims identified
Victim group joining is coming soon.

Investigation

50%

Facts and investigation

Ledger

Attacker

MISSING — attacker identity/entry vector not publicly disclosed by Triple-A. Consolidation address on Ethereum: 0x01F83B5d4fb30E8AA3daC1681B4048D9135253b1

Funds moved to

Stolen assets were swapped and bridged across six networks (Ethereum, TRON, Polygon, Arbitrum, Solana, TON) into a single Ethereum address, 0x01F83B5d4fb30E8AA3daC1681B4048D9135253b1, holding approximately 5,227 ETH (~$9.7-11.8M depending on the reporting date). As of the most recent public reporting, the funds remained static in this address with no further outbound movement (no CEX deposit or mixer routing identified); on-chain researchers were actively monitoring the address for any change.

Linked

Singapore-based fiat-to-crypto payment gateway Triple-A (licensed under Singapore's Payment Services Regulations). Consolidated Ethereum address: 0x01F83B5d4fb30E8AA3daC1681B4048D9135253b1 (~5,227 ETH). No attacker-controlled source wallets on the individual chains (TRON/Polygon/Arbitrum/Solana/TON) have been publicly disclosed. Client funds are held in segregated trust accounts and were not affected; only the company's own treasury/hot wallet assets were compromised.

Chronology

1 beat
  1. T0 — July 24, 2026, ~21:18 UTC: On-chain analyst Specter first flags suspicious outflows from wallets linked to Triple-A, putting initial damage at approximately $9.3 million. T+~4.5h: PeckShield amplifies the alert, raising the estimate to over $9.7 million and identifying that ~5,227 ETH of bridged proceeds were being consolidated at a single Ethereum address beginning 0x01F8. Deposits into the compromised wallets were not disabled, and new incoming funds continued to be swept for at least 31 hours after the first large outflows were detected — Specter noted the team did not appear aware, since deposits remained open. July 26 (Saturday): Triple-A internally detects the breach and places certain services into maintenance mode for approximately three hours to secure infrastructure and complete checks; no public statement is issued at this point. By July 27 (Sunday), the cumulative loss figure had climbed to $11.8 million as transfers continued to be traced. July 27: Triple-A officially and publicly acknowledges the incident, stating attackers gained unauthorized access to wallets holding the company's own digital assets (not customer funds, which remain protected in segregated trust accounts under Singapore's Payment Services Regulations). The company confirms it is working with cybersecurity firms, blockchain forensics teams, and the Singapore Police Force to trace and recover the stolen assets. All services are confirmed restored and processing normally across markets. As of the most recent reporting, the consolidated Ethereum address holding ~5,227 ETH has not moved further, and 0% of funds have been recovered.

Sources and coverage

Victim testimonies

No testimonies yet.

+ Add my testimony → (coming soon)