Reddit user MoneroDontCheeseMe said that he lost 1680 Monero (about $ 80,000 at the current rate) when transferring funds using the Monero client version 0.14 and the hardware wallet Ledger Nano S version 1.1.3.

According to him, he made several Monero cryptocurrency transfers from the Ledger device to the “view-only” wallet for 0.000001, 10, 200 and 141.9 XMR.

Before sending the last transaction on the wallet, MoneroDontCheeseMe had about 1690 XMR, and on the unlocked balance sheet – 141.95 XMR. However, after completion of the operation, the user's wallet showed a zero balance.

“I noticed that the sent amounts and transactions recorded in the blockchain do not match. In fact, a 200 XMR transaction took 1691,001 XMR from my Ledger wallet. In addition, the amounts specified for transaction 10 XMR do not match each other, ”writes MoneroDontCheeseMe.

In the comments to the post of the user, Ledger technical director Nicolas Bakka called the synchronization problem the most likely cause of the incident.

Card

However, later it turned out that this was not the case. According to the developers of Ledger, the bug manifests itself when using the client Monero version 0.14 with the company's own client version 1.1.3.

Monero Ledger HW app with latest Monero client v0.14. Support issues have been reported. See more here https://t.co/yOV2b09QaG

– Ledger (@Ledger) March 4, 2019

“It seems that there is a bug related to the address of the return wallet. Refunds appear to be incorrect. The undesirable effect is a combination of a specific version of the Monero client with a specific version of the wallet application, ” they said .

To avoid problems, the developers recommended Ledger Nano S owners not to use version 0.14 of the client until they receive further notice from the company. Users who will not conduct transactions with allegedly vulnerable software are not at risk.

Recall that in February, the developers of Ledger discovered a problem in the software version 1.5.5 for the Nano S wallet – improvements in the security context affected the memory size of the device.

Follow BlockchainJournal on Twitter !