It appears that this is actually aFirefox exploit that was patched a while back. Hurray for auto-updating browsers. I read suggestions of using a LiveCD, but th

It appears that this is actually aFirefox exploit that was patched a while back. Hurray for auto-updating browsers. I read suggestions of using a LiveCD, but that seems like it would leave you stuck to security fixes like this. If you were using Tails you could at least have had a random MAC (https://tails.boum.org/contribute/design/MAC_address/ https://tails.boum.org/contribute/design/MAC_address/), but this attack could have been a lot worse if it wanted more than the MAC. Since the OP didn't mention it, here's the gist of what happened: 1) A bug in Firefox related to the onreadystatechange event could end up arbitrarily executing memory on a page reload. 2) The attack created a Windows executable using JavaScript's typed arrays and array buffers (pretty interesting in its own right) 3) The executable phones home with a MAC address and Windows hostname