Attacks/Breaches
3/5/2014
01:05 PM
50%
50%

Bitcoin Heists Cause More Trouble

Attackers continue to pummel bitcoin "banks," exchanges, and crypto-currency users themselves via malware that steals virtual wallets.

Self-styled bitcoin "bank" Flexcoin this week announced that it's been forced to shut down after online thieves stole 896 bitcoins, worth nearly $600,000.

"As Flexcoin does not have the resources, assets, or otherwise to come back from this loss, we are closing our doors immediately," the Alberta, Canada, based company said in a statement. "Having this be the demise of our small company, after the endless hours of work we've put in, was never our intent. We've failed our customers, our business, and ultimatley (sic) the Bitcoin community."

The bitcoin bank generated profits by charging users 0.01 BTC (bitcoins), or 0.005% of the total transfer amount -- whichever was greater -- whenever they transferred bitcoins outside of Flexcoin. Users earned "interest" on their deposits in the form of discounts on their own out-of-bank transfers.

This is but the latest in a string of recent incidents that have rocked the crypto-currency system.

Flexcoin: Hackers exploit withdrawal system flaw
The Flexcoin hacker exploited the fact that bitcoins could be freely transferred from one Flexcoin account to another. "By sending thousands of simultaneous requests, the attacker was able to 'move' coins from one user account to another until the sending account was overdrawn, before balances were updated," according to the company's statement.

Anyone who had funds stored in Flexcoin's Internet-connected "hot wallet" won't get them back. While the three-year-old Flexcoin advertised itself as "the bitcoin bank," as the company noted in its terms of service, "technically we're not a licensed bank," and that "Flexcoin Inc is not responsible for insuring any bitcoins stored in the Flexcoin system."

[Are bitcoins already passé? See Bye, Bitcoin: Criminals Seek Other Crypto Currency.]

On the upside, however, the attacker didn't steal bitcoins stored in Flexcoin's offline, cold-storage service. Flexcoin said it would be contacting anyone with bitcoins in cold storage and transferring the virtual currency to them directly, after first verifying their identity.

Mt. Gox shutdown: Source code leaked
Flexcoin's failure follows the demise of Mt. Gox, which was once the world's third-largest bitcoin exchange. Friday, the Japan-based company filed for bankruptcy, saying that hackers stole about $500 million in bitcoins stored by the site.

Evidence that the 850,000 missing bitcoins were obtained via a hack attack arrived Sunday, when 1,719 lines of PHP code were posted to Pastebin. The code included the SSH keys required to connect to Mt. Gox's transaction-processing server, which would have allowed an attacker to redirect transactions or drain users' bitcoin wallets, Ars Technica reported.

Last week, Flexcoin boasted about not being affected by the Mt. Gox shutdown. "We hold zero coins in other companies, exchanges, etc.," Flexcoin tweeted. "While the Mt. Gox closure is unfortunate, we at Flexcoin have not lost anything."

Poloniex hacked: Owner launches bitcoin reimbursement program
Flexcoin and Mt. Gox weren't the only crypto-currency exchange -- a.k.a. "darkcoin trading" -- sites to have been successfully exploited in recent weeks. Notably, crypto-currency exchange Poloniex Tuesday revealed that an online attacker successfully stole 12.3% of the exchange's bitcoins -- worth about $50,000, based on the attacker's Bitcoin address and the currency's market value that day -- after exploiting a flaw in the site's withdrawal system. The attack was stopped, however, after the exchange's security controls noticed unusual withdrawal activity.

The flaw allowed the attacker to withdraw more money than his or her account balance should have allowed because the system failed to process withdrawals in a sequential fashion. "The hacker discovered that if you place several withdrawals all in practically the same instant, they will get processed at more or less the same time," Poloniex owner "Busoni" said on Bitcoin Forum. "This will result in a negative balance, but valid insertions into the [Poloniex] database, which then get picked up by the withdrawal daemon."

"I take full responsibility for this and am committed to repaying the debt of BTC," Busoni said. But to prevent a run on the exchange's bitcoins, he

Next Page

Mathew Schwartz served as the InformationWeek information security reporter from 2010 until mid-2014. View Full Bio

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
asksqn
50%
50%
asksqn,
User Rank: Ninja
3/5/2014 | 4:21:58 PM
Rotten in Denmark
I can't help but think that the utter annihilation of cryptocurrency is a concerted effort by the central banking cartel to destroy the threat Bitcoin et al. clearly poses to the status quo.
Mathew
50%
50%
Mathew,
User Rank: Apprentice
3/6/2014 | 4:27:47 AM
Re: Rotten in Denmark
I think Bitcoin's troubles come from within. The developer/chief behind Mt. Gox, for example, didn't code clean-enough code to prevent very, very patient attackers from finding a way to exploit the exchange. Likewise, Internet-connected virtual wallets are a sitting duck.

There are now more than 30 cryptocurrencies available. If Bitcoin dies, many more can take its place. I'd say this is less a fatwa against cryptocurrencies, and more of a Darwinian thing. Which, when you're dealing with developing stable monetary systems, is exactly how it should be.
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3407
Published: 2014-11-27
The SSL VPN implementation in Cisco Adaptive Security Appliance (ASA) Software 9.3(.2) and earlier does not properly allocate memory blocks during HTTP packet handling, which allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCuq68888.

CVE-2014-4829
Published: 2014-11-27
Cross-site request forgery (CSRF) vulnerability in IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allows remote attackers to hijack the authentication of arbitrary users for requests tha...

CVE-2014-4831
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to hijack sessions via unspecified vectors.

CVE-2014-4832
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to obtain sensitive cookie information by sniffing the network during an HTTP session.

CVE-2014-4883
Published: 2014-11-27
resolv.c in the DNS resolver in uIP, and dns.c in the DNS resolver in lwIP 1.4.1 and earlier, does not use random values for ID fields and source ports of DNS query packets, which makes it easier for man-in-the-middle attackers to conduct cache-poisoning attacks via spoofed reply packets.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?