Known-exploit-template selector deployed by any address
Beefy Finance's assessment for RD-F-162 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
T-09 phase-2 signal. No known exploit-template specifically targeting BeefyVaultV7 architecture deployed by any address. Beefy is an original protocol (not a fork); standard Compound-fork or Aave-fork exploit templates do not apply. The CLM TWAP critical (Zellic 2024-02-28) was fixed pre-deployment; no active exploit template derived from it is publicly known. Rekt incidents = 0 for Beefy (no historical exploit to derive a replay template from).
Sources #
- GitHubBeefy Finance audit repositorybeefyfinance/beefy-audits — no post-exploit replay templateretrieved 2026-05-16
- Polymarket data cache00-data-cache.json — rekt.incidents: []retrieved 2026-04-29
Methodology #
Determine whether any contract has been deployed containing a function-selector pattern matching a known exploit template targeting protocols of this class.
See the full factor methodology and distribution across all protocols →