{"id":3945,"date":"2014-04-14T14:12:14","date_gmt":"2014-04-14T18:12:14","guid":{"rendered":"http:\/\/acro.net\/blog\/?p=3945"},"modified":"2014-04-14T14:31:47","modified_gmt":"2014-04-14T18:31:47","slug":"what-is-at-stake-after-the-sedo-intrusion-incident","status":"publish","type":"post","link":"https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/","title":{"rendered":"What is at stake after the Sedo intrusion incident"},"content":{"rendered":"<p>On Saturday, I reported <a title=\"Did Sedo mass-email old accounts due to a glitch?\" href=\"http:\/\/acro.net\/blog\/domains\/sedo-mass-email-old-accounts-due-glitch\/\" target=\"_blank\"><strong>a potential glitch at Sedo<\/strong><\/a> that might have generated emails sent to existing users, asking them to confirm their accounts.<\/p>\n<p>Today, Sedo announced in an email, that the welcome email was the result of an intruder to the Sedo web site.<\/p>\n<p>The notification email from Sedo reads in part:<\/p>\n<blockquote><p><em>We wish to inform you that on Saturday, 12th April, the Sedo website was compromised by an unknown intruder through a previously unknown security loophole. This resulted in an unauthorized email with the subject \u201cConfirm your Sedo Account&#8221; being sent to a small number of our customers.<\/em><\/p>\n<p><em>Our immediate investigation into the matter has shown that your email address was unfortunately one of those affected. That means that the intruder has got your email address only. <strong>NO other data has been compromised, i.e. no passwords or other account information was obtained.<\/strong> The security vulnerability was closed as soon as it was detected and any further unauthorized access was successfully prevented. This means that your Sedo account is safe, and you do not need to take any action to safeguard data stored in your account. Clicking on the link in the unauthorized email has no adverse effects.<\/em><\/p><\/blockquote>\n<p>Most likely, the intruder gained access to the Sedo web site, potentially as a user with elevated privileges. That gave them access to a set of tools that included the ability to initiate a &#8220;Welcome to Sedo&#8221; email, which they edited accordingly.<\/p>\n<p>When one signs up for a new Sedo account, a confirmation email with the subject &#8220;Welcome to Sedo!&#8221; is sent out, as seen below:<\/p>\n<blockquote><p>Dear Mr. [firstname],<br \/>\nThank you for registering with Sedo!<\/p>\n<p>Please activate your free registration by clicking on this link:<br \/>\nhttp:\/\/www.sedo.com\/confirm_account.php?challenge=[redacted]&#038;language=e<br \/>\n(If clicking the link does not work, please try copying and pasting the entire link into a new browser window.)<\/p>\n<p>Please note that before you can sell, buy or park domain names you need to complete Sedo&#8217;s free Member Certification process.<br \/>\nAfter you have activated your account you will automatically be redirected to Sedo&#8217;s Member Certification process.<br \/>\nhttp:\/\/www.sedo.com\/member\/membercert\/index.php<\/p>\n<p>Here&#8217;s a quick tip to get you started: What&#8217;s the number one thing you can do to improve your chances of selling a domain name?<br \/>\nDomain Parking! Sedo&#8217;s Domain Parking is the secret that lets the pros consistently sell more domains at higher prices than marketplace listings alone.<br \/>\nEven better, it&#8217;s FREE and takes only a few minutes to setup.<\/p>\n<p>Learn how you can start earning more money with your domain names by following the link below:<br \/>\nhttp:\/\/www.sedo.com\/services\/parking.php3<\/p>\n<p>For more tips on promoting your domain sale, please visit:<br \/>\nhttp:\/\/www.sedo.com\/uk\/sell-domains\/overview\/?tracked=&#038;partnerid=&#038;language=us<\/p>\n<p>At Sedo, we strive to provide the best customer support in the domain industry.<\/p>\n<p>Once your account is activated, we will send you a welcome email with some helpful tips and information to get you started.<\/p>\n<p>If you have any questions, comments, or feedback, please do not hesitate to contact us at contact@sedo.com.<\/p>\n<p>Once again, welcome to Sedo!<br \/>\nBest Regards,<\/p>\n<p>Your Sedo Team<\/p>\n<p>________________________________________________<\/p>\n<p>Sedo.com :: 161 First Street :: Cambridge, MA 02142<br \/>\ntel 617-499-7200 :: fax 617-499-7219<br \/>\nhttp:\/\/www.sedo.com :: http:\/\/support.sedo.com<\/p>\n<p>________________________:: make a name for yourself.<\/p>\n<p>Confidentiality Statement:<br \/>\nThis e-mail, including attachments, may include confidential and\/or proprietary<br \/>\ninformation, and may be used only by the person or entity to which it is addressed. If the<br \/>\nreader of this e-mail is not the intended recipient or his or her authorized agent, the<br \/>\nreader is hereby notified that any dissemination, distribution or copying of this e-mail is<br \/>\nprohibited. If you have received this e-mail in error, please notify the sender by replying<br \/>\nthis message and delete this e-mail immediately.<\/p><\/blockquote>\n<p>As one can see, the real email differs a lot from the one sent on Saturday, which proves that <strong>the intruder customized the email<\/strong> that was sent out.<\/p>\n<p>It must be noted that both the intruder&#8217;s emails and the valid Sedo email are sent from the same third party mailer, as mentioned in <a href=\"http:\/\/acro.net\/blog\/domains\/sedo-mass-email-old-accounts-due-glitch\/\" target=\"_blank\"><strong>my previous post<\/strong><\/a>. Both emails share the same originating network and neighboring IP addresses.<\/p>\n<p>In other words, the vulnerability that was exploited in order to mass-mail existing accounts, was <strong>most likely limited<\/strong> to the following:<\/p>\n<ul>\n<li>Access to an administrative tool at Sedo.<\/li>\n<li>Compilation of a custom email.<\/li>\n<li>Mass dispatching of email to existing accounts or a portion thereof.<\/li>\n<\/ul>\n<p>The intruder could have done <strong>considerably larger damage<\/strong>, by including a phishing link into the custom email they compiled.<\/p>\n<p>It is very possible, that the intruder wanted to raise awareness to an existing security hole by causing some minimal damage while getting attention for it. They could have also failed at maximizing the impact of their attempt to access user accounts.<\/p>\n<p>At this time, there is no indication that any account info was compromised; while the <strong>hashed links<\/strong> sent in the Saturday email log users into their accounts, the links appear to have been dispatched <strong>individually<\/strong> to every user.<\/p>\n<p>This glitch points the finger &#8211; <em>potentially<\/em> &#8211; at the third party being used for the generation of emails, as well.<\/p>\n<p>It is a good idea, however, to <strong>change your Sedo password<\/strong>. In my opinion, the damage done is more or less limited to hurting Sedo&#8217;s reputation.<\/p>\n<p>Regardless of what type of vulnerability patching Sedo performed since the incident, <strong>they must also alter the code<\/strong> that generates and authenticates the hashed links, as the existing links &#8211; <em>when shared<\/em> &#8211; do log one into an active Sedo account.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>On Saturday, I reported a potential glitch at Sedo that might have generated emails sent to existing users, asking them to confirm their accounts. Today, Sedo announced in an email, that the welcome email was the result of an intruder to the Sedo web site. The notification email from Sedo reads in part: We wish [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[1045,1046],"class_list":["post-3945","post","type-post","status-publish","format-standard","hentry","category-domains","tag-sedo-intruder","tag-was-sedo-hacked","entry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.3 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>What is at stake after the Sedo intrusion incident - Acro.net - A Domain Investing Blog by Theo Develegas<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"What is at stake after the Sedo intrusion incident - Acro.net - A Domain Investing Blog by Theo Develegas\" \/>\n<meta property=\"og:description\" content=\"On Saturday, I reported a potential glitch at Sedo that might have generated emails sent to existing users, asking them to confirm their accounts. Today, Sedo announced in an email, that the welcome email was the result of an intruder to the Sedo web site. The notification email from Sedo reads in part: We wish [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/\" \/>\n<meta property=\"og:site_name\" content=\"Acro.net - A Domain Investing Blog by Theo Develegas\" \/>\n<meta property=\"article:published_time\" content=\"2014-04-14T18:12:14+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2014-04-14T18:31:47+00:00\" \/>\n<meta name=\"author\" content=\"Theo Develegas\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Theo Develegas\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/acro.net\\\/blog\\\/what-is-at-stake-after-the-sedo-intrusion-incident\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/acro.net\\\/blog\\\/what-is-at-stake-after-the-sedo-intrusion-incident\\\/\"},\"author\":{\"name\":\"Theo Develegas\",\"@id\":\"https:\\\/\\\/acro.net\\\/blog\\\/#\\\/schema\\\/person\\\/9c9625f061a0e603a87f5bf0f6f781fe\"},\"headline\":\"What is at stake after the Sedo intrusion incident\",\"datePublished\":\"2014-04-14T18:12:14+00:00\",\"dateModified\":\"2014-04-14T18:31:47+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/acro.net\\\/blog\\\/what-is-at-stake-after-the-sedo-intrusion-incident\\\/\"},\"wordCount\":956,\"commentCount\":2,\"keywords\":[\"Sedo intruder\",\"was Sedo hacked\"],\"articleSection\":[\"Domains\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/acro.net\\\/blog\\\/what-is-at-stake-after-the-sedo-intrusion-incident\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/acro.net\\\/blog\\\/what-is-at-stake-after-the-sedo-intrusion-incident\\\/\",\"url\":\"https:\\\/\\\/acro.net\\\/blog\\\/what-is-at-stake-after-the-sedo-intrusion-incident\\\/\",\"name\":\"What is at stake after the Sedo intrusion incident - Acro.net - A Domain Investing Blog by Theo Develegas\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/acro.net\\\/blog\\\/#website\"},\"datePublished\":\"2014-04-14T18:12:14+00:00\",\"dateModified\":\"2014-04-14T18:31:47+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/acro.net\\\/blog\\\/#\\\/schema\\\/person\\\/9c9625f061a0e603a87f5bf0f6f781fe\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/acro.net\\\/blog\\\/what-is-at-stake-after-the-sedo-intrusion-incident\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/acro.net\\\/blog\\\/what-is-at-stake-after-the-sedo-intrusion-incident\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/acro.net\\\/blog\\\/what-is-at-stake-after-the-sedo-intrusion-incident\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/acro.net\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"What is at stake after the Sedo intrusion incident\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/acro.net\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/acro.net\\\/blog\\\/\",\"name\":\"Acro.net - A Domain Investing Blog by Theo Develegas\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/acro.net\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/acro.net\\\/blog\\\/#\\\/schema\\\/person\\\/9c9625f061a0e603a87f5bf0f6f781fe\",\"name\":\"Theo Develegas\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6794630c371bee89f2b833c1f4b777d9ba75767b217c8fce2cfd6e6d7d90960d?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6794630c371bee89f2b833c1f4b777d9ba75767b217c8fce2cfd6e6d7d90960d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6794630c371bee89f2b833c1f4b777d9ba75767b217c8fce2cfd6e6d7d90960d?s=96&d=mm&r=g\",\"caption\":\"Theo Develegas\"},\"description\":\"Theo Develegas - News and opinions on domain name investing, brand development, design, and the occasional rant or two about life's challenges. Founder of Acroplex LLC.\",\"sameAs\":[\"https:\\\/\\\/acro.net\",\"https:\\\/\\\/x.com\\\/acroplex\"],\"url\":\"https:\\\/\\\/acro.net\\\/blog\\\/author\\\/admin\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"What is at stake after the Sedo intrusion incident - Acro.net - A Domain Investing Blog by Theo Develegas","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/","og_locale":"en_US","og_type":"article","og_title":"What is at stake after the Sedo intrusion incident - Acro.net - A Domain Investing Blog by Theo Develegas","og_description":"On Saturday, I reported a potential glitch at Sedo that might have generated emails sent to existing users, asking them to confirm their accounts. Today, Sedo announced in an email, that the welcome email was the result of an intruder to the Sedo web site. The notification email from Sedo reads in part: We wish [&hellip;]","og_url":"https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/","og_site_name":"Acro.net - A Domain Investing Blog by Theo Develegas","article_published_time":"2014-04-14T18:12:14+00:00","article_modified_time":"2014-04-14T18:31:47+00:00","author":"Theo Develegas","twitter_misc":{"Written by":"Theo Develegas","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/#article","isPartOf":{"@id":"https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/"},"author":{"name":"Theo Develegas","@id":"https:\/\/acro.net\/blog\/#\/schema\/person\/9c9625f061a0e603a87f5bf0f6f781fe"},"headline":"What is at stake after the Sedo intrusion incident","datePublished":"2014-04-14T18:12:14+00:00","dateModified":"2014-04-14T18:31:47+00:00","mainEntityOfPage":{"@id":"https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/"},"wordCount":956,"commentCount":2,"keywords":["Sedo intruder","was Sedo hacked"],"articleSection":["Domains"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/","url":"https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/","name":"What is at stake after the Sedo intrusion incident - Acro.net - A Domain Investing Blog by Theo Develegas","isPartOf":{"@id":"https:\/\/acro.net\/blog\/#website"},"datePublished":"2014-04-14T18:12:14+00:00","dateModified":"2014-04-14T18:31:47+00:00","author":{"@id":"https:\/\/acro.net\/blog\/#\/schema\/person\/9c9625f061a0e603a87f5bf0f6f781fe"},"breadcrumb":{"@id":"https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/acro.net\/blog\/what-is-at-stake-after-the-sedo-intrusion-incident\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/acro.net\/blog\/"},{"@type":"ListItem","position":2,"name":"What is at stake after the Sedo intrusion incident"}]},{"@type":"WebSite","@id":"https:\/\/acro.net\/blog\/#website","url":"https:\/\/acro.net\/blog\/","name":"Acro.net - A Domain Investing Blog by Theo Develegas","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/acro.net\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/acro.net\/blog\/#\/schema\/person\/9c9625f061a0e603a87f5bf0f6f781fe","name":"Theo Develegas","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/6794630c371bee89f2b833c1f4b777d9ba75767b217c8fce2cfd6e6d7d90960d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/6794630c371bee89f2b833c1f4b777d9ba75767b217c8fce2cfd6e6d7d90960d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/6794630c371bee89f2b833c1f4b777d9ba75767b217c8fce2cfd6e6d7d90960d?s=96&d=mm&r=g","caption":"Theo Develegas"},"description":"Theo Develegas - News and opinions on domain name investing, brand development, design, and the occasional rant or two about life's challenges. Founder of Acroplex LLC.","sameAs":["https:\/\/acro.net","https:\/\/x.com\/acroplex"],"url":"https:\/\/acro.net\/blog\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/acro.net\/blog\/wp-json\/wp\/v2\/posts\/3945","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/acro.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/acro.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/acro.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/acro.net\/blog\/wp-json\/wp\/v2\/comments?post=3945"}],"version-history":[{"count":0,"href":"https:\/\/acro.net\/blog\/wp-json\/wp\/v2\/posts\/3945\/revisions"}],"wp:attachment":[{"href":"https:\/\/acro.net\/blog\/wp-json\/wp\/v2\/media?parent=3945"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/acro.net\/blog\/wp-json\/wp\/v2\/categories?post=3945"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/acro.net\/blog\/wp-json\/wp\/v2\/tags?post=3945"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}