This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Triggering a Virus that takes all disk space

I have discovered a problem in running your software. This is happened on 2 different Macintosh computers (although one is just a migration of the information on the other). When I use your Sophos program to scan my hard disk for viruses, everything goes along fine until it reaches a certain number of around 197,000 (that number does not matter).

It is there that it stalls and appears to be working on a very large file. The reality is that it seems to trigger some sort of virus that completely fills up the empty space on my hard drive in about 20-30 minutes, until I get a warning that I have run out of disk space. Then I have to force quit my computer as I am unable to save files or even quit programs. Again, this happened twice and when I tried it a third time, I shut it down before it filled my hard disk again. 

Please advise me on the best solution to this problem. I don't want to run it again as I have already caused enough problems with it and the virus has not yet been removed. 

:1006057


This thread was automatically locked due to age.
Parents
  • Here Sophos, tell me if this 57 MB DMG that Disk Utility says is fine really needs more than my SSD's available 77 GB to decompress:

    http://neverball.org/ > Download > neverball-1.5.3.dmg

    If not, then it's a bug in the scanner.  Took me all day to find because I couldn't figure out how to determine which file the scanner was "working" on; all I could do was slowly iterate with the scanner over different sets of directories.   If there is faster way, *please* let me know.

    Tried 8.0.2C and 7.3.10C on a MacBook2,1 with 10.6.8 and 3 GB RAM.

    :1006351
Reply
  • Here Sophos, tell me if this 57 MB DMG that Disk Utility says is fine really needs more than my SSD's available 77 GB to decompress:

    http://neverball.org/ > Download > neverball-1.5.3.dmg

    If not, then it's a bug in the scanner.  Took me all day to find because I couldn't figure out how to determine which file the scanner was "working" on; all I could do was slowly iterate with the scanner over different sets of directories.   If there is faster way, *please* let me know.

    Tried 8.0.2C and 7.3.10C on a MacBook2,1 with 10.6.8 and 3 GB RAM.

    :1006351
Children
No Data