Days since last exploit
A operational history factor in the v1.7.0 rubric. Measured per protocol on a c cadence.
Methodology how we score #
**What this measures** This factor calculates the number of days between today and the most recent recorded hack incident for this protocol. When a protocol is under an active incident (confirmed drain with ongoing post-mortem), the value is set to zero. The field is computed continuously from the hacks database and is display-only; it does not directly trigger a rubric color but informs curator judgment on the freshness of the risk profile and the post-exploit response scoring window.
**Why it matters** Time elapsed since last exploit has a nuanced relationship with current risk. In the short term (fewer than ninety days), a recently exploited protocol is at elevated risk of a follow-on attack: six of the dataset's repeat exploits occurred within twelve months, and in one case (Deus DAO) the attacker bypassed the post-hack fix in just forty days. In the medium term (ninety to three hundred sixty-five days), risk may be lower if a verified re-audit was conducted and the patch is confirmed on-chain. Beyond twelve months without another incident, the exploit-recency signal fades and other factors (audit coverage, multisig posture) dominate. The field is most useful as a temporal qualifier on the exploit count rather than a standalone risk signal.
**Green / Yellow / Red** This factor is display-only and contributes no direct rubric color. It is shown on the protocol detail page as a time-since counter and informs the curator when setting the post-exploit response score (RD-F-081) and the auditor-re-engagement flag (RD-F-083).
**Common gray cases** Protocols with multiple incidents record the most recent one. If a protocol was exploited and subsequently fully wound down and relaunched under the same branding, curator must determine whether the clock resets (new protocol entity) or continues (same team, same codebase lineage).
**Notable historical examples** No cross-hacked incidents currently linked in database for this factor.
Measurement what to look for #
Measure the number of days between today and the most recent incident for this protocol (0 if an incident is currently active).