On June 2023, DEPUSDT_LEVUSDC was exploited in a access control, resulting in approximately $105K in losses. That makes the DEPUSDT_LEVUSDC exploit the 211th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the DEPUSDT_LEVUSDC Access Control Played Out
Exploit Class Applied to DEPUSDT_LEVUSDC
The DEPUSDT_LEVUSDC incident on June 15, 2023 is classified as a Access Control. A privileged function lacks a proper authorisation check, letting an unauthorised caller execute it. In the full archive, DEPUSDT_LEVUSDC is 1 of 77 documented access control incidents.
DEPUSDT_LEVUSDC in Context
At $105K, the DEPUSDT_LEVUSDC exploit is a minor (<$1M) event compared to the largest same-class incident in our archive — Corkprotocol (2025) at $12M.
Prior Access Control Before DEPUSDT_LEVUSDC
The nearest access control incident before DEPUSDT_LEVUSDC was Local Trade LCT, 22 days earlier on May 24, 2023. The same exploit class surfaced again within the access control attack surface.
DEPUSDT_LEVUSDC Vulnerability Signature
The primary source categorises the DEPUSDT_LEVUSDC exploit specifically as “Incorrect access control”. This narrower label is entity-specific: it reflects how the DEPUSDT_LEVUSDC contract failed, rather than the broad access control pattern alone.
Impact & Recovery for DEPUSDT_LEVUSDC
DEPUSDT_LEVUSDC Loss Figure
The DEPUSDT_LEVUSDC exploit caused $105,000 in losses — a minor (<$1M) incident and the 83rd largest of 214 documented in 2023.
Where DEPUSDT_LEVUSDC Sits Among Access Control Attacks
Ranked by loss size, DEPUSDT_LEVUSDC is the 23rd largest of 77 access control incidents documented. That puts the DEPUSDT_LEVUSDC loss below the class average of $636K.
Timeline Since the DEPUSDT_LEVUSDC Incident
The DEPUSDT_LEVUSDC exploit occurred 2.8 years ago (1,034 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for DEPUSDT_LEVUSDC
Public post-mortem / on-chain analysis for the DEPUSDT_LEVUSDC incident: view source.
FAQ
How much did DEPUSDT_LEVUSDC lose?
The DEPUSDT_LEVUSDC exploit in June 2023 resulted in $105,000 in losses — the 83rd largest of 214 DeFi incidents that year.
When did the DEPUSDT_LEVUSDC hack happen?
The DEPUSDT_LEVUSDC exploit was recorded on June 15, 2023 — 1,034 days ago.
What type of exploit hit DEPUSDT_LEVUSDC?
The DEPUSDT_LEVUSDC 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 DEPUSDT_LEVUSDC?
Our archive contains 77 documented access control incidents. The DEPUSDT_LEVUSDC incident is one of them.
How does DEPUSDT_LEVUSDC compare to the largest Access Control attack?
The largest access control incident in our archive is Corkprotocol (2025) at $12M. The DEPUSDT_LEVUSDC loss is $105K.
What are the key dimensions of SRQ analyzed?
Availability, credibility, and strategic anchorage.
What role does Blockchain technology play in customer loyalty programs within the tourism sector?
Blockchain can streamline loyalty programs, making them more secure and verifiable.