The following is perhaps the worst way to tweet about the incident.
The user admits using his NetGalley password for several other accounts.
While that tweet might have been a joke, this next one certainly isnt.
There were other milder tweets, in which users admitted that their NetGalley account wasnt under their real name.
But the NetGalley breach was already bad, to begin with.
When revealing security breaches, most companies explicitly state the measures they have taken to protect users data.
But by then, the damage had already been done.
And theres nothing to prove they didnt have access to the data much sooner.
As the first tweet I shared suggested, users oftenreuse their passwords across many accounts.
After the NetGalley hack, the attackers have access to a fresh list of emails and passwords.
Cross-service account hijacking is somethingthat happens oftenand can even include high-profile tech executives.
So, alone, the NetGalley data breach might not look like a big deal.
Some users have dismissed the hack as harmless.
To be clear, this doesnt mean you shouldnt tweet about data breaches.
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.
Its not worth it.
The point is, the dark web is already replete with sensitive information about billions of users.
Dont make things worse by revealing more information about yourself and others through careless tweets.
you could read the original articlehere.
Also tagged with
