17-year-old claims responsibility for Twitter worm
bnonews.com
bnonews.com
The size of the social graph is harder to estimate. Out of a sample of 459,000 "more influential" Twitter users, the average user follows 262 other twitterers. So the information in the social graph is about 30 GB, assuming 64-bit IDs. They potentially store an edges table of the form (user1_id,user2_id) (60GB), and a denormalized list of followers and friends for each user (30GB each). This comes to about 120GB (I revise my earlier number).
Yes, it's a very rough estimation, but it is in the right ballpark.
That is if he was honest in the interview and what he did.
“I am the person who coded the XSS which then acted as a worm when it auto updated a users profile and status, which then infected other users who viewed their profile. I did this out of boredom, to be honest. I usually like to find vulnerabilities within websites and try not to cause too much damage, but start a worm or something to give the developers an insight on the problem and while doing so, promoting myself or my website.”
OH RLY?! Promoting yourself and your website by writing code that, despite his ridiculously naive belief, reflects what MILLIONS OF CONSUMERS COMPLETELY DESPISE in the form of disruptive viri, malware, spam, etc. Absolutely everything a consumer hates, he decided to be a marketing gimmick to attract people to his web site. In case he didn't get the memo, honest twitter-app developers have a difficult enough time convincing users to give them their l/p for value-added services that have no intention of creating disorder. Thanks for making that job easier.
Jesus h...
(1) At least it was only a marketing gimmick. Do you not know how much more damage a worm such as this could do if the author chose to?
(2) You make it sound like it was some well thought out scheme for him to become a millionaire. No, it was something he seems to have launched and it just caught fire and spread like crazy.
For a 17-year old, I would say this is pretty expected behavior.
Edit: Just read that the worm apparently deleted buncha tweets. If that is the case, that is pretty bad and crossing the "funny" line.
Mikeyy explained to BNO News that he created Stalk Daily from “boredom” and because he “needed a way to make money.”
Sounds to me like premeditated criminal intent.
Developing twitter apps should be an unsure market as it is new to the masses and extensive security testing should be done. I don't condone people breaking into websites or messing around with exploits but it happens and the less harm people do the better.
Outages, security issues, multiple times a day the page renders in different unusable ways. The only real reason they get a free pass is the site is mostly an entertainment product and has marginal usefulness.
I use the site to communicate but if it doesn't work I just go to Google trends to see what is happening or just ask people via skype whats going on.
Through looking at the code behind Twitter, Mikeyy was able to produce a similar site to Twitter with some additional features. “I used my past knowledge to gain an insight on how Twitter worked and outputted to a user. Although both of the sites are coded in different languages I was able to give my site the same features as Twitter, while coding some of my own.”
don't make any sense to me. It sounds like I'm either not understanding something or that it's not a very coherent sentence.
"For everyone wondering, I did NOT promote and/or was involved with the spamming ON Twitter. All bad things you are hearing about this site is not true. Please reconsider as I am not the person who did this…StalkDaily is a website that follows the same functions as Twitter, except more advanced How? Well, instead of just adding an “update status”, people can add pictures and videos. Then you can stalk them, so when they upload a video or picture, or comment someone, you’ll know!"
http://www.techcrunch.com/2009/04/11/twitter-hit-by-stalkdai...
Pretty lame, if you ask me.
I suppose I could visit with lynx/curl/etc., if my curiosity were strong enough.
But either of those strategies are a lot of trouble for very little payoff.
CSRF attacks, on the other hand, are typically launched from a 3rd party site.