How To Avoid SIM Swap Attacks

As recently as February 22, 2020 at least $45 million worth of cryptocurrency was stolen by an attacker who used one of the oldest tricks in the book: SIM Swapping.

SIM swapping is a simple “human engineering” kind of hack that usually involves convincing the victim’s phone company to move their existing phone number to a phone and SIM that the attacker controls. This is done to bypass 2FA systems where a text message or phone call is used as the last line of defense for account recovery options such as a password reset.

In this guide we will review the simplest approach to avoid having your crypto stolen by an attacker utilizing the same approach


How To Avoid SIM Swap Attacks


Step 1)

Instead of tying SMS to your account recovery, utilize cryptographic 2FA provided by apps such as Authy, Google Authenticator.


Step 2)

That’s it!


The Launch of Byzantine

Today we’re proud to announce we’ve slated a LAUNCH DATE for Byzantine, along with token swap details. By using Byzantine you’ll be able to be part of our payments network, which you can read more about on the dedicated Byzantine page at


Acquiring Byz tokens

In order to acquire Byz tokens at a 5x ratio (5 Byz token for every 1 Blue you swap) you’ll need to be one of the first to perform the swap. If you don’t make it in to the first 1 million coin swaps, that’s OKAY, you can participate in round two at a 4x ratio, which will be limited to 2 million Blue tokens. The full chart is here: which leaves 42M BYZ minted, the same as the total supply of Blue:

5:1 Ratio
Byzantine Limit: 5 million
Blue Limit: 1 million

4:1 Ratio
Byzantine Limit: 8 million
Blue Limit: 2 million

3:1 Ratio
Byzantine Limit: 9 million
Blue Limit: 3 million

2:1 Ratio
Byzantine Limit: 20 million
Blue Limit: 10 million

1:1 Ratio
No limits needed!


How to Claim:

On August 20th, 2019, an update will be posted across Twitter, Telegram, and via email for everyone to claim their coins. After this it will be a first-come-first-server system where you swap your Blue tokens by sending them to the swap smart contract (the contract address and code will be available at the same time). If you want to be notified right away you can sign up for the notification list here: Email Me!

Exchange Donations


After extensive talks with several exchanges we’ve got an opportunity to improve our visibility through some top 50 exchanges. We aren’t sure who we will go with yet but we’re going to open up donations for those who want to see BLUE on more exchanges. Regardless of the exchange selection, we’ll need a few more BTC to pay for listing. When contributing be sure to PM an Admin on Telegram, or email [email protected] with a tx id and a name so we can add you to the website as a contributor (plus a little secret surprise later this year that will show up in your Blue Wallet)
If you contribute via BTC, be sure to include your Blue wallet address as well!

Major criteria for our new exchange selection process:
1) Must be in the top 50 by adjusted volume
2) Must be available in China, S Korea, Japan
3) Must be above board with a clean record free of hacks, wash trading, and scam coin listings
4) Must be willing to consider using our SDK within the exchange

Contribute BTC: 39jtTnJtStNL63PQyquX7HiGukJVmMLcbu
Contribute ETH: 0xdfb3355981ca3c7ba6ba790b26f02c3737727de7

Interested in seeing the list of supporters so far? You can see them here.

MyEtherWallet Keeps Getting Hacked

Back in January, the security team at BLUE noticed an irregularity with’s DNS configuration. In particular we saw that some users were being sent to a fake version of the site that was stealing their private keys and using this to funnel out MEW user’s funds during a very short timeframe. After this occurred the DNS settings were changed back and as far as anyone could tell the site was operating as per usual. MEW claimed there was never an issue in the first place, and asserted that MEW was safe to use.

We notified our community and the MEW team of this vulnerability, to which MEW responded with a CoinTelegraph article, calling us “stupid liars”.[] We were not contacted to comment on this by the journalist involved. The MEW team also sent us legal threats via email, refuting that there was ever a problem. This was their approach, as opposed to simply discussing the issue to prevent future DNS issues. It would appear that the MEW team has continued to have the same lacking security of their DNS, and today the issue happened once again. CoinTelegraph has responded with a follow-up acknowledging it’s role in the misleading statements made by MEW []

The issue has to do with the way domain names resolve to a specific web server. The normal server controlled by MyEtherWallet was never touched, however a new duplicate server was created by a hacker that looked and behaved exactly like the MyEtherWallet official site. This site had one critical difference: Instead of performing your transactions after authorizing the site with a private key, it would simply use this private key to funnel all of the user’s funds to a hackers wallet.

The hacker’s wallet was identified today as having stolen at least 215 ETH, or $150,547 at the time of this writing. The hackers wallet address: 0x1d50588C0aa11959A5c28831ce3DC5F1D3120d29

This issue is related to a DNS registry problem with the public Google DNS server located at, used by many around the world for reliable DNS access, as many ISPs have frequent problems and Google is trusted to manage this service properly.

Our advice to our community to secure their funds is of course to use the BLUE Wallet Chrome extension, but if you must use MyEtherWallet, absolutely download a local copy for yourself and access it with a hardware wallet such as a Trezor or Ledger. To be clear, if you have previously used MEW to send and receive funds, we do NOT advise logging in and attempting to move your funds out at this time. Your funds should be safe, but logging in to check your balance or send out your funds may lead to the phishing server, and we can not recommend performing this action at this time. We will update the community on our official twitter, @Blue_Protocol when it is safe to transfer your funds away from the service.


UPDATE: MyEtherWallet released an official statement on the issue, acknowledging that it’s DNS servers were manipulated.

It is our understanding that a couple of Domain Name System registration servers were hijacked at 12PM UTC to redirect myetherwallet[dot]com users to a phishing site.

This redirecting of DNS servers is a decade-old hacking technique that aims to undermine the Internet’s routing system. It can happen to any organization, including large banks. This is not due to a lack of security on the @myetherwallet platform. It is due to hackers finding vulnerabilities in public facing DNS servers.

A majority of the affected users were using Google DNS servers. We recommend all our users to switch to Cloudfare DNS servers in the meantime.

Affected users are likely those who have clicked the “ignore” button on an SSL warning that pops up when they visited a malicious version of the MEW website.

We are currently in the process of verifying which servers were targeted to help resolve this issue as soon possible.

A message to our MEW community:

Users, PLEASE ENSURE there is a green bar SSL certificate that says “MyEtherWallet Inc” before using MEW.

We advise users to run a local (offline) copy of the MEW (MyEtherwallet).

We urge users to use hardware wallets to store their cryptocurrencies.

In the meantime we urge users to ignore any tweets, reddit posts, or messages of any kind which claim to be giving away or reimbursing ETH on behalf of MEW.

Your security and privacy is ALWAYS our priority. We do not collect or own any user data.

We greatly appreciate your patience and understanding as we try to fight against this criminal phishing attack.

To keep up this fight against phishing, we need our amazing community to support