Russian Nuclear Scientists Arrested For 'Bitcoin Mining Plot' (bbc.com)

Russian security officers have arrested several scientists working at a top-secret Russian nuclear warhead facility for allegedly mining crypto-currencies, BBC reported Friday, citing local media. From the report: The suspects had tried to use one of Russia's most powerful supercomputers to mine Bitcoins, media reports say. The Federal Nuclear Centre in Sarov, western Russia, is a restricted area. The centre's press service said: "There has been an unsanctioned attempt to use computer facilities for private purposes including so-called mining." The supercomputer was not supposed to be connected to the internet -- to prevent intrusion -- and once the scientists attempted to do so, the nuclear centre's security department was alerted. They were handed over to the Federal Security Service (FSB), the Russian news service Mash says. "As far as we are aware, a criminal case has been launched against them," the press service told Interfax news agency.

Comments

Easy to do without oversight

[Anonymous Coward]

Posting this anonymously, even though I'm pretty sure the statue of limitations is long past.

Many years ago I got a job for SGI on site at big customer. This was back when the Origin 2000 was the new hotness. This site had a whole O2k buildout (3 or 4 racks worth of compute cores, 32 R10k MIPS processors clocked at around 200Mhz all connected via these thick cable bundles into a hypercube topology IIRC) purely for benchmarking and compatibility testing. They were used only sporadically. This was also the time when the distributed.net RSA cracking challenge was running. So obviously I set up a process that would run distributed.net across all of the cores, but would also monitor for any access to the machine and shut the whole thing down, not so much because I was trying to hide it but because I didn't want to impact any tests other people wanted to run. I also made it so I had to start it manually after verifying that the machine was truly idle. The only problem was that the machine had LEDs that indicated CPU activity, and when the process was running they would be full up, but as soon as someone logged in to investigate they would be gone. Luckily nobody who worked there was the suspicious type.

After one long weekend I came back to discover that my aggregation machine (The O2k didn't talk directly to distributed.net servers, I ran a local server to cut down on the internet traffic) had suffered a drive failure and had been down for several days. I took the morning to get the aggregation server restarted and working. A couple of days later one of my friends mentioned that I was #3 for that day on the distributed.net statistics page. Oops.