the National Science Foundation (NSF) revealed that more than $8,000 (£4,760) worth of bitcoins had been generated from NSF-funded computers. 
The researcher said he was conducting tests. 
Equipment worth $150,000 (£89,230) at the government-backed organisation was used to mine the digital currency.

A member of the Harvard community was stripped of his or her access to the University’s research computing facilities last week after setting up a “dogecoin” mining operation using a Harvard research network. 
The individual in question allegedly utilized the high-powered network that Harvard calls the “Odyssey cluster” to collect the coins.
The Odyssey cluster is a bunch of computers networked together in a way that allows fast data transfer between processors. 

Frozen Funds
In preparation of the following, we have with immediate effect stopped the possibilities to withdraw BTC, LTC, FTC and TRC. All incoming deposits will also not be credited to the users accounts for the time being. 
On 24th March 2014 we will be freezing the current BTC, LTC, TRC and FTC accounts, then perform the below distribution of the available coins and reenable deposits and withdrawals. This action will also require us to delete all open sell orders for BTC, LTC, FTC and TRC. 
As you may very well be aware, we had two incidents last year that lead to a loss of a significant number of BTC, LTC, FTC, TRC. We had communicated at that time that we will be covering those losses from our income, which we have done so far. We had enough coin balances in our cold wallet to upkeep our platform and the positive cashflow enabled us to gradually refill the wallets.
Unfortunately we had large fund withdrawals in the last weeks which have lead to a complete depletion of our cold wallet balance and we are now facing the option of either closing the site with significant unrecoverable losses for all or to work out a solution that allows the exchange to continue to operate and gradually pay back the losses.

Transaction malleability-related fixes
--------------------------------------
This release contains a few fixes for transaction ID (TXID) malleability 
issues:
- -nospendzeroconfchange command-line option, to avoid spending
  zero-confirmation change
- IsStandard() transaction rules tightened to prevent relaying and mining of
  mutated transactions
- Additional information in listtransactions/gettransaction output to
  report wallet transactions that conflict with each other because
  they spend the same outputs.
- Bug fixes to the getbalance/listaccounts RPC commands, which would report
  incorrect balances for double-spent (or mutated) transactions.
- New option: -zapwallettxes to rebuild the wallet's transaction information

So you can sit on the network, watch for transactions, and echo them with the signatures slightly tweeked, but still valid.  These new transactions will have different hashes, and will compete with the original transactions for inclusion in a block. When a cloned transaction beats out the original for block inclusion, it will leave the original in the owners wallet unconfirmable forever, resulting in inconvenience and unspendable coins.  Quick echoing and network latency gives this a finite chance of happening.
Of course, you can't create or destroy coins with this, and the money still winds up at the right destination. However, the typical user isn't going to know how to restore an old wallet and rescan the block chain to get his bitcoin client back to working condition.
It might be a good idea to patch this before some enterprising person with excess time on their hands (cough) makes a cloned transaction echobot.