Governance Attack
Pronunciation: GUH-vur-nuns uh-TAK
Definition
A governance attack manipulates voting, delegation, proposals, administrators, or decision processes to gain unauthorized or harmful control over a system. For Governance Attack, an attempted action, a detected indicator, a confirmed compromise, and a realized loss are separate states that require different evidence and response.
Overview
Meaning and scope
A governance attack manipulates voting, delegation, proposals, administrators, or decision processes to gain unauthorized or harmful control over a system. For Governance Attack, an attempted action, a detected indicator, a confirmed compromise, and a realized loss are separate states that require different evidence and response.
Mechanism and operation
A governance attack targets the mechanism used to change protocol rules, contracts, parameters, treasury use, upgrades, or emergency powers. Attackers may acquire voting power, borrow tokens, compromise delegates, exploit quorum rules, or deceive authorized signers. Weak proposal validation, concentrated ownership, low participation, instantaneous execution, ambiguous permissions, and unprotected upgrade keys increase exposure. A formally valid vote can still be economically manipulated or procedurally illegitimate when the underlying process is captured. Defenses include quorum and threshold design, time locks, voting-power snapshots, delegation transparency, proposal simulation, role separation, and emergency review. Monitoring should detect sudden concentration, borrowed influence, suspicious delegate changes, and proposals with hidden technical effects.
Practical payment example
A token-based protocol vote attempts to replace an oracle with an attacker-controlled feed. Safeguards such as timelocks and monitoring allow defenders to evaluate the change before it affects collateral or payments.
Operational checks
Governance rules are a security boundary, so voting power, proposal code, execution delay, delegation, and emergency authority need layered protection. Assessment of Governance Attack should trace governance attack manipulates voting, delegation, proposals, administrators, or decision processes to gain unauthorized or harmful control over a system from prerequisite and entry point through observable impact on the affected service.
Distinctions and limits
A theoretical weakness or scanner result involving governance attack manipulates voting, delegation, and proposals should not be reported as exploitation without corroborating logs, transactions, or configuration evidence.
Related reading
Example
A token-based protocol vote attempts to replace an oracle with an attacker-controlled feed. Safeguards such as timelocks and monitoring allow defenders to evaluate the change before it affects collateral or payments.
Comparison
A theoretical weakness or scanner result involving governance attack manipulates voting, delegation, and proposals should not be reported as exploitation without corroborating logs, transactions, or configuration evidence.
Key Takeaway
Governance rules are a security boundary, so voting power, proposal code, execution delay, delegation, and emergency authority need layered protection.
Sources
- NIST Documentation: Cyberframework — NIST (2026-07-30)
- FATF Documentation: Virtual Assets — FATF (2026-07-30)