Submitted by shenwilly
https://github.com/code-423n4/2022-05-backd/blob/2a5664d35cde5b036074edef3c1369b984d10010/protocol/contracts/tokenomics/InflationManager.sol#L609-L618
https://github.com/code-423n4/2022-05-backd/blob/2a5664d35cde5b036074edef3c1369b984d10010/protocol/contracts/tokenomics/KeeperGauge.sol#L82
https://github.com/code-423n4/2022-05-backd/blob/2a5664d35cde5b036074edef3c1369b984d10010/protocol/contracts/actions/topup/TopUpActionFeeHandler.sol#L95-L98
https://github.com/code-423n4/2022-05-backd/blob/2a5664d35cde5b036074edef3c1369b984d10010/protocol/contracts/actions/topup/TopUpAction.sol#L807
https://github.com/code-423n4/2022-05-backd/blob/2a5664d35cde5b036074edef3c1369b984d10010/protocol/contracts/actions/topup/TopUpAction.sol#L653
When _removeKeeperGauge is called, there is no guarantee that the keeper gauge isnt currently in use by any TopUpActionFeeHandler. If its still in use, any top up action executions will be disabled as reporting fees in KeeperGauge.sol will revert:
If this happened during extreme market movements, some positions that require a top up will not be executed and be in risk of being liquidated.
Consider adding an on-chain check to ensure that the keeper gauge is not in use before removing them.
danhper (Backd) confirmed 
Alex the Entreprenerd (judge) commented:
