On October 2022, Team Finance was exploited in a other, resulting in approximately $15.8M in losses. That makes the Team Finance exploit the 25th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the Team Finance Other Played Out
Exploit Class Applied to Team Finance
The Team Finance incident on October 27, 2022 is classified as a Other. A specific exploit class outside the most common buckets. In the full archive, Team Finance is 1 of 188 documented other incidents.
Team Finance in Context
At $15.8M, the Team Finance exploit is a major ($10M–$100M) event compared to the largest same-class incident in our archive — MIMSpell (2024) at $65M.
Prior Other Before Team Finance
The nearest other incident before Team Finance was Carrot, 17 days earlier on October 10, 2022. The same exploit class surfaced again within the other attack surface.
Team Finance Vulnerability Signature
The primary source categorises the Team Finance exploit specifically as “Liquidity Migration Exploit”. This narrower label is entity-specific: it reflects how the Team Finance contract failed, rather than the broad other pattern alone.
Impact & Recovery for Team Finance
Team Finance Loss Figure
The Team Finance exploit caused $15,800,000 in losses — a major ($10M–$100M) incident and the 3rd largest of 129 documented in 2022. This single incident represents 7.1% of all tracked losses that year.
Where Team Finance Sits Among Other Attacks
Ranked by loss size, Team Finance is the 4th largest of 188 other incidents documented. That puts the Team Finance loss above the class average of $2.03M.
Timeline Since the Team Finance Incident
The Team Finance exploit occurred 3.5 years ago (1,265 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for Team Finance
Public post-mortem / on-chain analysis for the Team Finance incident: view source.
FAQ
How much did Team Finance lose?
The Team Finance exploit in October 2022 resulted in $15,800,000 in losses — the 3rd largest of 129 DeFi incidents that year.
When did the Team Finance hack happen?
The Team Finance exploit was recorded on October 27, 2022 — 1,265 days ago.
What type of exploit hit Team Finance?
The Team Finance incident is classified as a Other. A specific exploit class outside the most common buckets.
How common is the Other pattern seen at Team Finance?
Our archive contains 188 documented other incidents. The Team Finance incident is one of them.
How does Team Finance compare to the largest Other attack?
The largest other incident in our archive is MIMSpell (2024) at $65M. The Team Finance loss is $15.8M.
Which model is used to analyze the volatility of stock market indices?
The GARCH (Generalized Autoregressive Conditional Heteroskedasticity) model.
What are the implications of cryptocurrencies for VAT/sales taxes according to the study?
Cryptocurrencies pose profound risks for VAT/sales tax compliance and evasion.