All About Lightning Electrum
Bitcoin desktop wallet client Electrum has released a 4.0 beta version, adding several important updates, including support for the Lightning network, nearly a year after the previous version of Electrum, 3.3.8 (last July). In the 4.0 beta version, Electrum mainly added features such as PSBT (partially signed Bitcoin transactions), Lightning Network, watchtowers (暸 watchtowers) and Submarineswaps (subliminal switching). (Github)
Electrum posted a message about the incident on Twitter today, claiming that "there are currently phishing attacks against Electrum users" and imploring users to check the validity of their login information.
Digital wallet developer Electrum has released an emergency patch saying it found a vulnerability that could lead any website hosting Electrum to steal a user's digital currency, exposing passwords to the JOHNSONRPC interface and ingelling hackers full control of the wallet. Earlier, Electrum released the first patch, but it didn't seem to solve the problem, and they released a second update urgently Sunday night local time.
According to Bleeping Computer, the Bitcoin wallet app Electrom was on GitHub on May 9th, accusing a phishing product called Electrum Pro of stealing a user's seed key and registering a domain name called electrum without Electrum's permission. The Electrum team noted that there was a piece of code indicating that the counterfeit product might have taken the user's seed key and uploaded it to the electrum. Affected users should transfer funds from Bitcoin URLs managed by Eletrum Pro.
AToken Wallet is a centered wallet that allows users to pay only miners' fees when using the wallet feature to transfer money. As mentioned above, the miners' fee is paid to the miners for their work, not for the service of the AToken wallet. In other words, AToken wallets are free, centered wallets for users. So how to set a reasonable transfer fee?
The electrum and Electrum-LTC versions below 3.3.3 are vulnerable to phishing attacks in which a malicious server displays a message asking the user to download the fake Electrum. To prevent user exposure, versions older than 3.3 can no longer connect to public servers and must be upgraded. Do not download software updates from sources other than electrum.org and electrum-ltc.org.
Users of Bitcoin wallet Electrum are facing a phishing attack, according to the Devi Security Lab. Hackers broadcast messages to the Electrum client through a malicious server, prompting the user to update to v4.0.0, and if the user follows the prompt to install this "backdoor-carrying client", the private key is stolen and all digital assets are stolen. At the time of writing, at least 1,450 BTCs worth about $11.6 million had been stolen from phishing attacks that faked Electrum upgrade tips. DeViable Security Labs hereby suggests that versions of Electrum below 3.3.4 are vulnerable to such phishing attacks, and users using Electrum Wallet are requested to update to the latest version of Electrum 3.3.8 via the official website (electrum.org), which has not yet been officially released, and do not use the link in the prompt to avoid asset losses.
Before sending a message to Bob's Ethereum address, the application encrypts the message using Bob's public key. It also attaches a copy of a message encrypted with Alice's public key so that Alice can decrypt the message sent later.
Whether you choose to use mixers or not, there are additional steps you should take to mask your transactions and outsemod those forensics firms. One of the easiest but most effective ways to create a new Bitcoin wallet using services such as Electrum. Send your tokens to this address, then use the Tor browser to connect to the web, create a new wallet, and then send the tokens to a new address. For added privacy, you can repeat this step, send tokens between multiple wallets, and change the time delay between transaction amounts and each send. This process may seem difficult and not practical in everyday use, but in some cases it is a valuable exercise when you want to maintain a distance between the token source and the token destination.