• Resolved David Okoli

    (@enochdavid)


    Hello, my wordfence suddenly stopped scanning.
    1.The last action I can remember was blocking all access to wp-includes and wp-config.php files respectively using a functions.php rule.
    OR
    what could be the possible causes?
    2. I see some “YARA” file stuff when I scan with clamav. I hear it’s a false +ve is this true?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi @enochdavid,

    If you remove the changes you made to functions.php does Wordfence work again? Can you show me the changes you made to functions.php (let me know the line number and what was changes).

    There might be other changes that might affect scanning such as changing the maximum execution time, disabling cURL, or installing other plugins that can conflict with Wordfence.

    As for scanning with ClamAV using YARA rules, can you provide what exactly ClamAV found? What rule did it trigger?

    Dave

    Thread Starter David Okoli

    (@enochdavid)

    Here is what the clamav scanner reported – Do I need to be worried as regards the latest clamav report

    File Virus
    tmp/analog/ssl/kikicoin.pw/cache YARA.r57shell_php_php.UNOFFICIAL
    tmp/awstats/ssl/awstats102018.kikicoin.pw.txt YARA.r57shell_php_php.UNOFFICIAL

    I am sorry for the part of functions.php. The rules are actually .htaccess rules(my bad and so sorry). Here are my lastest changes to .htaccess:

    # Blocks all wp-includes folders and files
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^wp-admin/includes/ – [F,L]
    RewriteRule !^wp-includes/ – [S=3]
    RewriteRule ^wp-includes/[^/]+\.php$ – [F,L]
    RewriteRule ^wp-includes/js/tinymce/langs/.+\.php – [F,L]
    RewriteRule ^wp-includes/theme-compat/ – [F,L]
    </IfModule>

    # Restricts access to PHP files from plugin and theme directories
    RewriteCond %{REQUEST_URI} !^/wp-content/plugins/file/to/exclude\.php
    RewriteCond %{REQUEST_URI} !^/wp-content/plugins/directory/to/exclude/
    RewriteRule wp-content/plugins/(.*\.php)$ – [R=404,L]
    RewriteCond %{REQUEST_URI} !^/wp-content/themes/file/to/exclude\.php
    RewriteCond %{REQUEST_URI} !^/wp-content/themes/directory/to/exclude/
    RewriteRule wp-content/themes/(.*\.php)$ – [R=404,L]

    <IfModule mod_headers.c>
    # Using DENY will block all iFrames including iFrames on your own website
    # Header set X-Frame-Options DENY
    # Recommended: SAMEORIGIN – iFrames from the same site are allowed – other sites are blocked
    # Block other sites from displaying your website in iFrames
    # Protects against Clickjacking
    Header always append X-Frame-Options SAMEORIGIN
    # Protects against Drive-by Download attacks
    # Protects against MIME/Content/Data sniffing
    Header set X-Content-Type-Options nosniff
    </IfModule>

    # Deny access to wp-config.php file
    <files wp-config.php>
    order allow,deny
    deny from all
    </files>

    The two files that clamAV scanned were just temporary text files that can be safely deleted.

    Now onto why Wordfence does not scan anymore, I don’t think any changes within .htaccess should cause an issue.

    Is Wordfence able to scan if you temporary move away the .htaccess file? What error is Wordfence having when the scan fails (maximum time exhausted, or something else)?

    Thread Starter David Okoli

    (@enochdavid)

    uhm, this is weird. I just de-activated wordfence, activated it again and it worked…
    So Sorry dear

    No worries! Come back any time if you have any problems with Wordfence. ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘wordfence not scanning anymore’ is closed to new replies.