DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

New and very concerning developments following breach involving Disqus comments

Posted on February 5, 2014 by Dissent

Back in December, I noted a breach involving Disqus comments disclosed by a group of investigative journalists calling themselves Research Group (ResearchGruppen) in Sweden. The researchers had been able to identify – and then “out” – pseudoanonymous commenters. Kevin Townsend had some interesting commentary on the case, while Disqus focused on denying any security breach of their system.

The breach actually struck me as pretty serious, because we’ve seen this before where anonymous commenters have been outed for political reasons – with loss of jobs as one result, and/or risk to personal safety as another. Despite the concerns I had, the breach didn’t seem to make the mainstream media here in the U.S.

Today, a Swedish reader contacted me to alert me that there was more to this story.  Automated translations of two Swedish articles (here and here) are pretty abysmal, but it appears that Research Group, in collaboration with Seppuku Media, has now used the information they acquired to start requesting hundreds of individuals’ credit reports – at least 400 so far, if I’m understanding the situation correctly.

It is illegal under Swedish law to request someone’s credit report like this, as a court case cited by Avpixlat article indicates, and I understand that police have received numerous complaints from victims and are investigating the matter.

I do not know whether Swedish citizens can utilize credit freezes that we have here that might prevent others from obtaining their credit reports, but if they can, anyone who used Disqus might want to consider taking that route for now.

It is not clear to me whether Sweden’s regulators have opened any investigation into the credit bureau(s) providing these reports to determine whether they have adequate data security or two-factor authentication or what. AB Bisnode was specifically mentioned in the two articles I read.

But that’s not the full scope of the problem. My correspondent also informed me that user data Research Group had downloaded  has been published on a website in searchable form.  The correspondent believes that Research Group did this to solicit help cracking the other MD-5 email hashes, but I have no way of knowing whether that is accurate or not. I am not posting the link to the user information, but it was sent to me.

Keeping in mind that this started with Disqus, it’s worth re-visiting their initial response:

Disqus offers an API service that includes MD5 hashes of email addresses in order to use Gravatar, a commonly used third party service that enables users to display a consistent avatar across platforms. This appears to be a targeted attack on a group of individuals using pattern matching of their activity across the web, associated with email addresses used by those individuals. To use our API or service for such purposes, is a breach of our privacy guidelines. As in all such cases, we are terminating the account.

​Further, we are disabling Disqus’ use of the Gravatar service and removing the MD5 hash email addresses from the API. We will evaluate any further changes that will need to be made based on these actions.”

But the horse is out of the barn already. What, if anything, can or should Disqus do now? Can it do any takedown request or notice if data acquired from their server via API has been and is being misused? Can they use any copyright laws to prohibit further publication or use of the data?

No related posts.

Category: Non-U.S.Of Note

Post navigation

← Privacy and Security Considerations of Telehealth
FDNY might sell your personal health info? Not so fast…. →

2 thoughts on “New and very concerning developments following breach involving Disqus comments”

  1. Ranger says:
    February 5, 2014 at 6:48 pm

    I’m not sure I understand, how does knowing a person’s Disqus profile help them request credit reports? My understanding is that the group already had a list of people and simply used the MD5 hash to match that real information with anonymous comments.

    I don’t see how making that connection gave them the information they needed to retrieve credit reports. They already had all the information, including the email, before Disqus was involved.

    1. Jan Ove Malmgren says:
      February 6, 2014 at 3:33 am

      They used the Disqus users email addresses retrieved through Disqus API and matched them with addresses used elsewhere and subsequently managed to identify the users. From there it’s a simple matter to find the users real name and their addresses and so forth. Note to self: Never use your public email address other than for public reasons. Use a fake ameal address if you want to express personal views.

Comments are closed.

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Air Force Employee Pleads Guilty to Conspiracy to Disclose Unlawfully Classified National Defense Information
  • UK police arrest four in connection with M&S, Co-op and Harrods cyberattacks (1)
  • At U.S. request, France jails Russian basketball player Daniil Kasatkin on suspicion of ransomware conspiracy
  • Avantic Medical Lab hacked; patient data leaked by Everest Group
  • Integrated Oncology Network victim of phishing attack; multiple locations affected (2)
  • HHS’ Office for Civil Rights Settles HIPAA Privacy and Security Rule Investigation with Deer Oaks Behavioral Health for $225k and a Corrective Action Plan
  • HB1127 Explained: North Dakota’s New InfoSec Requirements for Financial Corporations
  • Credit reports among personal data of 190,000 breached, put for sale on Dark Web; IT vendor fined
  • Five youths arrested on suspicion of phishing
  • Russia Jailed Hacker Who Worked for Ukrainian Intelligence to Launch Cyberattacks on Critical Infrastructure

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • How to Build on Washington’s “My Health, My Data” Act
  • Department of Justice Subpoenas Doctors and Clinics Involved in Performing Transgender Medical Procedures on Children
  • Google Settles Privacy Class Action Over Period Tracking App
  • ICE Is Searching a Massive Insurance and Medical Bill Database to Find Deportation Targets
  • Franklin, Tennessee Resident Sentenced to 30 Months in Federal Prison on Multiple Cyber Stalking Charges
  • On July 7, Gemini AI will access your WhatsApp and more. Learn how to disable it on Android.
  • German court awards Facebook user €5,000 for data protection violations

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.