While we are up and about trying to find the next bewt project to farm in order to qualify for an allocation, don't forget to take the security of your wallet account very seriously — if you're not using Rabby wallet already, get it in place of Metamask.
I have been using Metamask since I started using Ethereum and it works for my needs so I stick with it, I have heard about Rabby albeit for wrong reasons cause they were hacked (you can read about it here). What is your reasoning behind suggesting Rabby over MM anyway?
Firstly, Rabby has some of the best security out of the box. When you want to interact with a function/method on chain, there's no way to know the function you're interacting with if you're using metamask just based on the calldata. What I mean is that, when you're interacting with a function in a contract, metamask only shows you the entire bytes in hexadecimal format which includes the function 4-byte function selector and the calldata input. Only EVM-savvy users can use a tool like Foundry to decode the bytes in order to get the 4-byte selector of preferred function. In Rabby, they decode the calldata for you and you can immediately see the function you're interacting with is indeed correct and then they run a simulation on that transaction for you so you can see an example result before you even sign the transaction. For instance, if you're doing a swap, it immediately does a simulation and show you what could happen if you actually sign the transaction.
TLDR: Rabby decodes calldata bytes and show you what you're signing so you can make a well informed decision. Metamask doesn't. It's called "blind signing" — you don't know what you're signing until transaction has been executed and there are repercussions, if any.
Secondly, Rabby has the best UX. You can seamlessly interact with dapps on different networks especially if you're dealing with an interoperability protocol or bridge and requires you to switch networks. Rabby does the switch in the background. For Metamask, you have to explicitly open the extension and switch the network.
Also, the hack you're talking about is their smart contract swap feature, not the wallet itself.
A couple of weeks ago, I shared the the Ledger vulnerability for web3 dapp connectors. Rabby showed users a notice about connecting plus before signing, it warned users that the transaction was to allow maximum allowance of tokens for spending.
It has got lengthy so I'll do here. You can keep using Metamask, it's still a good choice, you can try using Foundry with it to decode the 4-byte selector to verifying if you're interacting with correct functions prior to signing.