LSP Flagging Thread On Wilders

Discussion in 'malware problems & news' started by LoneWolf, Sep 27, 2007.

Thread Status:
Not open for further replies.
  1. LoneWolf

    LoneWolf Registered Member

    Joined:
    Jan 2, 2006
    Posts:
    3,408
    LinkScanner Pro is flagging a thread here at wilders as having an exploit.
    Is anyone else who is using LSP getting the same?
    Now it's only this thread and only the second page of the thread.
    Just started today,i've visited this thread before with no problems.
    A FP from Exploit Prevention Labs perhaps or something else?
    Here is a screenshot of the thread and warning.
     

    Attached Files:

  2. LowWaterMark

    LowWaterMark Administrator

    Joined:
    Aug 10, 2002
    Posts:
    17,874
    Location:
    New England
    That false positive is actually fairly similar to one that avast! was flagging the other day. It's alerting based upon the presence of text that happens to be a code snip example from a script. Of course, text on a forum page isn't a script, so it doesn't execute any more than having a DOS DEL command line in a post here.

    This one is flagging the text in Zombini's post. See an image of the post below. I don't have LSP, but I'd guess it's flagging because of the "ActiveXObject()" line.
     

    Attached Files:

  3. LoneWolf

    LoneWolf Registered Member

    Joined:
    Jan 2, 2006
    Posts:
    3,408
    Thank you LowWaterMark,that explains that.
    Had the FP with Avast the other day also.
    LSP had the post with the text of the exploit blocked so I could not see that.
    Glad Wilders was not hacked. Have seen a lot of that latley with forums.
    Avast forums,Castlecops and I believe a few others.
    Thanks again for clearing that up for me.
    I'll try and contact the LSP people about the FP.
     
  4. rogert30062

    rogert30062 Registered Member

    Joined:
    May 1, 2006
    Posts:
    68
    Location:
    Atlanta
    Hi guys,

    Should be fixed in todays update. Sorry about that. Btw, if anyone is running anything older than LinkScanner 2.6.6, they should upgrade. The older scanning engine is not smart enough to ignore this f.p.

    Cheers

    Roger
     
Thread Status:
Not open for further replies.