My spaces rudating validating against xsd schema


10-Oct-2020 03:28

Update: Since writing this piece, My Space have posted a blog about the incident which they've dated as having occurred before 11 June 2013.

They're not clear about before then the incident occurred and indeed it could have been many years earlier (it seems like they had a major architecture change then which has allowed them to provide some context around the date).

Keep in mind that we're talking about a time where My Space was running into serious trouble and there were a raft of lay-offs, it's highly conceivable that someone literally walked out the door with the data.

That's not to say it couldn't have been hacked in a more traditional external-actor sort of way, but the timing is coincidental...

It may be that the incident occurred after 2008, but I doubt it was much later as they were still getting registrations and they would have been very heavily Gmail biased by that time.

One possibility that would explain the ginormous volume of data that was taken (the extracted breach file is 33GB) is an insider threat.

When we look at the top 3 email address in the My Space breach by domain, we see an interesting distribution: What's up with Gmail?!

my spaces rudating-46

Free kinky chat lines

There's been no information forthcoming from anyone about when this breach actually occurred and there's no explicit indicators in the data dump either (sometimes there are timestamps on account creation or website activity). The passwords are stored as SHA1 hashes of the first 10 characters of the password converted to lowercase.

What I really needed though was a max date, so a point in time after which people registered yet That last one used a My Space prefix on a personal domain for their email address so was obviously taking care to track which accounts were created where.