The database in question included sensitive user information, including usernames and passwords, names, email addresses, mailing addresses, birthdays, company names, and Kindle email addresses.<\/p>\n
Unfortunately, many users took to social media and started discussing the incident without thinking about what they are putting up for everyone to see. And in their haste to be the first to tweet about the breach, many users made awful mistakes, which could further compromise their security.<\/p>\n
The following is perhaps the worst way to tweet about the incident. The user admits using his NetGalley password for several other accounts.<\/p>\n While that tweet might have been a joke, this next one certainly isn\u2019t. The user posted an image of the NetGalley advisory email that contained her full name (covered in image). Since the Twitter account name is pseudonymous, the user just revealed the full name of the person behind it.<\/p>\n There were other milder tweets, in which users admitted that their NetGalley account wasn\u2019t under their real name. Less dangerous tweets were by users who admitted they had a NetGalley account, and they had just learned of the hack and had either changed their password or deleted their accounts.<\/p>\n At first glance, many of these tweets might look harmless because NetGalley doesn\u2019t store very sensitive information such as bank account and credit card data. But the NetGalley breach was already bad, to begin with.<\/p>\n When revealing security breaches, most companies explicitly state the measures they have taken to protect users\u2019 data. For instance, many organizations quickly point out that leaked passwords were <\/span>encrypted or hashed<\/a>, which makes it hard (but not impossible) for the attackers to access the accounts. There is no mention of encryption in neither the original advisory nor the updated version published on NetGalley\u2019s website on Sunday, which suggests the hacked database stored user passwords and other information in plain text.<\/p>\n [Read: Meet the 4 scale-ups using data to save the planet<\/span><\/a>]<\/em><\/p>\n On December 23, when NetGalley sent the first advisory, the company invalidated all login credentials and notified users that they will have to reset their passwords the next time they try to log in. But by then, the damage had already been done. The hackers defaced the website on December 21, as users had pointed out on Twitter and the company confirmed in the advisory. And there\u2019s nothing to prove they didn\u2019t have access to the data much sooner.<\/p>\n <\/a><\/div>\n<\/div>\n<\/figure>\n Even if the company had invalidated passwords before the attackers had the chance to use them, the data would still be valuable to them. As the first tweet I shared suggested, users often <\/span>reuse their passwords across many accounts<\/a>. After the NetGalley hack, the attackers have access to a fresh list of emails and passwords. They can use this information in credential stuffing attacks, where they enter the login information obtained from a data breach on other services and possibly gain access to other, more sensitive accounts. Cross-service account hijacking is something <\/span>that happens often<\/a> <\/span>and can even include high-profile tech executives.<\/p>\n The attacks can also combine the data from the NetGalley breach with the billions of user account records leaked in other data breaches to create more complete profiles of their targets.<\/p>\n So, alone, the NetGalley data breach might not look like a big deal. But when viewed in the context of other security incidents and the growing sophistication of cyberthreats, every piece of information that falls into the hands of malicious actors can become instrumental to a larger attack.<\/p>\n Some users have dismissed the hack as harmless. As one user said, \u201cWhat\u2019s the worse [sic] that can happen, somebody gonna write a review posing as me?\u201d<\/p>\n The real answer is, \u201cNo, the <\/span>worst<\/em> <\/span>that can happen is that some threat actor can use your data and all the other public information they can gather about you, and use them to attack you from another, more sensitive spot.\u201d<\/p>\n To be clear, this doesn\u2019t mean you shouldn\u2019t tweet about data breaches. In fact, I found plenty of good information about the data breach on Twitter, like this user who first raised concern about the leaked data possibly being unencrypted\u2026<\/p>\n \u2026 and this other tweet that shared some decent tips.<\/p>\n <\/a><\/div>\n<\/div>\n<\/figure>\n It\u2019s also fine to criticize the way the company handled the breach, though I would advise against spreading conspiracy theories that would only add to the confusion.<\/p>\n But in general, you must be very careful when posting information on social media about data breaches. So, before posting about a security incident, stop and think twice. If what you\u2019re about to share reveals any personal information about you or someone else, such as services you\u2019re using, your devices, email address, location, and IP address, then resist the urge to post something witty to your followers. It\u2019s not worth it.<\/p>\n The point is, the dark web is already replete with sensitive information about billions of users. Don\u2019t make things worse by revealing more information about yourself and others through careless tweets.<\/p>\n This article was originally published by Ben Dickson<\/span><\/i> on <\/span><\/i>TechTalks<\/span><\/i><\/a>, a publication that examines trends in technology, how they affect the way we live and do business, and the problems they solve. But we also discuss the evil side of technology, the darker implications of new tech and what we need to look out for. You can read the original article here<\/a>.<\/span><\/i><\/p>\n![\"NetGalley](\"https:\/\/i2.wp.com\/bdtechtalks.com\/wp-content\/uploads\/2020\/12\/NetGalley-data-breach-tweet.png?resize=696%2C150&ssl=1\")
<\/a><\/figure>\n![\"NetGalley](\"https:\/\/i2.wp.com\/bdtechtalks.com\/wp-content\/uploads\/2020\/12\/NetGalley-data-breach-tweet.jpg?resize=696%2C446&ssl=1\")
<\/a><\/figure>\n![](\"https:\/\/cdn0.tnwcdn.com\/wp-content\/blogs.dir\/1\/files\/2021\/01\/Screenshot-2021-01-06-at-10.16.45.png\")
<\/figure>\n![\"NetGalley](\"https:\/\/i0.wp.com\/bdtechtalks.com\/wp-content\/uploads\/2020\/12\/NetGalley-data-breach-tweet-1.png?resize=696%2C447&ssl=1\")
<\/a><\/figure>\n![](\"https:\/\/cdn0.tnwcdn.com\/wp-content\/blogs.dir\/1\/files\/2021\/01\/Screenshot-2021-01-06-at-10.18.22.png\")
<\/figure>\n<\/div>\n<\/div>\n<\/figure>\n![](\"https:\/\/cdn0.tnwcdn.com\/wp-content\/blogs.dir\/1\/files\/2021\/01\/Screenshot-2021-01-06-at-10.18.42.png\")
<\/figure>\n![\"netgalley](\"https:\/\/i1.wp.com\/bdtechtalks.com\/wp-content\/uploads\/2020\/12\/netgalley-data-breach-tweet.png?resize=696%2C237&ssl=1\")
<\/a><\/figure>\n