Loading prices…
🩸BEARISH

WEMIX Owner Contract Mints 5.2M, Freezing Network

The freeze turns a contract exploit into an exit-risk test: users must know whether funds remain withdrawable when an L2 bridge fails.

Hackers used a compromised owner contract to mint 5.2 million WEMIX stablecoins, forcing a complete network freeze. Users were told to pull funds as the incident raised a critical question for Ethereum L2s: can holders exit when the bridge layer breaks?

Why it matters

The exploit links two risks that are often assessed separately. A contract compromise can create unauthorized supply, while a bridge failure can make it difficult for users to withdraw funds from a rollup. Together, they put both asset integrity and exit access under pressure.

Market impact

The immediate impact is operational: the network freeze interrupts normal transfers and undermines confidence in WEMIX stablecoin balances. The incident also puts rollup exit design under scrutiny, with users and developers likely to focus on whether withdrawal paths remain usable when bridge infrastructure fails.

Related tokens
$WEMIX $ETH

Frequently asked questions

  1. How many WEMIX stablecoins were minted in the compromise?

    Hackers minted 5.2 million WEMIX stablecoins through a compromised owner contract.

  2. What action were crypto users told to take?

    Users were told to pull funds after the contract compromise and Ethereum L2 bridge failure exposed withdrawal risks.

  3. Why did the incident force a network freeze?

    The compromised owner contract enabled unauthorized minting of WEMIX stablecoins, prompting a complete network freeze.

  4. What rollup risk did the bridge failure expose?

    The failure raised questions about whether users can still withdraw funds when the bridge layer supporting an Ethereum L2 breaks.

  5. How could the incident affect confidence in WEMIX?

    The freeze interrupts normal transfers and puts the integrity of WEMIX stablecoin balances and the reliability of exit paths under scrutiny.

Source attribution
Aggregated from CryptoSlate · Verified · Last refreshed 1h ago
Open original →