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

Avoid multi-auth phishing attack #3343

Closed
abitmore opened this issue Feb 24, 2021 · 4 comments
Closed

Avoid multi-auth phishing attack #3343

abitmore opened this issue Feb 24, 2021 · 4 comments

Comments

@abitmore
Copy link
Member

abitmore commented Feb 24, 2021

Is your feature request related to a problem? Please describe.

Several people have been phished by so-called "multi-auth attack" recently.

The attacker registered a lot of phishing accounts which are similar to exchange deposit accounts or frequent recipients of victims, and added the victims' to the phishing accounts' active authorities with a low weight. When a victim opens the "Send" dialogue, a phishing account will appear in the drop down list of "to" field automatically, if the victim didn't pay attention but clicked the phishing account, funds will be sent to the phishing account.

Note: it only affects key-file (.bin file or local wallet) login mode.

image

I've tried to reproduce, see screenshots below.
image

image

Describe the solution you'd like

A quick workaround is to disable the drop down list temporarily.

Better solutions are to be discussed.

@abitmore
Copy link
Member Author

abitmore commented Feb 24, 2021

Some ideas for long-term solution:

  • label "my accounts" and "contacts" in account selector with different color and/or text (note: it's almost there already - different icons and text, but it's hard to save users who don't pay attention)
  • improve the isKnownScammer check to check from dynamic data source (E.G. Auto blacklist proposal scammers #2658 (comment)).
  • warn user when detected it's the first time to transfer to a recipient (this may be not as useful due to limited history size)

@shulthz
Copy link
Contributor

shulthz commented Feb 25, 2021

A quick workaround is to disable the drop down list temporarily.

or only "my accounts" and "contacts" or “history” can be in this list.


There hava a BTS ID for every account, maybe as a authentication for “multi-auth” confirm.

@abitmore
Copy link
Member Author

or only "my accounts" and "contacts" or “history” can be in this list.

Actually the multi-auth phishing accounts are identified as "my accounts" now, because the victims "own" a weight of those accounts. We need to figure out a way to distinguish them (probably via UX).

By the way, if pay attention, when transferring, accounts in contacts now show an "star" icon, while my accounts and such phishing accounts show a user icon, and the account inputted has no icon if not in my accounts, contacts or known scam account list.

The screenshot below was for reproducing a scenario that assumes abit-test is the attacker, abit-test2 is the victim, and abit is in contacts.

image

The workaround in pull request #3344 won't show my accounts at all, which is a bit inconvenient but safer (a test environment is temporarily available at https://pr.bts.mobi/):

image

@abitmore
Copy link
Member Author

I think this is fixed.

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

2 participants