No, no, this happened just after 2.0.7 came out and apparently we didn’t put in the patch notes that we’d fixed a remote code exploit, so they didn’t update to 2.0.7. So yeah it was apparently our fault they got hacked.
Never mind that it wasn’t a remote code exploit and nothing to do with what changed between 2.0.6 and 2.0.7. It was apparently our fault they did what they did.
Seeing how I’m the one who personally made the 2.0.7 patch, I was less than enthused by this course of actions.