DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

Cloaked Keywords Hack

 3 Replies
 1 Subscribed to this topic
 15 Subscribed to this forum
Sort:
Author
Messages
Advanced Member
Posts: 224
Advanced Member

    Hi everybody,

    I'm curently dealing with a problem at Google Search Console about "Cloaked Keywords Hack" for one of my clients website.

    I'm not sure how to approach this and I'm looking for possible solutions. This is the current situation:

    1. I already check the files and folders for the website and there is no physical files recently change.
    2. I checked the pages structure within DNN and there is no pages others than the one I created.
    3. The website doesn't use HTTPS but some of the URL's show https like this one "https://agronegocioscr.com/the-lost-oawwdn/einstein-the-mad-scientist-genius-full-movie-565f1c"
    4. The Website is currently at 8.0.0 and I know I need to upgrade the DNN version to the latest but currently I've a conflict with the theme we're using and if I run the update the theme will have compatibility problems until we change the skin for a different one.
    5. The list of links are available at Google Search by using the query site:agronegocioscr.com (the fake results starts at page 2)

    The screenshot available here: https://we.tl/t-SGMIUoYdWu (link expires in 7 days)

    Thanks in advance.

    Veteran Member
    Posts: 543
    Veteran Member
      Marco,
      please check again, whether there are added subfolders and files in the root of your IIS website hosting DNN or redirect rules in web.config - but I suppose, it's the first - maybe even hidden in file system and NOT displayed in DNN File Manager.
      The page doesn't seem to be served by DNN, just plain html served by IIS - that might be the reason for https being used.
      Advanced Member
      Posts: 224
      Advanced Member
        Just as heads up...

        On this case, I don't have the domain DNS servers pointing at me so I wasn't able to manage the domain itself. We figure this out by talking to the client and finding out that he kept the old website version he had before ours and somebody hacked that website, the client didn't update the domain to point www and non www to our IP address and we received all these hacked content error messages because of this.

        At the end, the client cancelled the other hosting and update the domain to have www and non www pointing at the same IP address.
        Veteran Member
        Posts: 1143
        Veteran Member

          Thank you for reporting back :-)

          These Forums are dedicated to the discussion of DNN Platform.

          For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

          1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
          2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
          3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
          4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
          5. No Flaming or Trolling.
          6. No Profanity, Racism, or Prejudice.
          7. Site Moderators have the final word on approving / removing a thread or post or comment.
          8. English language posting only, please.

          Would you like to help us?

          Awesome! Simply post in the forums using the link below and we'll get you started.

          Get Involved