Please! Anybody please help me as soon as possible… Fatal Error

The files listed at the Sucuri scan are well known malware and not a part of WordPress. Please read the links.

I think it’s possible that you could have misinterpreted or might have overlooked what you were actually seeing in the scan results. I took a look at the site and at the scan results, and there didn’t appear to be anything in the results that actually indicated that those files were found on the site. In fact, it did not appear as though the scan ever made it past the fatal php error.

I thought Chris summed it up rather well in the last reply…

The links posted above have nothing to do with the site in question. The 404 JavaScript was not found on the site by the scanner. The scanner trys to hit known exploit files and because of the fatal error the warnings were generated. Scan again and you will see that once the PHP fatal error was fixed the scan was clean.

…and I agree with that opinion.

I really didn’t see any evidence in that scan report that would justify jumping right onto the hacker-alarmist bandwagon. I’m not saying it doesn’t happen, because we all know it does. I’m just saying all I saw on the above site and in the scan results was a fatal php error that needed correcting before any real scan could be performed.

It isn’t your intentions I disagree with, it’s just the methodology behind reaching your conclusion so quickly that I was curious about. It’s fun learning new ways to detect problems in files on sites you don’t have any direct access to, and I thought maybe you had a trick that I haven’t used yet.

and I thought maybe you had a trick that I haven’t used yet.

= Experience with issue at hand.

Nobody was being alarmist.

Note the site now does not have warnings and is using the same theme.

As the OP has not returned to explain, the above statement:

Scan again and you will see that once the PHP fatal error was fixed the scan was clean.

is wholly speculative.

The scan noted both a fatal error and files with known bad eval base 64 code it found. I am not sure why that is unclear.

@all: This is getting old! Lets just drop all these debates and help the guy.

@cjlidua: Whats the current situation?

@prionkor

Your concern for @cjlidua’s situation is appreciated, however the issue appears to have already been resolved for quite some time now.

This is just friendly conversation (as far as I’m concerned) surrounding differing opinions regarding the interpretation of the possible cause a fatal php error based on information provided by an online scan tool that many of us frequently use as a point of reference when looking for possible WordPress threats. I’m simply stating that Seacoast Web Design’s immediate declaration of a malware infestation was probably a premature decision base on facts not in evidence and -or- misinterpretation of available information.

The scan noted both a fatal error and files with known bad eval base 64 code it found. I am not sure why that is unclear.

Neither am I, because the scan results I saw did not support that statement, and what you thought you might be seeing has already been plausibly explained. So, the only thing that is really wholly speculative, is the assertion that the issue must be caused by malware.

That’s okay, though, because it’s all part of the learning process for everyone – including me. I’m certainly open to any other non-speculative input that might convince me that I have misunderstood or misinterpreted the same information you were looking at.

Beyond that, it’s just a matter of agreeing to disagree, and then using what we learn to contribute to a more informed decision making process in the future.

Neither am I, because the scan results I saw did not support that statement

You are correct in that the results were dynamic. This is the nature of this malware – delete a file – all is well – next you know it is back.

I suggest we wait for OP to note what was done.

And yes, the community can disagree, even strongly, but we will continue our best to support it.

You are correct in that the results were dynamic. This is the nature of this malware – delete a file – all is well – next you know it is back.

I don’t really feel like shooting myself in the foot here, but if I’m wrong, I’m wrong. Are my thoughts on this actually too far out into left field to support my opinion?

– In this particular case –in the presence of the fatal php error – wouldn’t it be very likely that any positive interpretation of a result for malware is invalid simply because of the tools inability to progress beyond the fatal error? As in, the scanner can’t even complete an analysis because the fatal php error prevents it?

wouldn’t it be very likely that any positive interpretation of a result for malware is invalid simply because of the tools inability to progress beyond the fatal error

I believe the scanner found the well known malware

…And I believe the scanner was incapable of returning those results.

Do you agree with the opinion that the scanner was not actually able to scan the site due to the presence of the fatal php error that resulted in this message being generated by the scan tool itself?

From Securi:
PHP Error: Fatal error
Description: This error happens when a PHP file has a fatal error and is causing the site to crash. It could be related to malware or just a programing error. Either way, it should be fixed because the site is down.