It was business as usual when blogger Igor Kromin noticed he was having issues with his site's admin interface. He took a look under the hood and did a little digging around.
After going over his site with a fine tooth comb he noticed something out of the ordinary, something he didn't recall seeing before, something that would let him know someone or something had been there.
This is what he found:
After going over his site with a fine tooth comb he noticed something out of the ordinary, something he didn't recall seeing before, something that would let him know someone or something had been there.
This is what he found:
<script>'undefined'=== typeof _trfq || (window._trfq = []);'undefined'=== typeof _trfd && (window._trfd=[]),_trfd.push({'tccl.baseHost':'secureserver.net'}),_trfd.push({'ap':'cpsh'},{'server':'xxxxxxxx0000'}) // Monitoring performance to make your website faster. If you want to opt-out, please contact web hosting support.</script><script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>A tiny bit of mysterious Javascript he didn't recognize. If he didn't place the code in his pages who did? Was it some hacker in a dimly lit room seeking to wreak havoc on his site? Nope. The culprit was actually his web hosting service -- GoDaddy. You're probably wondering (like I did) why would a web hosting service covertly inject JavaScript into their client's web pages?
