On March 2023, – Phoenix was exploited in a access control, resulting in approximately $100K in losses. That makes the – Phoenix exploit the 214th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the – Phoenix Access Control Played Out
Exploit Class Applied to – Phoenix
The – Phoenix incident on March 7, 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, – Phoenix is 1 of 77 documented access control incidents.
– Phoenix in Context
At $100K, the – Phoenix exploit is a minor (<$1M) event compared to the largest same-class incident in our archive — Corkprotocol (2025) at $12M.
Prior Access Control Before – Phoenix
The nearest access control incident before – Phoenix was – swapX, 8 days earlier on February 27, 2023 ($1M lost). The same exploit class surfaced again within the access control attack surface.
– Phoenix Vulnerability Signature
The primary source categorises the – Phoenix exploit specifically as “Access Control & Arbitrary External Call”. This narrower label is entity-specific: it reflects how the – Phoenix contract failed, rather than the broad access control pattern alone.
Impact & Recovery for – Phoenix
– Phoenix Loss Figure
The – Phoenix exploit caused $100,000 in losses — a minor (<$1M) incident and the 84th largest of 214 documented in 2023.
Where – Phoenix Sits Among Access Control Attacks
Ranked by loss size, – Phoenix is the 24th largest of 77 access control incidents documented. That puts the – Phoenix loss below the class average of $636K.
Timeline Since the – Phoenix Incident
The – Phoenix exploit occurred 3.1 years ago (1,134 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for – Phoenix
Public post-mortem / on-chain analysis for the – Phoenix incident: view source.
FAQ
How much did – Phoenix lose?
The – Phoenix exploit in March 2023 resulted in $100,000 in losses — the 84th largest of 214 DeFi incidents that year.
When did the – Phoenix hack happen?
The – Phoenix exploit was recorded on March 7, 2023 — 1,134 days ago.
What type of exploit hit – Phoenix?
The – Phoenix 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 – Phoenix?
Our archive contains 77 documented access control incidents. The – Phoenix incident is one of them.
How does – Phoenix compare to the largest Access Control attack?
The largest access control incident in our archive is Corkprotocol (2025) at $12M. The – Phoenix loss is $100K.
Are there differences in SRQ between Italy and Germany after the directive?
The study explores SRQ differences, aiming to assess impacts of the directive in both countries.
What does the paper conclude about the effectiveness of anomaly detection algorithms in cold start scenarios?
Anomaly detection algorithms underperform and are best reserved for cold start scenarios, with active learning yielding better outcomes.