Incident case

QANplatform QANX Bridge 2022 wallet hack

QANplatform states that its bridge wallet was hacked beginning on BNB Smart Chain at 08:16:39 UTC on 2022-10-11 and immediately afterward on Ethereum. The project replaced the affected QANX token contract and created a recovery and compensation process.

reviewedcurrent

Incident facts

Incident title
QANplatform QANX Bridge 2022 wallet hack
Bridge
QANplatform QANX Bridge
Incident date
2022-10-11
Incident type
Exploit
Major incident
Yes
Affected chains
BNB Chain, Ethereum
Affected assets
Unknown
Attack category
Private Key Compromise
Reported loss
No reviewed canonical source supports one reconciled stolen USD amount.
Amount confidence
High
Loss amount basis
First Party Recovery Material; Amount Intentionally Unresolved
Recovery
None Confirmed
Reimbursement
Announced
Restart
Token Replacement Planned
Current outcome
Affected Token Deprecated
Postmortem
Partial
Resolution
Unresolved
Last reviewed
2026-08-26
Last verified
2026-08-26

Amount and valuation

No reviewed canonical source supports one reconciled stolen USD amount.

Token replacement and compensation rules are documented, but this record does not infer a stolen USD total.

Why this remains unresolved

Timeline events

  • QANplatform replaces QANX token and opens compensation process2022-10

    QANplatform replaced the affected QANX token contract and published replacement and compensation rules, including 100% replacement eligibility for pre-hack holders.

    Token Replacement And CompensationHigh

    Eligibility and process are documented; final completion for every affected holder is not asserted.

  • QANX bridge wallet hack begins2022-10-11

    QANplatform identifies the bridge-wallet hack as beginning on BNB Smart Chain at 08:16:39 UTC and immediately afterward on Ethereum.

    Exploit DisclosedHigh

Evidence records

Source tiers describe evidence authority, not certainty for every claim. Tier 1 is the strongest source class; Tier 2 and Tier 3 provide progressively more secondary or supporting context. Source notes define what each record actually supports.

Known unknowns

Independent incident archive

Help maintain incident aftermath records

Support recovery, reimbursement, restart, migration, shutdown, evidence, and correction checks.

Support BIR
Record maintenance

Report a correction

Report missing evidence, incorrect dates, outcome changes, recovery details, reimbursement status, or broken links. GitHub Issues are preferred for structured review; the Google Form is available if you do not use GitHub.