OAK — OnChain Attack Knowledge

Worked example · 2024-04

ZKasino gambling-platform bridge-exit — Ethereum / L2s — 2024-04-20 onward

Loss
~$33M (approximately 10,515 ETH) bridged by users into the ZKasino bridge contract under the representation that the bridge would return ZKAS tokens at a 1:1 ratio against bridged ETH and that the platform would launch as a functioning gambling protocol. The bridged ETH was subsequently routed to Lido for staking rather than being returned to depositors; the ZKAS token launch and platform launch were indefinitely deferred.
OAK Techniques observed
OAK-T5.005 (Treasury-Management Exit — primary; the operator controlled the bridge contract and redirected user-deposited ETH to staking rather than to the promised bridge-return mechanism). OAK-T11.005 (Operator-side Fake-Platform Fraud — structurally adjacent; the platform's operational promise — a functioning on-chain gambling protocol with a token — constituted the acquisition surface for user deposits, but the platform did not launch). OAK-T15 (Off-chain Entry-Vector / Pre-Positioning — the platform's brand-building surface included prominent crypto-VC and influencer endorsement that produced user-side trust in the bridge-deposit mechanism).
Attribution
pseudonymous (the ZKasino operational entity was pseudonymously operated; Dutch authorities arrested a 26-year-old suspect on April 29, 2024 in connection with the case on suspicion of fraud, embezzlement, and money laundering; Binance's on-chain investigations team assisted Dutch authorities with the identification). The broader operator cohort behind the platform remained pseudonymous at v0.1 beyond the single Dutch arrest.
Key teaching point
A bridge contract whose deposit-to-return ratio is represented as 1:1 but whose operator controls the returned-asset side and can unilaterally redirect the deposited side is a standing T5.005 surface regardless of whether the deposit contract itself is immutable. The ZKasino bridge contract accepted ETH deposits and was represented as returning ZKAS at a 1:1 ratio, but the ETH was redirected to Lido staking — the operator retained control over the deposited ETH and exercised it contrary to the public representation.

Summary

ZKasino presented as a decentralised gambling and casino platform built on Ethereum Layer 2 infrastructure, with a planned ZKAS token. The platform's public narrative positioned it as "the first on-chain casino" with backing from prominent crypto venture-capital firms and endorsements from crypto influencers. The core user-acquisition mechanism was a bridge contract: users deposited ETH into the ZKasino bridge and were represented as receiving ZKAS tokens at a 1:1 ratio against their bridged ETH upon the platform's token-generation event.

Between approximately April 7 and April 20, 2024, the bridge accumulated approximately 10,515 ETH (~$33M at the time) from depositors. On or around April 20, 2024, the bridge's operators:

  1. Redirected the bridged ETH to Lido for stETH staking — the ETH was transferred from the bridge contract to Lido, where it was staked for stETH, making it unavailable for the promised 1:1 return to depositors.
  2. Removed the explicit "ETH will be returned" representation from the platform's website, replacing it with language indicating that the bridged ETH was now a "contribution" to the ZKasino ecosystem.
  3. Indefinitely deferred the platform launch and ZKAS token-generation event.

The operational sequence — accumulate deposits → redirect deposited assets to operator-controlled yield → alter the public representation of the deposit terms → defer the platform launch — is the canonical T5.005 (Treasury-Management Exit) pattern at the platform-launch layer.

The Dutch Fiscal Information and Investigation Service (FIOD) arrested a 26-year-old suspect on April 29, 2024 on suspicion of fraud, embezzlement, and money laundering. FIOD seized approximately €11.4M in assets including real estate, luxury watches, and cryptocurrency. Binance's on-chain investigations team was publicly credited by Dutch authorities with contributing to the identification of the suspect.

The platform did not launch as of the v0.1 cutoff. User-deposited ETH remained staked in Lido under operator-controlled withdrawal credentials. The ZKAS token did not reach a functioning token-generation event.

Timeline

When Event OAK ref
2024-04-07 to 04-20 ZKasino bridge accumulates ~10,515 ETH from depositors under the 1:1 bridge-return representation T5.005 surface created
2024-04-20 Bridged ETH redirected to Lido staking; platform website alters the deposit-terms representation; ZKAS token launch deferred T5.005 execution
2024-04-20 to 04-28 Crypto community identifies the bridge-redirect pattern; ZigZag Exchange (a prior ZKasino-associated project) publicly distances from the ZKasino operators; influencer-endorser scrutiny intensifies (community response)
2024-04-29 Dutch FIOD arrests 26-year-old suspect; seizes ~€11.4M in assets; Binance on-chain investigations team credited with contributing to identification (law-enforcement response)
2024-04 to 2025 Bridged ETH remains staked in Lido; platform does not launch; depositor recovery efforts continue through Dutch legal process (post-event)

What defenders observed

  • Bridge-contract deposit-to-return ratio representations are not contractually enforceable unless the return side is contractually committed at the bridge layer. ZKasino's bridge accepted ETH and the return-side token (ZKAS) did not exist at deposit time — the return was a forward promise from the operator, not a contract-enforced mechanism. The operator could redirect the ETH because the bridge contract's ETH custody was under operator control and the return-side obligation was social, not cryptographic.
  • VC / influencer endorsement does not substitute for operator-identity verification. ZKasino's brand-building surface — crypto-VC firm names cited in marketing, influencer endorsements on social media — constituted the T15 pre-positioning layer that produced user-side trust in the bridge deposit. Post-event, several cited VCs and endorsers clarified that their involvement was limited or misrepresented.
  • The ETH-to-staking redirection is the defining T5.005 signal. Rather than exiting via direct wallet drain (T5.001 pattern), the ZKasino operators redirected depositor ETH to Lido staking — converting the ETH into a yield-bearing stETH position under operator control. The staking redirection extends the exit window because the stETH remains in DeFi rather than being immediately off-ramped to fiat, and the staking yield provides ongoing operator revenue while the legal process unfolds.

What this example tells contributors writing future Technique pages

  • T5.005 is the primary classification for platform-launch bridge exits where the operator controls the deposited-asset side. The ZKasino pattern — accumulate deposits via a bridge representation, redirect deposited assets to operator-controlled yield, alter the deposit-terms representation, defer the platform launch — is structurally distinct from token-level rug pulls (T5.001 / T5.002) and from fake-exchange frauds (T11.005) because the platform's smart-contract infrastructure was partially deployed and the gambling-platform operational promise was at least notionally real rather than a pure database fiction.
  • The T11.005 adjacency is structural but secondary. ZKasino's platform did not launch, making it T11.005-adjacent (fake-platform fraud). However, the load-bearing surface for depositor loss was the operator's control over the bridged ETH combined with the alteration of the deposit-terms representation — which is T5.005's load-bearing surface (treasury-management exit) rather than T11.005's (fake platform). The distinction matters for mitigation: closing T11.005 requires regulatory-licensing enforcement; closing T5.005 requires bridge-contract-enshrined deposit-return guarantees.
  • The case anchors the "platform-launch bridge exit" sub-shape of T5.005. This sub-shape — where the bridge contract is the deposit mechanism and the platform-launch promise is the acquisition surface — is structurally distinct from the Bybit / Safe{Wallet} T11.001 sub-shape (vendor-side UI compromise) and from the Mango Markets T16.002 sub-shape (post-exploit governance settlement). Contributors writing future T5.005 technique pages should distinguish it accordingly.

Public references

  • Dutch Fiscal Information and Investigation Service (FIOD). "Suspected of fraud, embezzlement and money laundering in cryptocurrency investigation." 29 April 2024. Arrest announcement; ~€11.4M asset seizure.
  • Binance. "Binance's Investigation Team Assists Dutch Authorities in ZKasino Case." April–May 2024.
  • ZigZag Exchange. "Statement on ZKasino." April 2024. Prior-associated project publicly distances from ZKasino operators.
  • Cross-reference: T5.005 (Treasury-Management Exit) at techniques/T5.005-treasury-management-exit.md.
  • Cross-reference: T11.005 (Operator-side Fake-Platform Fraud) at techniques/T11.005-operator-side-fake-platform-fraud.md.

Proposed new BibTeX entries

@misc{fiodzkasino2024,
  author = {{Dutch Fiscal Information and Investigation Service (FIOD)}},
  title = {Suspected of fraud, embezzlement and money laundering in cryptocurrency investigation — ZKasino},
  year = {2024},
  month = apr,
  day = {29},
  note = {26-year-old suspect arrested; approximately €11.4M in assets seized including real estate, luxury watches, and cryptocurrency}
}

@misc{binancezkasino2024,
  author = {{Binance}},
  title = {Binance Investigation Team Assists Dutch Authorities in ZKasino Case},
  year = {2024},
  month = may
}

Techniques demonstrated (3)