Unauthorized Upgrade / Proxy Hijack
1 min read
Pronunciation
[uhn-uh-thaw-ri-ized uhpgreyd prok-see hahy-jak]
Analogy
Like changing the locks on a building without authorization so that only the attacker’s keys work.
Definition
An exploit where attackers gain permission to upgrade a proxy contract’s implementation, redirecting logic to malicious code and compromising contract integrity.
Key Points Intro
Proxy hijacks occur when upgrade mechanisms lack proper access controls.
Key Points
Admin role: insecure or exposed proxy admin wallet
Access control: missing `onlyOwner` or timelock guards
Implementation change: attacker sets malicious logic contract
Delegation: proxy’s `delegatecall` runs attacker code
Example
A DeFi protocol releases an upgradeable proxy but forgets to restrict `upgradeTo` to governance, allowing a hacker to point it to a malicious implementation.
Technical Deep Dive
Proxies follow EIP-1967 or UUPS patterns. Attackers target admin slots (keccak256 hashes) or bypass ownership via unprotected functions. Secure patterns include timelock-enforced upgrades, multisig admin keys, and transparent proxy design to separate user and admin calls.
Security Warning
Improper access control can lead to full takeover and fund theft.
Caveat
Upgrade patterns require rigorous audit and secure governance processes.
Unauthorized Upgrade / Proxy Hijack - Related Articles
No related articles for this term.