On December 2023, PineProtocol was exploited in a business logic flaw, resulting in approximately $90K in losses. That makes the PineProtocol exploit the 224th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the PineProtocol Business Logic Flaw Played Out
Exploit Class Applied to PineProtocol
The PineProtocol incident on December 22, 2023 is classified as a Business Logic Flaw. A business-logic bug in the contract — such as an incorrect formula or missing state update — lets the attacker withdraw more than their share. In the full archive, PineProtocol is 1 of 144 documented business logic flaw incidents.
PineProtocol in Context
At $90K, the PineProtocol exploit is a minor (<$1M) event compared to the largest same-class incident in our archive — – EulerFinance (2023) at $200M.
Prior Business Logic Flaw Before PineProtocol
The nearest business logic flaw incident before PineProtocol was FloorProtocol, 5 days earlier on December 17, 2023 ($16M lost). The same exploit class surfaced again within the business logic flaw attack surface.
Impact & Recovery for PineProtocol
PineProtocol Loss Figure
The PineProtocol exploit caused $90,000 in losses — a minor (<$1M) incident and the 87th largest of 214 documented in 2023.
Where PineProtocol Sits Among Business Logic Flaw Attacks
Ranked by loss size, PineProtocol is the 42nd largest of 144 business logic flaw incidents documented. That puts the PineProtocol loss below the class average of $6.08M.
Timeline Since the PineProtocol Incident
The PineProtocol exploit occurred 2.3 years ago (844 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for PineProtocol
Public post-mortem / on-chain analysis for the PineProtocol incident: view source.
FAQ
How much did PineProtocol lose?
The PineProtocol exploit in December 2023 resulted in $90,000 in losses — the 87th largest of 214 DeFi incidents that year.
When did the PineProtocol hack happen?
The PineProtocol exploit was recorded on December 22, 2023 — 844 days ago.
What type of exploit hit PineProtocol?
The PineProtocol incident is classified as a Business Logic Flaw. A business-logic bug in the contract — such as an incorrect formula or missing state update — lets the attacker withdraw more than their share.
How common is the Business Logic Flaw pattern seen at PineProtocol?
Our archive contains 144 documented business logic flaw incidents. The PineProtocol incident is one of them.
How does PineProtocol compare to the largest Business Logic Flaw attack?
The largest business logic flaw incident in our archive is – EulerFinance (2023) at $200M. The PineProtocol loss is $90K.
Compared to which other major events is the war's impact analyzed?
The Covid-19 pandemic and the 2008 global financial crisis.
What challenges are identified in measuring ESG performance?
The lack of granular data on ESG attitudes and the absence of a consistent ESG rating system.