On June 2023, SHIDO suffered a business logic flaw — the first of 144 documented business logic flaw incidents in our archive where the loss figure was not publicly disclosed but the exploit pattern is documented below.
Attack Mechanics: How the SHIDO Business Logic Flaw Played Out
Exploit Class Applied to SHIDO
The SHIDO incident on June 23, 2023 is classified as a Business Logic Flaw. A business-logic bug in the contract — such as an incorrect formula or missing state update — lets the attacker withdraw more than their share. In the full archive, SHIDO is 1 of 144 documented business logic flaw incidents.
SHIDO in Context
The SHIDO incident joins a class whose largest loss to date is – EulerFinance (2023) at $200M.
Prior Business Logic Flaw Before SHIDO
The nearest business logic flaw incident before SHIDO was Contract_0x7657, 4 days earlier on June 19, 2023 ($20K lost). The same exploit class surfaced again within the business logic flaw attack surface.
SHIDO Vulnerability Signature
The primary source categorises the SHIDO exploit specifically as “Business Logic”. This narrower label is entity-specific: it reflects how the SHIDO contract failed, rather than the broad business logic flaw pattern alone.
Impact & Recovery for SHIDO
SHIDO Loss Figure
The loss figure for SHIDO is not publicly disclosed. The primary source reports the exploit in non-USD terms, so no USD estimate is published here. For reference, the average loss across 144 business logic flaw incidents in our archive is $6.08M.
Timeline Since the SHIDO Incident
The SHIDO exploit occurred 2.8 years ago (1,026 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for SHIDO
Public post-mortem / on-chain analysis for the SHIDO incident: view source.
FAQ
How much did SHIDO lose?
The SHIDO loss figure is not publicly disclosed. The primary source reports the exploit in non-USD token terms, so no USD estimate is published here.
When did the SHIDO hack happen?
The SHIDO exploit was recorded on June 23, 2023 — 1,026 days ago.
What type of exploit hit SHIDO?
The SHIDO incident is classified as a Business Logic Flaw. A business-logic bug in the contract — such as an incorrect formula or missing state update — lets the attacker withdraw more than their share.
How common is the Business Logic Flaw pattern seen at SHIDO?
Our archive contains 144 documented business logic flaw incidents. The SHIDO incident is one of them.
How does SHIDO compare to the largest Business Logic Flaw attack?
The largest business logic flaw incident in our archive is – EulerFinance (2023) at $200M. The SHIDO loss was not publicly disclosed.
How does green bond issuance affect corporate stock prices?
Announcements of green bond issuance have a positive impact on corporate stock prices.
What does signer-linkability in SALRS prevent?
Double spending by linking signatures from the same derived public key.