Ah, so it was previously running, and then it got overwritten somehow?
My first instinct is to say that it's almost certainly due to either a non-hashcat-supplied script with a bug in it, or some other automated or security-related process. Nothing I'm aware of within hashcat itself would do this.
That being said, hashcat does open, close, create, delete, and truncate files in various ways, so it's theoretically possible that you've run into a bug in hashcat itself. Seems less likely, though.
My first instinct is to say that it's almost certainly due to either a non-hashcat-supplied script with a bug in it, or some other automated or security-related process. Nothing I'm aware of within hashcat itself would do this.
That being said, hashcat does open, close, create, delete, and truncate files in various ways, so it's theoretically possible that you've run into a bug in hashcat itself. Seems less likely, though.
~