If it is true that like stated on mtgox.com not only Bitcoins, but also fiat-money was stolen by hackers, taking the possibility that Mt. Gox is not lieing here,

then I start asking my selfe if this is not likely a job done by the same professionals who already finished up Sadam Hussein and Mohamal Gadafi only because they saw them as a thread for the dollar as world currency.
 

@jedisurfer

I asume that if the loss of Mt. Gox is really caused by  "transaction malleability" then the resending was not doen after e-mails to Mt. Gox support, but the bug in the Mt. Gox system was rather that such resending was triggered automatically whenever an automatic check in the blockchain for a transaction-ID still failed after a certain maximum time.
 

Wouldn't it be interesting to know at first how Mt.Gox dealt with malicious transactions that went in the blockchain?

The 2 possibilities I can think of are:

1. they send the bitcoins a 2nd time because they belive the transaction didnt take place. (bad)

2. they do nothing unless they are asked for the money by the reciever, but keep in their accounting that the money was not spent. (not really a problem as long as they don't use the money they already sent but still belive to have otherwise)

They really lost money only in case 1 or if they sent again after being asked for it in case 2.

Malicious transactions can be spotted in the Blockchain and it should be also possible to find the ones where the same transactin was done a 2nd time after a malicious one.

What about finding all theese cases in the blockchain and adding up the number of bitcoins that were actually sent twice because of malleability. This should give the amount of bitcoins that were sent unitentionally to persons who didnt deserve them and thereby the muximum loss that might have been caused by malleability.

It looks very interesting to me to compare this result with the number of bitcoins that Mt.Gox claims to have lost because of malleability.
 

#582XX 1.0 bitcoin ca. 1.1.2014 hanging (requested). Ticket from maybe 15th with request for "staff action" unanswered.