Kontos

In the contract `DeployFactory` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and perform malicious upgrades.  In the contract `DeployFactory` the role `_superowner` has authority over the functions shown in the diagram below.  In the contract `SmartAccount` the role `_eoaOwner` has authority over the functions shown in the diagram below. Any compromise to the `_eoaOwner` account may allow the hacker to take advantage of this authority and execute arbitrary transaction from the SmartAccount.  In the contract `SmartAccountBeacon` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and perform malicious upgrade to the beacon implementation contract.  In the `EntryPoint` contract, the `broker` role is responsible for bundling `userOps` and signing them to be executed via `handleOps()`. If addresses with `broker` role is compromised, normal user operations would not be able to be executed via the `EntryPoint` contract.

In the `DeployFactory` contract, the role `owner` has the authority to update the implementation contract behind the SmartAccount Beacon and perform various upgrades to the `upgradeGateKeeperProxy` contract. Additionally, the `UpgradeGateKeeper` is an upgradeable contract that inherits other upgradeable contracts. Any compromise to the `owner` account may allow a hacker to take advantage of this authority and change the implementation contract which is pointed by proxy and therefore execute potential malicious functionality.