Security researchers have created a tool to help Snapchat users who are worried that their information was compromised find out if their personal details were released online as part of an attack that affected 4.6 million people as the temporary messaging company works with U.S. law enforcement to find culprits.
Snapchat was hit by a cyber attack on Wednesday, which reportedly exposed many usernames and phone numbers. Estimates put the number of affected users at 4.6 million. The data was posted on a website called SnapchatDB.ingo, which has since been suspended. However, the hackers censored the last two digits of the phone numbers "in order to minimize spam and abuse," but offered to disclose the database "under certain circumstances," according to The Telegraph.
In order to provide users with a means to tell if their information was compromised, Gibson Security has developed a website called GS Lookup where people can enter in their Snapchat username and be told if their data was included in the security leak. The site claims that most of the affected users were in the United States.
The site also offers advice for anyone who finds their details have been leaked: "If your data has been leaked, don't freak out! There are a few things you can do if you've been affected.
First and foremost, you can delete your Snapchat account here - sadly, this won't remove your phone number from the already circulating leaked database."
The site continues saying, "If you feel that you'd rather unscrupulous entities not potentially have your phone numberm you're free to contact your phone TelCo, and request that they give you a new number. If you detail the breach, they'll almost certainly give you a new one.
Lastly, ensure that your security settings are up to scratch on your social media profiles. Be careful about what data you give away to sites when you sign up - if you don't think a service requires your phone number, don't give it to them."
You can check and see if your Snapchat account has been affected HERE via GS Lookup.
