I haven't been able to replicate this problem and I've done an exhaustive search through the entire codebase and database for crackle and have found no results. A quick search on Google for this issue brings up articles like this one:
In short, this is a browser hijacking virus and resides as a trojan on the computer of the person browsing, evidently not on the website itself. There is a solution offered but I can't vouch for it as I haven't needed it.
I'll keep an eye out for things, but so far I haven't been able to find anything on our end that would cause the reported behavior.
Users browsing this forum: No registered users and 0 guests