Forum Replies Created
-
AuthorPosts
-
This threat is already in my definitions, have you downloaded the latest definition updates?
If you still haven’t found it then you can email me directly with your wp-admin login and I’ll figure out where it’s hiding.
A Read/Write Error simply means that my plugin was unable to read (or, when attempting to fix a file, write to) that file, usually because of the file permissions but sometimes it is because of the files size and/or the memory_limit being set too low in your php.ini file. It does not necessarily mean that those file are bad or malicious but it is an indication that there is some kind of issue on your server that needs to be investigated further. I would never suggest anyone delete files on there server just because there was a read/write error, but if you are able to download and open the files and you find the contents to be completely malicious then you can delete them for that reason (remember that some files that contain malicious code may also have code in then that your site need in order to function correctly).
Ok, Well if your PC is clean then maybe it some malware on your site that is trying to redirect you to localhost. In that case then the Norton warning you are getting should stop when we get your site clean
So you cleaned that aurorauniformspr.com site with the newest definitions but it is still blacklisted by Google.
I see from Google’s Safebrowsing Diagnostic page that they updated info about your site today but I cannot see the details of what they found:
Can you add my email address (eli AT gotmls DOT net) to the users in your Google Webmaster Tools account for that site?
Thank you for your donation but it is not necessary to donate in order to clean your site, donations only unlock additional features.
Did you download the latest definition updates?
When you ran the scan, did it find and remove any Known Threats?
after removing the threats you will still need to Request a Review in Google Webmaster Tools to have them take you off the blacklist. Submitting a current and clean XML Sitemap will also help expedite your sites search results returning to normal.
This looks like a warning about a threat on your localhost, are you running a webserver on your PC?
You should scan your local machine for viruses.
This is a JavaScript Error. I don’t see this error on your login page right now so it may have just been a fluke but if it happens again you can check the Error Console in your browser’s Element Inspector to see why the JavaScript is not working on your wp-login.php page.
Under “What to scan:” click on “plugins” and then check the box for “mailchimp-for-wp” in the popup for “Only Scan These Folders:”.
You could try increasing the memory limit to 256M but normally 128M should be enough. Maybe it’s having trouble with those files for some other reason. It is a pretty unusual that it would take 30 minutes just to scan the plugins directory. Your server may just be really under-powered regardless of your php.ini settings.
(I do my best to consider the efficiency of the scan process, however it is always going to be taxing on your server to read and parse every file looking for malicious patterns in the code. As a comparison to your server, it take less than 10 minutes to scan the plugins directory on one of my sites and I have over 60 plugins, with almost 4000 files scanned.)
Good question. The permission look right on those files so I would guess that it has to do with the memory_limit in your php.ini file being set too low for scanning larger files.
February 5, 2016 at 7:39 am in reply to: [SOLVED] Failing or Timing-out? Automatically Fix SELECTED Files Now #1389Good idea, un-checking and then check only a few at a time is another good way to split up the batch site, but I realize that would be easier with options for “Check All” and “Uncheck All”.
Having a stable internet connection is important when you are running long scans because the Complete Scan relies on JavaScript call from your browser to keep the scan going. This is one of the reasons it been so hard for me to create the scheduled scan feature that everyone wants. However, I don’t think your internet connection speed has anything to do with the timeout issue you are having when you try to fix larger batches. That kind of problem really relies more on the speed of the server then the client. Last year I was using a Satellite Internet provider, which was way slower than any DSL connect I had ever used, and those kind of timeout issues completely depended on what server I was running my plugin on. Some server have very little physical memory and are overburdened with site that cause them to run too many processes too slowly. Also there could be settings in your php.ini like memory_limit or max_execution_time which are restricting the abilities of the php code running on your site.
February 4, 2016 at 5:44 pm in reply to: [SOLVED] Failing or Timing-out? Automatically Fix SELECTED Files Now #1385Unfortunately I cannot tell from your screenshots how many Known Threats you have there but I suspect it may be more than your server can handle fixing in one click. I also cannot tell how long it took for the scan to finish producing those results but my first suggestion would be to start the scan again and this time employ the fix-as-you-go method which means you click on the Automatic Fix button as soon as there is anything to fix but you let it keep scanning at the same time. That way it fixes things in smaller batches and by the time the scan is finished the fixing would be not far behind.
P.S. As a point of reference, it shouldn’t take more than 60 seconds for that popup window/frame to produce it results (if it’s going to at all).
Yes, that should work. My plugin will scan all the files under the root directory of any WordPress install, even if the files are not related to WordPress.
You missed the .htaccess file in your public_html directory!
This file still has all that BPS code in it, including the 403 that is blocking my dynamic JavaScript that you want to work. That .htaccess file is on level up ,outside the site’s root directory, so it will actually affect all the site that you have inside your public_html directory (not a good idea, IMHO).There was also an .htaccess file in /wp-content/ for this site which contains this code (which might also cause problems):
<FilesMatch "\.(?i:php)$">
<IfModule !mod_authz_core.c>
Order allow,deny
Deny from all
</IfModule>
<IfModule mod_authz_core.c>
Require all denied
</IfModule>
</FilesMatch>The Quarantine is really just a record of the the malicious code that was removed. Those files are now clean and the prior contents are encoded into your database as a custom post_type. Don’t delete the files that those records refer to because they are clean but you can delete the records from the Quarantine if you want to. Personally, I find the Quarantine to be very useful for later reference, in case the site gets hacked again, you can compare the files and dates of the infection and you can also restore any of those files if the need arises. I suppose the only harm that could come from leaving those records in the quarantine is that an admin could accidentally restore the infected files at a later date.
On another subject, I just wanted to say what a pleasant surprise it was to wake up this morning and find you brilliant review and rebuttal in my behalf on wordpress.org, not to mention that very generous donation you made. Thank you!
“No response from server” means that there is something on your server that is blocking my patch. If you want to send me your wp-admin login then I would be happy to take a look at it an let you know what the problem is.
-
AuthorPosts
