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.