RacingPost Attacked, Customer Information Compromised
RacingPost.com went through a cyber-attack from November 22 - 23, 2013 which resulted in customer data being compromised.
In what the UK-based betting site called a "sophisticated, sustained and aggressive attack," hackers accessed one database in which they were able to obtain unencrypted customer information and encrypted passwords.
The RacingPost site said that the information taken from the database would vary based on what information each customer provided when they registered. Unencrypted data taken by the hackers included usernames, users' first and last names, email addresses, customer addresses, and date of birth.
About the Author
Bill Oliver has been working in Healthcare for the past 30+ years in a variety of management roles including Material Management, Purchasing, Nurse Registry, and IT. In the past 12 years his focus has been on the business end of IT Contracts, Software Licensing and Purchasing.
RacingPost could not guarantee that its password encryption was hacker-proof. "As a consequence, customers have been advised by email that they should take the precaution of changing their password on other sites if it is the same one that they use for racingpost.com," stated a notice on their website.
The website's press release also implied that financial information was not exposed during the attack, stating "customer credit and debit card details are not stored on the site and have therefore not been accessed and are not at risk."
"Security is an area we take extremely seriously and our website has not been compromised previously. As soon as we were aware of the situation we did everything in our power to halt the breach," said Racing Post editor Bruce Millington. "As part of our efforts to resolve the issue, we have turned off the ability to register / log-on to racingpost.com. You will still be able to access the site safely. Members' Club content will also be available."
The site is assuring its customers that "stringent new measures are being put in place to prevent a repeat of the malicious attack on our database that has affected users of racingpost.com."