I'm using Firefox that is run over our NFS (program stored on the server not on the Mac). That might be part of the problem. They said it has happened (though not as catastrophically) so I'm beginning to suspect that this is just part of how my Firefox is interacting with the update page.