ESET's blog said:
BleepingComputers, upon notification, immediately pulled the infected executables and shortly after that, sUBs issued an apology and an explanation. In short, the combination of being overly busy working for a good cause and a faulty mouse issuing a double-click rather than a single click while looking at malware in an infected archive triggered the infection of his system. It is true but unhelpful to state that malware should never be looked at and handled on a production system as it only takes a minor mistake as this one to cause an infection on production software..
Production systems are indeed not the best place to mess around with malware samples.--
Limited User Accounts.
Software Restriction Policies.