On April 2024, GROKD suffered a access control — the first of 77 documented access control incidents in our archive where the loss figure was not publicly disclosed but the exploit pattern is documented below.
Attack Mechanics: How the GROKD Access Control Played Out
Exploit Class Applied to GROKD
The GROKD incident on April 12, 2024 is classified as a Access Control. A privileged function lacks a proper authorisation check, letting an unauthorised caller execute it. In the full archive, GROKD is 1 of 77 documented access control incidents.
GROKD in Context
The GROKD incident joins a class whose largest loss to date is Corkprotocol (2025) at $12M.
Prior Access Control Before GROKD
The nearest access control incident before GROKD was ETHFIN, 14 days earlier on March 29, 2024. The same exploit class surfaced again within the access control attack surface.
GROKD Vulnerability Signature
The primary source categorises the GROKD exploit specifically as “lack of access control”. This narrower label is entity-specific: it reflects how the GROKD contract failed, rather than the broad access control pattern alone.
Impact & Recovery for GROKD
GROKD Loss Figure
The loss figure for GROKD is not publicly disclosed. The primary source reports the exploit in non-USD terms, so no USD estimate is published here. For reference, the average loss across 77 access control incidents in our archive is $636K.
Timeline Since the GROKD Incident
The GROKD exploit occurred 2 years ago (732 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for GROKD
Public post-mortem / on-chain analysis for the GROKD incident: view source.
FAQ
How much did GROKD lose?
The GROKD loss figure is not publicly disclosed. The primary source reports the exploit in non-USD token terms, so no USD estimate is published here.
When did the GROKD hack happen?
The GROKD exploit was recorded on April 12, 2024 — 732 days ago.
What type of exploit hit GROKD?
The GROKD 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 GROKD?
Our archive contains 77 documented access control incidents. The GROKD incident is one of them.
How does GROKD compare to the largest Access Control attack?
The largest access control incident in our archive is Corkprotocol (2025) at $12M. The GROKD loss was not publicly disclosed.
How does the framework address the scalability challenges associated with blockchain?
By integrating a layered blockchain structure with L2 solutions for improved performance.
What period does the study cover?
2010 to 2015.