<span id="hs_cos_wrapper_post_body" class="hs_cos_wrapper hs_cos_wrapper_meta_field hs_cos_wrapper_type_rich_text" style="" data-hs-cos-general-type="meta_field" data-hs-cos-type="rich_text" ><p>At ThreatSTOP we have been reading about the <a href="http://arstechnica.com/security/2015/02/lenovo-pcs-ship-with-man-in-the-middle-adware-that-breaks-https-connections/">Lenovo/Superfish</a>&nbsp;adware security hole with amazement. Not so much at the enormous gaping hole that has been discovered (sadly that seems to be SOP at too many places) but at the way that the various parties involved have <a href="https://arstechnica.com/security/2015/02/superfish-doubles-down-says-https-busting-adware-poses-no-security-risk/">completely failed to understand</a> that they have created such an enormous gaping hole.</p> <!--more--><p>Given that the creators of the hole seem to be unclear on why they have caused a problem we now believe that it is worth blocking all connections to superfish.com and its associated adware domains (e.g.&nbsp;best-deals-products.com ). The following IP addresses have been added to our system in the TSCriticalG feed that is present in most user policies either directly or because it is included in the BASIC policy:</p> <ul> <li style="padding-left:30px;">66.70.34.101</li> <li style="padding-left:30px;">66.70.34.103</li> <li style="padding-left:30px;">66.70.34.105</li> <li style="padding-left:30px;">66.70.34.113</li> <li style="padding-left:30px;">66.70.34.115</li> <li style="padding-left:30px;">66.70.34.117</li> <li style="padding-left:30px;">66.70.34.119</li> <li style="padding-left:30px;">66.70.34.125</li> <li style="padding-left:30px;">66.70.34.127</li> <li style="padding-left:30px;">66.70.34.129</li> <li style="padding-left:30px;">66.70.34.251</li> </ul> <p>This will <strong>not stop</strong> the gaping hole (which<a href="https://blog.filippo.io/komodia-superfish-ssl-validation-is-broken/"> seems to get ever more gaping</a> as people look at it more deeply), but it should help our customers determine which computers in their network are vulnerable because they will be the ones with dozens of connections to these IP addresses. Once these devices have been identified it is critical to both <a href="http://www.popularmechanics.com/technology/security/a14194/how-do-i-delete-superfish-lenovo/">uninstall the software and verify that the offending root certificate(s) is&nbsp;removed</a>&nbsp;from them.</p></span>