← Radar

Incident case file

Sign in to watch

WEMIX$ Proxy Re-Initialization Exploit — DIOS/AMA Contract Takeover

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

1 views

ContainedWEMIX3.0 (bridged to EthereumBSC)Proxy re-initialization / logic flawCluster: WEMIX-PROXY-2026-07

Estimated loss

$758K

Victims identified

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

Investigation

100%

Facts and investigation

Ledger

Attacker

MISSING — WEMIX confirms attacker addresses were identified internally and blacklist requests were sent to exchanges, but addresses are not publicly disclosed while a criminal complaint is under investigation (filed July 28, 2026, 04:00 UTC).

Funds moved to

The abnormally minted WEMIX$ was converted into 30,736 WEMIX and 724,198.27 USDC.e (official post-mortem figures: 723,244.4936 USDC.e and 34,752.3199 WEMIX transferred out by the attacker). These converted assets were bridged out to Ethereum and Binance Smart Chain, then swapped into assets including ETH and USDT. A portion of the funds subsequently reached centralized exchanges; WEMIX requested asset freezes from the relevant exchanges and stablecoin issuers, and some associated addresses have

Linked

Affected contracts: DIOS (designed to maintain WEMIX$ price stability) and AMA (designed to redeem WEMIX$ for collateral assets at a 1:1 ratio), both originally deployed October 2022 under an upgradeable proxy pattern, with a third upgrade in November 2022 that introduced the re-initialization flaw. Both contracts were no longer in active use under WEMIX$'s termination plan at the time of the exploit. Contract addresses for DIOS and AMA on WEMIX3.0 were not located in public sources at time of w

Chronology

1 beat
  1. T0 — July 26, 2026, 18:17 KST (09:17 UTC): In a single transaction, the attacker exploits a proxy re-initialization vulnerability affecting the DIOS and AMA contracts. Root cause (per WEMIX's official July 30 post-mortem): DIOS and AMA used an upgradeable proxy pattern where the owner address is set via an initialize() function that should only be callable once. During the third contract upgrade in November 2022, a code change altered the execution restriction on initialize(), permitting a second call. Because upgrading the implementation did not automatically re-run initialize(), the initialization counter remained at one, and no separate access control was applied to a second call — allowing any network participant to call initialize() again and register a new owner address. The attacker called initialize() a second time on both contracts, changing ownership to a malicious contract they had deployed, then authorized that contract to call mint and redeem functions. By alternating between AMA's redeem function and DIOS's price-adjustment minting logic across nine cycles of flash loans and swaps, the attacker minted 5,225,524.9997 WEMIX$ without authorization. T+detection: WEMIX's internal monitoring first flags abnormal movements in game token prices, triggering investigation. ~16:30 UTC: WEMIX publicly acknowledges abnormal WEMIX$ transactions. ~01:20 UTC July 27: WEMIX suspends all bridges connected to WEMIX3.0 (including Chainlink CCIP and the PLAY Bridge), pauses the WEMIX$ swap module, PNIX DEX, and multiple liquidity pools (WEMIX-USDC.e, WEMIX-WEMIX$, CROW-WEMIX$, TIPO-WEMIX$, PLAY-WEMIX$), and withdraws Foundation-provided liquidity. Some global exchanges independently suspend WEMIX deposits/withdrawals as a precaution. July 28, 2026, 13:00 KST (04:00 UTC): WEMIX files a formal criminal complaint with law enforcement and begins full cooperation, providing collected on-chain analysis data. July 30, 2026: WEMIX publishes a complete root-cause analysis and response update, confirming the technical vector, current asset-freeze status, and a comprehensive contract-review plan; this is the second major WEMIX security incident in roughly 17 months, following a ~$6M Play Bridge Vault exploit in February 2025.

Sources and coverage

Victim testimonies

No testimonies yet.

+ Add my testimony → (coming soon)