• Resolved eva2000


    On a local test install i upgraded WP from 3.5.1 to 3.6.1 then installed Sucurit WordPress scanner plugin and the integrity check run returns output for following files ? What does this mean that these files were modified compared to whos’ wordpress hashing database ? Sucuri’s ?

    compared to 3.5.1 or 3.6.1 ?

    Core File Added:1

    Core File Removed: 4

    Core File Modified: 16


Viewing 3 replies - 1 through 3 (of 3 total)
  • I saw exactly the same results immediately after a clean install using Dreamhost’s one-click installer.

    I posted exactly the same question to Sucuri’s support email address and received an answer asking if I was a customer and to login and submit again.

    —-MY Conclusions—-
    1. The question is about a free function, the WordPress Integrity scan in the WordPress plug-in.

    2. If the free version of a product is presenting false results (I suspect these are “false positives”), then what confidence should I have that the fee version of the product is any better?”

    3. Some of us are very reluctant to invest in products that won’t answer simple support questions about free services? That behavior suggests how the fee paying customers might also be subject to overly zealous gate keepers.

    Meanwhile Sucuri corporate is having a party about acquiring another firm and expanding their offerings.

    Another variation.
    I reported seeing these “false positives” after a Dreamhost “one-click” install. Exactly the same as the original post 4 core files removed and 16 core files modified.

    Not being absolutely sure what the Dreamhost installer robot does, I installed a new blog COMPLETELY from scratch, new DB, new WP 3.6.1 files downloaded directly form WP, etc.

    Akismet ant Hello Dolly are “built in,” but not activated, plugins. Immediately after loggin in the first time, I installed the Sucuri bplug-in (level 1.4.7) and ran the WP Integrity Check.

    Once again, EXACTLY the same 4 and 16 files identified. It looks like Sucuri hasn’t updated their hash references for 3.6.1.

    This is NOT a confidence builder. Nor are their support practices.

    Apparently, I’m not alone in worrying about scanners that find a bunch of false positives. (Why should we spend good money and time on false alarms?)

    I found this: “…with a scanner this poor it is unlikely that it will actually do a good job of detecting when website are infected. ”

    Read the whole thing at: http://www.whitefirdesign.com/blog/2012/06/25/false-positives-highlight-deeply-flawed-website-malware-scanners/

    Plugin Author Daniel Cid


    Sucuri.net Support

    It has been fixed. Our integrity database was still set for 3.6, so the changes on 3.6.1 were showing as modified.


Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Integrity check 3.5.1 to 3.6.1’ is closed to new replies.