It is irresponsible to use (let alone to hardcode) those addresses in the first place. But in any case, fortunately, software can be patched and it has been done so already in 'tricky' cases: Y2K and X.509 UTCTIME are examples.
My company operates big networks and it caught us off guard when 44/8 got used on the public Internet. Internal tooling used the space because it was assumed to be non-routable. Assumptions like this always carry a risk and sooner or later, they need to be fixed. In our case, a workaround could be produced within hours, and it was fixed within weeks.
0/8 support has been added in the Linux kernel as well.
Edit: scdown.qq.com resolves to 0.0.0.1 and is possibly related to WeChat. I am not sure, if the address is actually routable in China, though.
My company operates big networks and it caught us off guard when 44/8 got used on the public Internet. Internal tooling used the space because it was assumed to be non-routable. Assumptions like this always carry a risk and sooner or later, they need to be fixed. In our case, a workaround could be produced within hours, and it was fixed within weeks.
0/8 support has been added in the Linux kernel as well.
Edit: scdown.qq.com resolves to 0.0.0.1 and is possibly related to WeChat. I am not sure, if the address is actually routable in China, though.