I ran a scan on my mac and it came up with four infections. Three of them I could move to the virus chest and then delete them but the fourth comes up with message
It was recently brought to my attention by a Mod. in this forum that malware removal is not to be discussed in this section of the Avast forum, but instead should be discussed in the Virus & Worms section. However the Malware Removal Specialist in that section of the forum only remove Windows malware. So you have three options:
Open a thread in the Virus & Worms section in Avast and I will attempt to get a Mod. in that forum to assist you who is familiar with Macs.
Contact apple tech. support or bring your machine into a retail apple store for diagnostics, which usually takes 2 days, and they will most likely wipe your HD.
In the meatime, turn OFF Time Machine, if Time Machine is connected to an external HD also disconnect this, do not sync this machine with any other devices, turn off iCloud for this machine until a malware specialist has given you further instructions. Do not insert a USB drive into this machine. Thank you.
/.MobileBackups/ is a special folder used by OS X to store temporary backups while away from Time Machine, you shouldn’t tinker with it and the files get deleted automatically, the permission denied comes from the fact that the system does not allow that folder to be changed. After the next TM backup the MobileBackup will likely get deleted. Anyway, in my opinion, you shouldn’t really worry about this, this is not an infection, it’s just a backup of a previous state of your Mac.
In fact, let me add that the file in question is an .exe, it’s probably a Windows virus but it cannot infect a Mac, Macs don’t execute .exe files. Avast! also detects Windows viruses and this is apparently something you downloaded for Windows.
EDIT: It’s also possible that the operation is denied because the file no longer exists.
Ok so what you’re saying is do a backup? I have been overseas for three months so of course this hasn’t been done in a while… Then perhaps run another scan to check that the issue has been removed?