Skip to main content

Social Strata hacked, Ars Technica users being spammed

Ars Technica used to use a service from Social Strata for the their forums, I say used to, because some time ago, they moved off of the platform. But apparently, Social strata did not delete the information from their servers. Hmm.. Okay.

So, as it would come to pass, Social Strata's server (one of them apparently) was rooted, I think the cause of which is still being investigated, but anyway, they got rooted. The only thing that was gotten a hold of was email addresses. So the users of Ars Technica's forums from that long ago started receiving phishing emails.

While it's important that the passwords were not compromised, the moral of this story is that companies and users need to check with cloud-based server provider's license agree to see what the retention clause is on the data, or at least make sure there is one. When you leave a service, you can't immediately assume that your data is leaving that service too.

Be careful out there. Below is a transcript of the forum post with a bit more detail. Supposedly, if you were affected, you would receive the following in an email as well.

This stresses the importance of good password control (don't use the same password for several different sites), and the importance of having a disposable email address that you can use to set up forum accounts, finally, good spam filters to catch that phishing if the unthinkable does actually happen.



Hello,

You are receiving this message because you have a registered an Ars Technica account with this email address.

Our previous forum provider (Social Strata, formerly known as Groupee and Infopop) had a server hacked recently, and has advised us that private registration email addresses were harvested. These included email addresses for anyone who registered with Ars Technica while we were still using their services. In addition, the rooted server was used to send out at least one mass phishing attempt.

Although Groupee/Social Strata tells us that no password information of any kind was accessible from that server, we still recommend that you change your Ars Technica password (and any account on a third party site you use that password with) just to be safe.

We became aware of this issue this morning and are following up with Groupee/Social Strata to see if we can get more details and assurances on the scope of the compromise. We have also requested that they purge all Ars Technica data from their systems so future problems don't affect our users.

We apologize for any inconvenience this may have caused. If you would like to read further updates on this issue, please see the active announcement we have in our new forums:
viewtopic.php?f=3&t=1108748

Please contact us with any questions.

Update:

One of Social Strata/Groupee's servers got rooted and was used to both harvest private emails and send out spam. I'm trying to get clarification on what exact data was accessible from that server (since their report wasn't quite clear). They claim that passwords weren't stolen, just email addresses.

Original post:

It seems that many users received phishing attempts to Ars only email addresses this morning. We're working on it and will update this post when we find something out.

We believe that our previous forum provider has some exploit that allows people to send messages to private email addresses through their servers. Every report we've seen has originated at one of their web front ends. If we are correct, your email addresses have not been compromised. It's obviously pretty bad to be getting phishing attempts forwarded through someone else, but not quite as bad as if an email DB had been jacked or something.

We have emails out to them. There's a chance we won't hear back for a couple of hours since they're on pacific time, but we're doing what we can.

Comments

[...] This post was mentioned on Twitter by JoelEsler, Christopher Clark, Roer.com - the Blog!, Avnet SolutionsPath™, Niels Groeneveld and others. Niels Groeneveld said: RT @JoelEsler: #SocialStrata hacked, #ArsTechnica users being spammed http://bit.ly/9wrqdF #cybersecurity #hacking #infosec #spam [...]

Popular posts from this blog

Offset, Depth, Distance, and Within

Without going off the deep-end here and discussing every single Snort rule keyword, I just wanted to touch on a few modifiers that people sometimes misunderstand.  They aren't difficult, and hopefully after this explanation and a few examples, I can clear some of the air around these five modifiers.

The five modifiers that I am talking about are
OffsetDepthDistanceWithinnocaseThese five modifiers are not keywords of themselves, but rather they apply as modifiers to another keyword.  That keyword is "content". The content keyword is one of the easiest pieces of the Snort rules language as all it does is look for a particular string.  So for instance if I wanted to look for the word "joel" within a packet.  A simple:
content:"joel";Would allow me to do that.  The interesting part comes into play when you want to specify where inside of a particular packet you want the string "joel" to be looked for.  If you are running just a plain content ma…

Writing Snort Rules Correctly

Let me start off by saying I'm not bashing the writer of this article, and I'm trying not to be super critical.  I don't want to discourage this person from writing articles about Snort rules.  It's great when people in the Snort community step up and explain some simple things out there.  There are mistakes, it comes with the territory.  If you choose to be one of the people that tries to write Snort rules, you also choose to be someone who wants to learn how to do it better.  That's why I write this blog post, not to bash the writer, but to teach.

I noticed this post today over at the "Tao of Signature Writing" blog, and to be honest I glanced over most of it figuring it was a rehash of things I've already read or things that have already been written from countless people about "Here's how you write Snort rules!".  I scrolled down quickly skimming, not reading at all really, and noticed this part:
Now, let us look at the second questio…

Safari 5.1.4 now available

Safari 5.1.4 now available, fixes issues and improves performance | TUAW - The Unofficial Apple Weblog:


Improve JavaScript performanceImprove responsiveness when typing into the search field after changing network configurations or with an intermittent network connectionAddress an issue that could cause webpages to flash white when switching between Safari windowsAddress issues that prevented printing U.S. Postal Service shipping labels and embedded PDFsPreserve links in PDFs saved from webpagesFix an issue that could make Flash content appear incomplete after using gesture zoomingFix an issue that could cause the screen to dim while watching HTML5 videoImprove stability, compatibility and startup time when using extensionsAllow cookies set during regular browsing to be available after using Private BrowsingFix an issue that could cause some data to be left behind after pressing the "Remove All Website Data" button