Antispyware Complaining about TB

[Alkali Ike]

I'm sure this is a false positive (at least I hope so). Trend Micro OfficeScan is displaying the following on the TB forums...

http://www.talkbass.com/forum/attachment.php?attachmentid=207363&stc=1&d=1301958625

Just sharing this in case someone wants to look into it...

 

[David Wilson]

hi,
there's a couple of threads on this subject such as this one: TalkBass PC Threat? - TalkBass Forums

 

[paul]

I'm sure this is a false positive (at least I hope so). Trend Micro OfficeScan is displaying the following on the TB forums...

http://www.talkbass.com/forum/attachment.php?attachmentid=207363&stc=1&d=1301958625

Just sharing this in case someone wants to look into it...

In your specific case, I have some info: Trend Micro recently tagged the shared hosting domain "cdnlayer.com" as malicious, as somebody unrelated was using it to host malicious software. Our client Driving Revenue, was using cdnlayer.com to host their javascript snippet, so that's why you got the warning. I have since updated the code to use DR's own private domain instead of the shared host.

Here's the complete PR from Driving Revenue (Viglink):

Hello,


Yesterday we detected that TrendMicro labeled content hosted on one of the shared hosting domains we use as malicious. The content was unrelated to VigLink, but as a result, sites whose VigLink code references the shared domain are showing a warning when visitors load the page.


Our records indicate that your site's code is referencing the domain in question. At your earliest opportunity, it is critical that you edit your site's VigLink code snippet as follows:

Locate the <script> tag that includes this URL: http://www.talkbass.com/forum/attachment.php?attachmentid=207363&stc=1&d=1301958625...
Replace the entire "http://http.cdnlayer.com/..." URL with this new URL: "http://cdn.viglink.com/api/merged.js"

If you have any doubts about making this change, you can log into drivingrevenue.com if you have not been migrated or viglink.com if you have been migrated and reinstall using the updated code snippet from the JavaScript Codes page ([Invalid or Expired Link Removed] or VigLink - Sign In). Once you have edited or replaced your code snippet, the issue will be fully addressed and will not happen again.


We apologize for the inconvenience this has caused -- while there is no indication that the issue is related to the use of VigLink, we will be avoiding the use of shared hosting domains in the future, in order to prevent a future reoccurrence.


Regards,

Galen

--
Galen Thompson
Relationships Manager / VigLink