Looks like an employee mistake. Somebody's gonna get fired.
Not sure if it is a real employee's mistake. It looks like it's an issue with their servers, and I don't think someone would be dumb enough to just dox a bunch of emails. If he/she was though, god damn, I would not like to be him, don't think there is any way they keep their jobs.
No it's really a human mistake, according to them they wanted to adapt their existing software to be able to send the mailing more quickly but they didn't test it before using it.
To remedy this, we built an in-house system to handle the necessary rendering, translation, staging, and piecemeal (as not to trigger rate limits) sending of important email. BitMEX has not sent an email to every customer at once since 2017, and much has changed since then. When we initiated the send, it became clear that it would take upwards of 10 hours to complete, and there was a desire on the team to ensure users received the same material information on a more reasonable timescale.
To handle this, the tool was quickly rewritten to send single SendGrid API calls in batches of 1,000 addresses. Unfortunately, due to the time constraints, this was not put through our normal QA process. It was not immediately understood that the API call would create a literal concatenated “To:” field, leaking customer email addresses. As soon as we became aware, we immediately prevented further emails from being sent and have addressed the root cause. Since then we have been aiding all who have been affected as best we can and mitigating the damage to contain the leak.
And no, nobody seems to have been fired.
BitMEX is a company that takes engineering seriously, and we are disappointed that this lapse in care has resulted in unwanted disclosure for our customers. We believe that processes, not engineers, are to blame for these failures. Our processes failed here. We are working around-the-clock to revamp them and to ensure that even the simplest-looking code changes are put under strict review.
https://blog.bitmex.com/email-privacy-issue-what-is-happening-and-how-can-we-help/