Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security: Warning before signing some authz MsgGrant transactions #1084

Open
arlai-mk opened this issue Mar 28, 2024 · 0 comments
Open

Security: Warning before signing some authz MsgGrant transactions #1084

arlai-mk opened this issue Mar 28, 2024 · 0 comments

Comments

@arlai-mk
Copy link

Is your feature request related to a problem? Please describe.
There are a number of scams that use Cosmos SDK authz MsgGrant feature to give themselves complete control over the wallet on the chain, and users may not be aware that signing the MsgGrant can lead to such outcomes.
MsgGrant is a very valid feature and should surely be better explained to users, however it feels like wallets like Keplr could have a responsibility in alerting their users of potential risks before signing such transactions. I am especially thinking of the cases with GenericAuthorization allowing the grantee access to MsgGrant, MsgSend. These should not be too common.

Describe the solution you'd like
I would like Keplr wallet extension (or mobile app) to show a warning whenever the user is ready to sign an authz MsgGrant (at least with GenericAuthorization giving the grantee access to MsgGrant, MsgSend.
The warning could be something like: "We notice that you are going to sign a transaction that can lead to loss of funds in your wallet. Please confirm that you are absolutely certain that you are on a legitimate site and that you know what you are doing, before signing the transaction."

Describe alternatives you've considered
I don't think we can ask the Cosmos SDK team to block certain messages in MsgGrant, so it seems the wallet is the best place to warn users to not fall to this kind of scam.

Additional context
Please find below an example of a wallet being drained this way.
The victim only signed one transaction that granted the attacker the right to MsgGrant.
https://www.mintscan.io/cosmos/tx/421B90D333AC90E8EC27264CDF6DDDA75B69D3B93AB3288DDA019786DBF2C41D?height=19607412
From there, the attacker had all access, could grant himself more permissions, then granted same full access to 2000 of its wallets (making it more difficult to revoke - that's another topic) and then drained all funds (~1000 staked ATOM + all liquid assets).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant