The files with '.$$$' are temporary files; the reason scanners have problems with them is that they are incomplete files which are usually renamed and moved once the file has been fully written to disk.
As such, if it is in the tmp folder and has the extension .$$$, it is almost guaranteed to be a "corrupt file". Sophos logs these but does not crash on them or bring up needless alerts.
However, it *is* possible that the issues some people have been having with "calculating..." taking too long have to do with these files swapping in and out of the temp folder. To test this, you can try excluding /private/tmp *temporarily* from scans to see if this fixes your issue.
I say temporarily, because tmp is a common staging ground for both legitimate and malicious software, and if something is caught while still in this folder (which is readable and writeable by everyone), it will likely never get as far as doing anything actually malicious on the system it is attacking.
That said, could someone with .$$$ files logged please use either the free app Sloth, or the terminal command:
lsof |grep \.\$\$\$$
and post the results? This should tell us what application, running process etc. is involved in creating these specific temp files.
The files with '.$$$' are temporary files; the reason scanners have problems with them is that they are incomplete files which are usually renamed and moved once the file has been fully written to disk.
As such, if it is in the tmp folder and has the extension .$$$, it is almost guaranteed to be a "corrupt file". Sophos logs these but does not crash on them or bring up needless alerts.
However, it *is* possible that the issues some people have been having with "calculating..." taking too long have to do with these files swapping in and out of the temp folder. To test this, you can try excluding /private/tmp *temporarily* from scans to see if this fixes your issue.
I say temporarily, because tmp is a common staging ground for both legitimate and malicious software, and if something is caught while still in this folder (which is readable and writeable by everyone), it will likely never get as far as doing anything actually malicious on the system it is attacking.
That said, could someone with .$$$ files logged please use either the free app Sloth, or the terminal command:
lsof |grep \.\$\$\$$
and post the results? This should tell us what application, running process etc. is involved in creating these specific temp files.