- Joined
- Jul 24, 2008
- Messages
- 33,627
- Points
- 0
[h=1]CHROME AND FIREFOX FLAG bit.Iy LINKS AS MALWARE[/h]
<!-- /.block --> <style>.node-article .field-name-link-line-above-tags{float: right;}.node-article .field-name-ad-box-in-article {float: left;margin: 15px 15px 10px 0;}.node-article .field-tags{clear: both;}</style> Post date:
25 Oct 2014 - 9:00pm
<iframe src="http://tpc.googlesyndication.com/safeframe/1-0-0/html/container.html" style="display: none; visibility: hidden;"></iframe><ins id="aswift_0_expand" style="margin: 0px; padding: 0px; border: currentColor; width: 336px; height: 280px; display: inline-table; visibility: visible; position: relative; background-color: transparent; border-image: none;"><ins id="aswift_0_anchor" style="margin: 0px; padding: 0px; border: currentColor; width: 336px; height: 280px; display: block; visibility: visible; position: relative; background-color: transparent; border-image: none;"><iframe name="aswift_0" width="336" height="280" id="aswift_0" frameBorder="0" marginWidth="0" marginHeight="0" scrolling="no" vspace="0" hspace="0" allowfullscreen="true" style="left: 0px; top: 0px; position: absolute;" allowTransparency="true"></iframe></ins></ins>
Having issues accessing bit.Iy links? You’re not alone. It seems many internet users are being greeted with this following message when accessing links that emanate from the popular link-shortening service.
While bit.Iy links are working fine on Safari and Internet Explorer, the problem was initially limited to Mozilla’s Firefox and Google Chrome, though Firefox now seems to be working fine for us.
Google itself states:
<ins id="aswift_1_expand" style="margin: 0px; padding: 0px; border: currentColor; width: 336px; height: 280px; display: inline-table; visibility: visible; position: relative; background-color: transparent; border-image: none;"><ins id="aswift_1_anchor" style="margin: 0px; padding: 0px; border: currentColor; width: 336px; height: 280px; display: block; visibility: visible; position: relative; background-color: transparent; border-image: none;"><iframe name="aswift_1" width="336" height="280" id="aswift_1" frameBorder="0" marginWidth="0" marginHeight="0" scrolling="no" vspace="0" hspace="0" allowfullscreen="true" style="left: 0px; top: 0px; position: absolute;" allowTransparency="true"></iframe></ins></ins>
There’s no word yet on what’s causing all bit.Iy links to be blocked, however. If it had just been Chrome blocking the bit.Iy links, then one could perhaps assume that there was an over-zealous Google at play. But given that it affected Firefox too for quite a while, this suggests that there could be something a little more malicious going on from bitIy’s side, with a higher-than-usual number of miscreant sites using bit.Iy links to trick internet users.
We’ll update here with more details as and when we receive them
<!-- /.block --> <style>.node-article .field-name-link-line-above-tags{float: right;}.node-article .field-name-ad-box-in-article {float: left;margin: 15px 15px 10px 0;}.node-article .field-tags{clear: both;}</style> Post date:
25 Oct 2014 - 9:00pm
<iframe src="http://tpc.googlesyndication.com/safeframe/1-0-0/html/container.html" style="display: none; visibility: hidden;"></iframe><ins id="aswift_0_expand" style="margin: 0px; padding: 0px; border: currentColor; width: 336px; height: 280px; display: inline-table; visibility: visible; position: relative; background-color: transparent; border-image: none;"><ins id="aswift_0_anchor" style="margin: 0px; padding: 0px; border: currentColor; width: 336px; height: 280px; display: block; visibility: visible; position: relative; background-color: transparent; border-image: none;"><iframe name="aswift_0" width="336" height="280" id="aswift_0" frameBorder="0" marginWidth="0" marginHeight="0" scrolling="no" vspace="0" hspace="0" allowfullscreen="true" style="left: 0px; top: 0px; position: absolute;" allowTransparency="true"></iframe></ins></ins>
Having issues accessing bit.Iy links? You’re not alone. It seems many internet users are being greeted with this following message when accessing links that emanate from the popular link-shortening service.
While bit.Iy links are working fine on Safari and Internet Explorer, the problem was initially limited to Mozilla’s Firefox and Google Chrome, though Firefox now seems to be working fine for us.
Google itself states:
“Site [bit.Iy] is listed as suspicious – visiting this web site may harm your computer. Part of this site was listed for suspicious activity 31 time(s) over the past 90 days.”
Google adds that from the 91,854 pages it tested on the site in the past three months, “669 pages resulted in malicious software being downloaded and installed without user consent.” This included 200 trojans, 185 exploits and 152 scripting exploits.
<ins id="aswift_1_expand" style="margin: 0px; padding: 0px; border: currentColor; width: 336px; height: 280px; display: inline-table; visibility: visible; position: relative; background-color: transparent; border-image: none;"><ins id="aswift_1_anchor" style="margin: 0px; padding: 0px; border: currentColor; width: 336px; height: 280px; display: block; visibility: visible; position: relative; background-color: transparent; border-image: none;"><iframe name="aswift_1" width="336" height="280" id="aswift_1" frameBorder="0" marginWidth="0" marginHeight="0" scrolling="no" vspace="0" hspace="0" allowfullscreen="true" style="left: 0px; top: 0px; position: absolute;" allowTransparency="true"></iframe></ins></ins>
There’s no word yet on what’s causing all bit.Iy links to be blocked, however. If it had just been Chrome blocking the bit.Iy links, then one could perhaps assume that there was an over-zealous Google at play. But given that it affected Firefox too for quite a while, this suggests that there could be something a little more malicious going on from bitIy’s side, with a higher-than-usual number of miscreant sites using bit.Iy links to trick internet users.
We’ll update here with more details as and when we receive them
