Support » Plugin: Wordfence Security - Firewall & Malware Scan » WordFence scan: Unknown File

  • Resolved murielzs


    Hi, how do I get the full list of the 103 file detected as issues by WordFence scan?

    The scan names only 1 file out of the 103 files.

    Then I can show them to my host Siteground to see if they are malicious or not.

    Thank you

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author WFSupport


    What is the file name that is listed?


    Filename: wp-admin/css/colors/coffee/php.ini (+104 more)
    File Type: Core

    Details: This file is in a WordPress core location but is not distributed with this version of WordPress. This scan often includes files left over from a previous WordPress version, but it may also find files added by another plugin, files added by your host, or malicious files added by an attacker. 104 more similar files were found.

    Plugin Author WFSupport


    Thanks for supplying that information. Sometimes the auto update scripts on hosts that update WordPress will write those files into multiple directories to ensure that the update completes. The file, php.ini, is a configuration file and is usually removed after the update but occasionally will stick around. You can remove any of them except the one in the directory WordPress is installed in. So if you wanted to just remove them by clicking the delete file in the scan results you should be good to do that. Or Siteground can remove them for you.


    OK, thank you, that’s great to hear.

    But where do I find the whole list of the 104 files??? Wordfence gives only the name of 1 file. I need the whole list to have these deleted in one go. It’d take for ever to do it through WordFence single notifications.

    Many thanks,


    I have the same issue… loads of files (139) but only lists one, and you can only delete one at a time, then you have to run a scan AGAIN… Ridiculous!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.