Monero cryptocurrency fixes “the burning bug”

Posted: 26 September 2018 4:21 pm
shutterstock monero hot cold 450x250
{"theme":"dark","direction":"horizontal","showArrows":true,"splitTitle":true,"playerOptions":{"captions":true,"popupOnScroll":true,"subscribe":{"title":"Subscribe","url":"","visibleOnMain":true,"visibleOnPopup":true}},"active":{"index":0,"start”:1480,”end":null,"thumb":"","thumbAnimation":"kenburns-top-right","heading":{"small":"WATCH","large”:”XMR not alone - hidden bug in bitcoin code revealed”}},”yt":{"method":"videos","params":{"id":"0W4vAdqq5g8,8aIyxLawKkI,oOtfcgktxEo,k7FMeXTjl0g,qei8JC84MvQ"}},"banner":true}

There's a fine line between "there's nothing to worry about" and "we've discovered a critical bug."

The burning bug sounds like an STI and works kind of like one too.

What starts off as a good time – getting XMR deposited into a wallet – turns into a nightmare when the recipient is left with an unshakeable case of the burning bug, which functionally takes the form of unspendable funds. It's been observed in the wild as a hypothetical illness, but so far there are no confirmed cases of human transmission.

But rather than wait until there is, Monero developers have gone ahead and vaccinated it out of existence – just to really stretch the analogy to breaking point.

In more literal terms:

  • A theoretical burning bug attack was described well over a year ago. It was widely dismissed as being too impractical to be a cause for concern.
  • Nine days ago, from the time of writing, someone re-discovered the burning bug, and Reddit user s_c_m_l accidentally worked it into a practical attack with a hypothetical question.
  • Monero developers said "actually, yeah" and patched the bug out of existence.

Anatomy of the burning bug

The attack itself hinges on an anomaly in Monero's stealth addresses, in which multiple transactions of the exact same amount will get assigned the same key image. These will functionally mean the transactions are identified by the network as the exact same transactions, which would be interpreted and blocked as an attempted double spend attack. All but one of those transactions will be deemed invalid, and the coins "burned." Hence the name burning bug.

By itself, the attack is just a way for a suitably motivated person to destroy their own money.

The actually quite straightforward twist is what happens when someone carries out the attack after sending the funds to an exchange's wallet and selling the burned coins. It doesn't actually gain the attacker anything, and in fact comes at a cost, but the cost was relatively low, making it a potential attack vector for someone who wants to economically attack an exchange by destroying their money, even at no personal gain.

"Practically speaking this bug is exploited as follows," Monero developer dEBRUYNE explains. "An attacker first generates a random private transaction key. Thereafter, they modify the code to merely use this particular private transaction key, which ensures multiple transactions to the same public address (e.g. an exchange's hot wallet) are sent to the same stealth address.

"Subsequently, they send, say, a thousand transactions of 1 XMR to an exchange. Because the exchange's wallet does not warn for this particular abnormality (i.e. funds being received on the same stealth address), the exchange will, as usual, credit the attacker with 1000 XMR. The attacker then sells his XMR for BTC and lastly withdraws this BTC. The result of the hacker's action(s) is that the exchange is left with 999 unspendable / burnt outputs of 1 XMR.

"Fortunately, the bug did not affect the protocol and thus the coin supply was not affected."

juicy crypto words

To roll out the patch as quickly as possible, the developers notified all exchanges they were in contact with and sent out an email to those on the Monero mailing list.

"This event is again an effective reminder that cryptocurrency and the corresponding software are still in its infancy and thus quite prone to (critical) bugs," said the Monero announcement.

It seems unfortunate that even though the bug has been known for over a year, it's only recently that someone actually thought about it one step further. The leap from hypothetical useless vulnerability to practical attack was tiny and seems like it should have been a bit more obvious.

But things are always more obvious in hindsight. Plus, plenty of exchanges have listed Monero over the years, and despite being the ones predominantly at risk, it seems none of them independently discovered it either.

Disclosure: At the time of writing, the author holds ETH, IOTA, ICX, VET, XLM, BTC and ADA.

Disclaimer: This information should not be interpreted as an endorsement of cryptocurrency or any specific provider, service or offering. It is not a recommendation to trade. Cryptocurrencies are speculative, complex and involve significant risks – they are highly volatile and sensitive to secondary activity. Performance is unpredictable and past performance is no guarantee of future performance. Consider your own circumstances, and obtain your own advice, before relying on this information. You should also verify the nature of any product or service (including its legal status and relevant regulatory requirements) and consult the relevant Regulators' websites before making any decision. Finder, or the author, may have holdings in the cryptocurrencies discussed.

Crypto explained


Latest cryptocurrency news

Picture: Shutterstock

Get into cryptocurrency

Ask an Expert

You are about to post a question on

  • Do not enter personal information (eg. surname, phone number, bank details) as your question will be made public
  • is a financial comparison and information service, not a bank or product provider
  • We cannot provide you with personal advice or recommendations
  • Your answer might already be waiting – check previous questions below to see if yours has already been asked

Finder only provides general advice and factual information, so consider your own circumstances, or seek advice before you decide to act on our content. By submitting a question, you're accepting our Terms of Use, Disclaimer & Privacy Policy and Privacy & Cookies Policy.
Go to site