Viral defamation

[simont]

In the past 24 hours I've received four emails from random people asking me if I wrote a computer virus.

The emails have been relatively nonspecific (they've tended to assume I already know what they're talking about), but from what I can gather, lots of people's Windows boxes are suddenly putting up error boxes referring to an executable file with a variable name (all the reports I've had have called the file by some different jumble of random letters), which lists ‘Simon Tatham’ as its author, and apparently this file is infected with the ‘GoldG’ virus. I suppose all the people who have emailed me must have googled the listed author's name and found my website and email address. So I'll probably have to put up a notice on my front page saying it's nothing to do with me, if only because I anticipate the email load getting worse rather than better…

Supposing my correspondents' analysis is accurate, I wonder if the virus writer would be liable for some sort of defamation of my character? Or, I suppose, of the character of someone else with the same name – after all, there's nothing unambiguous to indicate that they mean me. Indeed, for all I know, the real virus writer might turn out to be a guy who genuinely does share my name. That would be even more annoying.

(Not that I expect it'll be realistically possible to catch them, and defamation would doubtless be nowhere near the top of the list of stuff to haul them into court for if anyone did, but just out of curiosity.)

Comments

[eponymousarchon.livejournal.com]

Worse scenario: Part of the malware's code is derived from PuTTY?

[simont]

I suppose it's perfectly possible that malware has used my code in the past. (Which would throw no blame on me – there's no end of infrastructure code in stuff I've written which would be just as useful for nefarious purposes as constructive ones, because the same sort of organisational stuff will always need taking care of no matter what top-level task you're trying to do.)

To put my name in the Windows executable metadata, though, is more sinister; the only way I can think of for that to get there by accident is if they cloned-and-hacked some part of my build scripts, and really, if they're going to copy anyone's build system I doubt they'd pick mine – it's all Unixy and idiosyncratic and weird. So I'm more inclined to think that has to have been done deliberately.

[eponymousarchon.livejournal.com]

This is the part of the conversation where I express a failing of empathy with malware writers and a bewilderment at why someone would *do* that.

Have you made enemies in bad circles? :)

[simont]

Not to my knowledge, but then, they wouldn't necessarily tell me if I had!

[eponymousarchon.livejournal.com]

How dare you be a constructive part of the open source community!

*koff* Well, quite.

[tigerfort.livejournal.com]

I'm tempted to suspect that this might, in fact, be the cause, unfortunately. (If there is an intentional cause, rather than, say, a program scumming Windows registry entries for software authors.)

[eponymousarchon.livejournal.com]

I'm having flashbacks to schoolyard bullies here. Unfortunately, I have the feeling that there's quite a lot in common there.