This is the first security issue that I have heard about with NATS, and it wasn't even with the NATS program itself but instead with the process of TMM storing an admin u/p on their server....and it was that storage server that got comprimised.

If a program owner has taken the right measures, they are secure and safe from this issue. TMM has also implemented new policies and new logging tools to ensure that this does not happen again.

In comparison, think about the number of security issues that have been (and continue to be) discovered with Windows, Apache, PHP, MySQL, etc, etc, etc..... but its not like you stop using these, instead you patch your system and implement as many security and auditing measures as possible.

If a program has a strong set of sites, good support and has already actioned this issue then stopping promoting them is a huge overreaction.