1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Norton blocking surveys from *******

Discussion in 'BlackHat Lounge' started by user08, Nov 10, 2012.

  1. user08

    user08 Newbie

    Joined:
    Mar 30, 2012
    Messages:
    2
    Likes Received:
    0
    Hi, I'm monetizing a facebook app with a content locker from *******.
    Norton antivirus started blocking the content locker that I have on that app. I have other content lockers from ******* on other websites and they are not being blocked by norton.
    Does anybody have any ideas on why norton is blocking the content locker?
    Norton wasn't blocking it before, this just started happening

    here's a screenshot of the alert from norton
    Code:
    img545.imageshack.us /img545/ 342/ fbapp.png
     

    Attached Files:

  2. HoNeYBiRD

    HoNeYBiRD Jr. VIP Jr. VIP

    Joined:
    May 1, 2009
    Messages:
    5,902
    Likes Received:
    7,138
    Gender:
    Male
    Occupation:
    Geographer, Tourism Manager
    Location:
    Ghosted
    it's not blocking the content locker, but the offer in it
    if it bothers you, more than likely you can whitelist the url/add it to the exceptions
    unfortunately it isn't solving the issue for the potential leads who uses Norton too
    it's above you, so you might need to consider to choose another offer
     
  3. user08

    user08 Newbie

    Joined:
    Mar 30, 2012
    Messages:
    2
    Likes Received:
    0
    It's blocking the entire content locker because it doesn't appear when the alert pops up.
    I just realized that another of my content lockers is also being blocked by norton.
    I have 10 content lockers and all of them have the same offers, but only 2 are blocked, so it's not the offer what it's being blocked.
    The first content locker is on a facebook app and the second one is on a normal website, however norton it's taking both content lockers as Facebook Fake surveys.
    I deleted the content locker and created a new one, but that didn't fix the problem.