Proxy Admin Explained in Detail
Proxy admin is the authority that can upgrade a proxy. In OpenZeppelin transparent proxies, this is often a ProxyAdmin contract owned by a multisig or governance system.
The proxy admin can change the code that user calls execute.
Smart contract example
ProxyAdmin owner -> ProxyAdmin upgrade call -> proxy implementation changes
The owner of the admin contract is usually the real upgrade authority.
Proxy Admin in Auditing
Proxy admin compromise is protocol compromise. A malicious upgrade can drain funds, change accounting, bypass checks, or brick the system.
Auditors identify the actual admin path, not just the contract name.
Red flags in code
-
Proxy admin is an EOA.
-
ProxyAdmin owner is not a multisig or timelock when high value is at risk.
-
Admin slot does not match deployment documentation.
-
Upgrade calldata is not decoded or reviewed.
-
Admin can renounce ownership and lock critical upgrades by mistake.
How to test or review it
Keep learning this topic
ERC1967
ERC1967 defines standard proxy storage slots for implementation, admin, and beacon addresses.
Transparent Proxy
A transparent proxy is an upgradeable proxy pattern where admin calls are handled by the proxy while non-admin calls are delegated to the implementation.
Upgrade Authorization
Upgrade authorization is the access-control logic that decides who can change a proxy implementation.
Practice this in real audit scenarios
Definitions help, but auditors need reps. SCH turns concepts like Proxy Admin into exploit labs, code review habits, and report-writing practice.
Start the free trial or see the full smart contract auditing course.