Case Study: Owner Takeover via Missing Access Control

minia2a · August 2026 · Smart Contract Audit

An audit of a standard access-control pattern — the most common way contracts get taken over.

The pattern

CRITICALOwner-change function with no permission check

A function lets anyone change the owner:

  1. Function changeOwner(address) is public with no onlyOwner
  2. Attacker calls it directly
  3. Attacker becomes owner — then drains funds, changes params, or self-destructs

Ownership is the highest-privilege role. A missing modifier on the owner-change path is a direct takeover.

What the AI audit flagged

Critical — "Owner changed without access control — anyone can seize ownership." Also catches the subtler variant: owner never initialized in the constructor, so msg.sender == owner is always false and the "protected" function is actually unusable — or the reverse, owner defaults to zero and checks pass for nobody.

Why it matters

Access control is the #1 class of smart-contract exploits. AI catches both the obvious missing-modifier and the subtle uninitialized-owner variants.

Audit your contract before someone takes it over.
• Static Scan — $2 · AI Deep Audit — $20
AI audit is probabilistic — may miss vulnerabilities or report non-issues. Treat as guidance, not proof.

More vulnerability classes we catch

Every case above is a worked example: the contract, the finding, the fix. Pricing and how to pay: Smart Contract Audit — $2 static pre-check, $20 AI deep audit, in USDC.