{"id":6963,"date":"2014-05-17T09:19:17","date_gmt":"2014-05-17T16:19:17","guid":{"rendered":"http:\/\/www.infosecurity.pro\/?p=6963"},"modified":"2019-04-20T16:24:35","modified_gmt":"2019-04-20T16:24:35","slug":"bitly-exploited","status":"publish","type":"post","link":"https:\/\/www.infosecurity.pro\/?p=6963","title":{"rendered":"Bitly exploited"},"content":{"rendered":"<p>\t\t\t\t<![CDATA[Bitly is a web service which is famous for the shortening of website URLs. A US-based company, headquartered in New York City, Bitly curtails more than one billion links each month for use in casual correspondence, SMS, and email. \u00a0\u00a0It has been a very popular service since 2009 for Twitter since Twitter won't allow more than 140 characters in a single tweet message. \u00a0\u00a0Bitly also provides the utility to see the statistics related to links shortened by the users.<img decoding=\"async\" style=\"width: 264px; height: 120px; float: left;\" src=\"http:\/\/upload.wikimedia.org\/wikipedia\/commons\/4\/46\/Bit.ly_Logo.png\" alt=\"bitly logo\" \/>\nWhen a link is shortened using the Bitly service, it uses the HTTP 301 redirect \u00a0for the link so the change is permanent and cannot be changed back.\u00a0 It uses the domain bit.ly for any shortened URLs. \u00a0It offers paid enterprise solutions called Bitly Enterprise so companies may generate their custom domain for an advanced branding feature.\nSecurity breaches on social websites and on the world wide web have increased radically recently. People tend to store more of their personal and business information on the internet.\nRecently on May 11<sup>th<\/sup>, Chief Executive Mark Josephson of Bitly wrote in their blog that their account credentials had been compromised and that they had seen accesses without proper authentication.\u00a0 It was stated that they have taken enough necessary safety precautions to guard accounts.\u00a0 He also stated that they have cancelled the links between Facebook and Twitter accounts so users would need to reconnect with them at their next login. The company is assuring their clients that their service is still secure and all the necessary precautionary measures are taken to ensure the security of accounts. \u00a0\u00a0The company emphasizes that they take this matter seriously because they want their customers to feel secure and trust them. They apologize for any inconvenience and will update their Twitter feeds if they have something additional to convey.\nThe security of the web comes up on the heels of a highlighted issue with the impacts of the heartbleed bug\u2019s misuse in world wide web security.\u00a0 Heartbleed left sensitive data and millions of passwords open to hackers. \u00a0A UK based website was the first to mention that security had been compromised due to the Heartbleed bug which is described as \u201ccatastrophic\u201d because it led to insurmountable amounts of organizations and people who had to install security patches to remove the flaw.\nAfter seeing this incident, Twitter has also increased their protection by adding two more features to improve login protection.\u00a0 Users will have to reset information sent to their mail account or phone number depending on the type of link done through the website. Twitter will start to monitor the login details to ensure the safety of users by saving the device used for logging and the location of the session with date and time.\n<span id=\"docs-internal-guid-9c6b3c28-0ac5-7c80-da95-e873b23f2705\" style=\"color: #000000; font-family: Arial; font-size: 15px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; background-color: transparent;\"><\/span>]]>\t\t<\/p>\n","protected":false},"excerpt":{"rendered":"<p>\t\t\t\t<![CDATA[]]>\t\t<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"amazonpipp_noncename":"","amazon-product-isactive":"","amazon-product-single-asin":"","amazon-product-content-location":"","amazon-product-content-hook-override":"3","amazon-product-excerpt-hook-override":"3","amazon-product-singular-only":"","amazon-product-amazon-desc":"","amazon-product-show-gallery":"","amazon-product-show-features":"","amazon-product-newwindow":"2","amazon-product-show-list-price":"","amazon-product-show-used-price":"","amazon-product-show-saved-amt":"","amazon-product-timestamp":"","amazon-product-new-title":"","amazon-product-use-cartURL":"","amazon_featured_post_meta_key":"","_amazon_featured_alt":"","amazon-product-template":"","footnotes":""},"categories":[66,67],"tags":[],"class_list":["post-6963","post","type-post","status-publish","format-standard","hentry","category-breaches","category-practices"],"_links":{"self":[{"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts\/6963","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=6963"}],"version-history":[{"count":1,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts\/6963\/revisions"}],"predecessor-version":[{"id":7946,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=\/wp\/v2\/posts\/6963\/revisions\/7946"}],"wp:attachment":[{"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6963"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=6963"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infosecurity.pro\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=6963"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}