On August 2023, ExactlyProtocol was exploited in a other, resulting in approximately $7M in losses. That makes the ExactlyProtocol exploit the 37th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the ExactlyProtocol Other Played Out
Exploit Class Applied to ExactlyProtocol
The ExactlyProtocol incident on August 18, 2023 is classified as a Other. A specific exploit class outside the most common buckets. In the full archive, ExactlyProtocol is 1 of 188 documented other incidents.
ExactlyProtocol in Context
At $7M, the ExactlyProtocol exploit is a significant ($1M–$10M) event compared to the largest same-class incident in our archive — MIMSpell (2024) at $65M.
Prior Other Before ExactlyProtocol
The nearest other incident before ExactlyProtocol was Uwerx, 16 days earlier on August 2, 2023. The same exploit class surfaced again within the other attack surface.
ExactlyProtocol Vulnerability Signature
The primary source categorises the ExactlyProtocol exploit specifically as “insufficient validation”. This narrower label is entity-specific: it reflects how the ExactlyProtocol contract failed, rather than the broad other pattern alone.
Impact & Recovery for ExactlyProtocol
ExactlyProtocol Loss Figure
The ExactlyProtocol exploit caused $7,000,000 in losses — a significant ($1M–$10M) incident and the 11th largest of 214 documented in 2023. This single incident represents 1.1% of all tracked losses that year.
Where ExactlyProtocol Sits Among Other Attacks
Ranked by loss size, ExactlyProtocol is the 6th largest of 188 other incidents documented. That puts the ExactlyProtocol loss above the class average of $2.03M.
Timeline Since the ExactlyProtocol Incident
The ExactlyProtocol exploit occurred 2.7 years ago (970 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for ExactlyProtocol
Public post-mortem / on-chain analysis for the ExactlyProtocol incident: view source.
FAQ
How much did ExactlyProtocol lose?
The ExactlyProtocol exploit in August 2023 resulted in $7,000,000 in losses — the 11th largest of 214 DeFi incidents that year.
When did the ExactlyProtocol hack happen?
The ExactlyProtocol exploit was recorded on August 18, 2023 — 970 days ago.
What type of exploit hit ExactlyProtocol?
The ExactlyProtocol incident is classified as a Other. A specific exploit class outside the most common buckets.
How common is the Other pattern seen at ExactlyProtocol?
Our archive contains 188 documented other incidents. The ExactlyProtocol incident is one of them.
How does ExactlyProtocol compare to the largest Other attack?
The largest other incident in our archive is MIMSpell (2024) at $65M. The ExactlyProtocol loss is $7M.
How does blockchain technology impact the auditing sector?
By offering a secure, transparent, and automated method of conducting audits, enhancing the speed and effectiveness of auditing procedures.
How do adversarial examples challenge the reliability of deep learning models?
By showing that small, often imperceptible, modifications to input data can lead to incorrect model predictions.