Perhaps if attacks are predominantly coming from Malaysia, we should begin deprioritizing Malaysian IP ranges. There are geo-IP services that we can trust as a third party to compile lists of such suspicious IP ranges, too.

All that some of us ask is that people stop supporting unnecessary centralized solutions. Just admit that there are better ways to approach DDOS attacks.
Indeed, like simply having nodes deprioritize IPs that are actively attacking them. This is a simple, decentralized solution that requires no third party trust. Why aren't XT supporters at least lobbying Gavin Anderson and Mike Hearn to change this? Rather than arguing that it's "innocent?"
because that is what Hearn wanted to do all along and because it is not simple:
Please read the roadmap at the top. The next step is to handle multiple connections from single IPs better, and to allow user-configurable priority lists. Then a quick fix would be to drop your little botnet IPs into a file and give it lower priority than Tor. After that, Tor connections would evict the botnet.
Then after that, there needs to be ways for a node to figure out priorities automatically, for instance by defining a utility function that doesn't rate all mobile connections as low utility. This is very hard, especially as the code would be open source, but is obviously the gold standard to aim for.
This is all a lot of work. Contributions of some additional logic to get us further along the path would be appreciated.
https://github.com/bitcoin/bitcoin/pull/6364