On August 2024, Unverified_667d was exploited in a access control, resulting in approximately $10K in losses. That makes the Unverified_667d exploit the 383rd largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the Unverified_667d Access Control Played Out
Exploit Class Applied to Unverified_667d
The Unverified_667d incident on August 28, 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_667d is 1 of 77 documented access control incidents.
Unverified_667d in Context
At $10K, the Unverified_667d 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_667d
The nearest access control incident before Unverified_667d was GAX, 48 days earlier on July 11, 2024 ($50K lost). The same exploit class surfaced again within the access control attack surface.
Impact & Recovery for Unverified_667d
Unverified_667d Loss Figure
The Unverified_667d exploit caused $10,000 in losses — a minor (<$1M) incident and the 113th largest of 188 documented in 2024.
Where Unverified_667d Sits Among Access Control Attacks
Ranked by loss size, Unverified_667d is the 49th largest of 77 access control incidents documented. That puts the Unverified_667d loss below the class average of $636K.
Timeline Since the Unverified_667d Incident
The Unverified_667d exploit occurred 1.6 years ago (594 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for Unverified_667d
Public post-mortem / on-chain analysis for the Unverified_667d incident: view source.
FAQ
How much did Unverified_667d lose?
The Unverified_667d exploit in August 2024 resulted in $10,000 in losses — the 113th largest of 188 DeFi incidents that year.
When did the Unverified_667d hack happen?
The Unverified_667d exploit was recorded on August 28, 2024 — 594 days ago.
What type of exploit hit Unverified_667d?
The Unverified_667d 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_667d?
Our archive contains 77 documented access control incidents. The Unverified_667d incident is one of them.
How does Unverified_667d compare to the largest Access Control attack?
The largest access control incident in our archive is Corkprotocol (2025) at $12M. The Unverified_667d loss is $10K.
What is the significance of the 'Key to the Desert' case study in understanding the Metaverse?
It highlights the practical application of AI and ML in creating a community platform that bridges digital and physical worlds, offering insights into future Metaverse developments.
What consensus mechanisms are discussed in the document?
Proof of Work (PoW), Proof of Stake (PoS), Delegated Proof of Stake (DPoS), and Practical Byzantine Fault Tolerance (PBFT) are discussed.