We use NATS.

From what I understand, a very large number, if not all NATS programs (including ours) were affected. As soon as we became aware of the issue (today), we followed the instructions to lock down our NATS program.

The really irritating thing is that TMM has known about this issue for months, but claims they "thought it was limited to a few users" and they threatened to sue OC3 networks (which OC3 told them to fuck off), and then OC3's customers (who asked OC3 to stop) when OC3 started publicly speaking about the issue several months ago.

To be fair to TMM, from everything I've read and understand, there is absolutely no connection between Segpay's systems and the nature of the exploit in NATS, so I would very seriously doubt there is any possible way that any Segpay data could be compromised... it would be no more likely than, for example, CCBill or Epoch data (neither of which is kept in NATS) being compromised.

Nonetheless, this is a very, very serious problem, further compounded by the longstanding lack of transparency and arrogance on the part of TMM.
There's some pretty serious groveling going on over on GFY -- TMM must have either gotten the fear of God in them, or else hired a crisis PR firm, because I've never seen anything remotely this conciliatory and humble from them ever before.

Only time will tell what the outcome is. Once again, the problem itself is forgiveable; every company has hacks and exploits, but what seems to be most upsetting to people is the fact that TMM knew about this problem and didn't notify anyone, and further threatened to sue someone (OC3) who had done extensive research and identified the problems and attempted to bring them to the attention of both TMM and the adult community.