On September 2024, Unverified_766a was exploited in a access control, resulting in approximately $100 in losses. That makes the Unverified_766a exploit the 450th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the Unverified_766a Access Control Played Out
Exploit Class Applied to Unverified_766a
The Unverified_766a incident on September 18, 2024 is classified as a Access Control. A privileged function lacks a proper authorisation check, letting an unauthorised caller execute it. In the full archive, Unverified_766a is 1 of 77 documented access control incidents.
Unverified_766a in Context
At $100, the Unverified_766a exploit is a minor (<$1M) event compared to the largest same-class incident in our archive — Corkprotocol (2025) at $12M.
Prior Access Control Before Unverified_766a
The nearest access control incident before Unverified_766a was Unverified_5697, 5 days earlier on September 13, 2024 ($12K lost). The same exploit class surfaced again within the access control attack surface.
Impact & Recovery for Unverified_766a
Unverified_766a Loss Figure
The Unverified_766a exploit caused $100 in losses — a minor (<$1M) incident and the 135th largest of 188 documented in 2024.
Where Unverified_766a Sits Among Access Control Attacks
Ranked by loss size, Unverified_766a is the 59th largest of 77 access control incidents documented. That puts the Unverified_766a loss below the class average of $636K.
Timeline Since the Unverified_766a Incident
The Unverified_766a exploit occurred 1.6 years ago (573 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for Unverified_766a
Public post-mortem / on-chain analysis for the Unverified_766a incident: view source.
FAQ
How much did Unverified_766a lose?
The Unverified_766a exploit in September 2024 resulted in $100 in losses — the 135th largest of 188 DeFi incidents that year.
When did the Unverified_766a hack happen?
The Unverified_766a exploit was recorded on September 18, 2024 — 573 days ago.
What type of exploit hit Unverified_766a?
The Unverified_766a incident is classified as a Access Control. A privileged function lacks a proper authorisation check, letting an unauthorised caller execute it.
How common is the Access Control pattern seen at Unverified_766a?
Our archive contains 77 documented access control incidents. The Unverified_766a incident is one of them.
How does Unverified_766a compare to the largest Access Control attack?
The largest access control incident in our archive is Corkprotocol (2025) at $12M. The Unverified_766a loss is $100.
Why are adversarial attacks on time series classification a significant concern?
They exploit vulnerabilities in deep learning models, leading to incorrect predictions.
What is the significance of the 'Lachesis' consensus algorithm in Fantom's performance?
Lachesis enables faster consensus without the energy-intensive processes typical of PoW or round-based PoS schemes.