New contract with similar bytecode to exploit template

Evidence summary #

T-09 phase-2 signal. No exploit-template-resembling bytecode known to target BeefyVaultV7 architecture. Beefy is an original protocol (not a fork of Compound or Aave), so standard fork-targeting exploit templates do not apply. The CLM TWAP critical finding (Zellic 2024-02-28) was fixed pre-deployment; no active exploit template derived from it is known.

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 →