It's still a problem in the largest deployment. Does anyone have a "solution" to this?
In this specific case, it seems like what they really should do is have a set of trusted nodes for ledger replication.
W.r.t. having a set of trusted nodes, that's fine, however does the blockchain add anything in this situation?
Satoshi didn't coin the term blockchain and they existed for a long time before bitcoin so giving him sole claim to it because it paired it with a feature that isn't specifically required to have a blockchain seems silly.
That said I do agree that their are a lot of buzzword vultures using it at the moment for stupid business ideas though I think 99% of the bitcoin business ideas are poorly thought out and poor replacements for existing solutions("but with bitcoin!") so it's no surprise 99% of the blockchain ones are too.
The real reason behind techniques such as PoW instead of just Distributed Byzantine Fault Tolerance algorithms is scaling in terms of number of validators. Most of DBFTs (afaik Algorand is the only exception) don't really scale. Proof of Authority behaves similarly to PoW, since it also does not have that problem.
Go with DBFT unless you want to have huge number of validators.
In the original form though, it makes no sense to fire up your own bitcoin, because when it's small it's vulnerable to the attack you mention.