According to Reddit user u/normal_rc, electrum's wallet was hacked and nearly 250 bitcoins (243.6 BTCs, nearly $1 million) were maliciously stolen, according to coinelegraph. Electrum then confirmed that the attack included creating a fake version of the wallet to trick users into providing password information. Electrum responded on Twitter that "this is a persistent phishing attack on Electrum users" and warned users not to download Electrum from any source other than the official website.
Today, electrum Wallet's official Twitter feed repeatedly alerted users to hacking attacks.
Bitcoin Wallet Electrum has released a beta version of Electrum 4.0, which supports the Lightning Network.
ZClassic (ZCL) has released a beta version of the ZCL Electrum wallet.
Electrum Litecoin Wallet review: Lightweight Litecoin customers.
When Electrum wallets are synchronized with malicious servers, they are instructed to "update" clients provided by hackers, resulting in the loss of assets contained in older versions. Previously, in December 2018, 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)
June 10, recently, slow fog security team received information, there are professional black production team for exchange users to carry out large-scale mail bulk net phishing attacks. Analysis by the Slow Fog Security team found that both attackers gave download links to macOS/Windows systems and performed a series of malicious actions, such as uploading local system user information, stealing sensitive information from electrum wallets, and so on.
Bitcoin Wallet providers like Trezor and Electrum.
df . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .