Thanks for those error logs. There are tons of error from the slim-seo plugin in there but the only error that related to my plugin is this one at 28-Feb-2023 19:13:27 UTC:
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted
This suggests that the php.ini file on your server has a memory_limit set to 256M and the Quarantine probably need a more memory than that in order to display and rescan each of the files listed in the quarantine.
There is a chance that this error was unrelated to Quarantine at all if it happened at a completely different time, though that is the only error triggered by me plugin. The could be an error from another conflicting plugin that is preventing the quarantine form loading but it would not name my plugin in the log file so the only way to find that is to correlate the timestamps in the log files with the exact times that you tried to render the Quarantine page.
Or you could turn on debugging by adding these lines to your wp-config.php file:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
define( 'WP_DISABLE_FATAL_ERROR_HANDLER', true );
As for the other issue, with the external scripts that are infected, you can’t do anything about the script itself if it is hosted on another domain which you do not have access to, but you can remove all references to that external script form your site and my plugin should do that for you. And form the 73 items in your Quarantine it sounds like my plugin has already removed a lot of these for you. If these infections are coming back though, you might still have a vulnerability on your site that is being exploited to inject these external references, and that will need to be found and patched. Fist try deactivating and deleting any themes and plugin that you don’t need. If the injections still return after that, then you will need to compare the times of these infections with the activity recorded in your raw access_log files to determine what vulnerable URLs are responsible for this injection and try to link those URLs back to the insecure code that is allowing this exploit.