New contract with similar bytecode to exploit template

Evidence summary #

T-09 v2-deferred signal. No live new-deploy sweep with bytecode similarity check against Cap's contracts. Cap uses UUPS proxy pattern + AccessControl — bytecode-similar exploit-template contracts are a plausible class. No specific exploit-template deployment targeting Cap found via OSINT web searches.

Sources #

Methodology #

Detect whether a freshly deployed contract has high bytecode similarity to a known exploit template targeting this protocol class.

See the full factor methodology and distribution across all protocols →