# \[Security Disclosure\] MetaMask Staking Precautionary Out of Order Exits

**URL:** <https://research.lido.fi/t/security-disclosure-metamask-staking-precautionary-out-of-order-exits/11961>\
**Category:** Node Operators\
**Created:** [September 30, 2026, 11:40pm UTC](https://research.lido.fi/t/security-disclosure-metamask-staking-precautionary-out-of-order-exits/11961 "2026-09-30T23:40:48Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dgusakov](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/dgusakov/32/1238_2.png) [@dgusakov](https://research.lido.fi/u/dgusakov)\
**Post date:** [October 5, 2026, 9:39am UTC](https://research.lido.fi/t/security-disclosure-metamask-staking-precautionary-out-of-order-exits/11961/2 "2026-10-05T09:39:45Z")

</div>

Due to the incident described above, Lido contributors propose setting the following target limit parameters for MetaMask Staking (ex Consensys Staking) in both CMv1 and CMv2:

- `targetLimit = 0`
- `targetLimitMode = 1` (soft)

These parameters mean that no new deposits will be allocated to MetaMask Staking (ex Consensys Staking) Node Operators in both CMv1 and CMv2.

The change will be implemented by adding the following calls to the next on-chain vote:

- On [`0x55032650b14df07b85bF18A3a3eC8E0Af2e028d5`](https://etherscan.io/address/0x55032650b14df07b85bF18A3a3eC8E0Af2e028d5) call `updateTargetValidatorsLimits(uint256 _nodeOperatorId, uint256 _targetLimitMode, uint256 _targetLimit)` with `_nodeOperatorId = 21, _targetLimitMode = 1, _targetLimit = 0`
- On [`0xDa5F930cE326EB5205085D66c72A4E79d60cB8C1`](https://etherscan.io/address/0xDa5F930cE326EB5205085D66c72A4E79d60cB8C1) call `updateTargetValidatorsLimits(uint256 nodeOperatorId, uint256 targetLimitMode, uint256 targetLimit)` with `_nodeOperatorId = 6, _targetLimitMode = 1, _targetLimit = 0`

---

_[View the full topic](https://research.lido.fi/t/security-disclosure-metamask-staking-precautionary-out-of-order-exits/11961)._