Good intentions, and it provides valuable functionality. But ultimately it isn't going to put a dent in the issue. It's still a plugin that you need to install and activate and the vast majority of WordPress users simply aren't going to do so. Not only that, but they will have never even known about it.

An issue this large and widespread needs to be addressed within the project itself. At it's very core.

Nagging people to update is also not the answer. Neither is education because you're not going to reach everyone that needs to be reached.

One solution that will help is more widespread use of background automatic updates.

That is not a popular idea in some circles of the WordPress development community but i've yet to hear anyone that knows of viable solutions to this problem that would have a greater impact or even any real impact at all.

Those developers seem to forget that if it's not for them they can simply disable it. Because... hooks and filters are cool like that.

I'm beating a dead horse here as i've already expressed this opinion numerous times. But issues related to widespread exploitation of vulnerable out of date WordPress installs is not going to go away and will only get worse as WordPress continues to grow in marketshare.