New contract with similar bytecode to exploit template
Jupiter Perpetual Exchange's assessment for RD-F-094 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
New contract deployment with similar bytecode to protocol target. EVM bytecode similarity requires 4-byte selector database and EVM bytecode comparison tooling (Etherscan verified-source comparison). Solana BPF programs use a different binary format (BPF ELF); no equivalent public bytecode-similarity database exists for Solana programs. The Solana program verification ecosystem (verify.osec.io) focuses on reproducibility matching a known build, not similarity-to-exploit-template across programs.
Sources #
- InternalPhase-2 shared briefing U10Solana BPF binary format; no 4-byte-selector DB or EVM bytecode similarity tools applicable. Briefing §15 U10.retrieved 2026-05-16
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 →