Beefy Zap Audit

OpenZeppelinFiles named in the report

Audit · firm’s term: audit

OpenZeppelin reviewed Zap Protocol (Beefy Zap Audit) on 29 Jun 2023: 6 findings, 1 critical; all marked fixed.

1 critical finding, fixed
Open Zap Protocol’s security record

The original report was removed from its address (seen 19 Oct 2026).

Trustblock does not review code.

Findings6

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical001
High001
Medium000
Low004
CriticalExternal Call to Permit2 Allows Stealing Users' TokensFixed

The report gives no description here.

HighDenial-of-Service of Router FunctionalityFixed

The report gives no description here.

LowFloating PragmaFixed

The report gives no description here.

LowMissing DocstringsFixed

The report gives no description here.

LowMissing Order Typehash Prefix for Witness ParameterFixed

The report gives no description here.

LowWitness Type String Does Not Follow EIP-712Fixed

The report gives no description here.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Repository and files the report names (6)

  • IPermit2.sol
  • IBeefyTokenManager.sol
  • ZapErrors.sol
  • BeefyZapRouter.sol
  • BeefyTokenManager.sol
  • IBeefyZapRouter.sol

Part of Zap Protocol’s security record

Zap Protocol
Audits4 audits by 2 firmsLast audit Apr 2024, by Zokyo.
Critical findingsNo open critical findingsAcross the 4 reports, 6 critical findings were reported. Each is marked fixed by the firm that reported it.
Open Zap Protocol’s security record

Security firm

OpenZeppelin

67 projects reviewed · 184 reports · latest Aug 2026

See OpenZeppelin’s audits

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us