Archives

April 2004 (7)
March 2004 (12)
February 2004 (12)
January 2004 (22)
December 2003 (19)
November 2003 (16)
October 2003 (26)
September 2003 (18)
August 2003 (38)
July 2003 (80)
June 2003 (13)
May 2003 (24)
April 2003 (76)
March 2003 (75)
February 2003 (51)
January 2003 (73)

Category

Family (5)
FYI (18)
Games (2)
Geek (88)
Geographic (3)
Hacks (13)
Home (15)
Humor (54)
Ideas (20)
Ideaspace (15)
Local (15)
Metadata (10)
Microsoft (2)
MovableType (5)
Nitwits (66)
PKI (2)
Politics (22)
Quotes (3)
RDF (15)
RSS (4)
Security (3)
Semantic Web (13)
Site Info (13)
Social Networks (1)
Spam (9)
Sysadmin (1)
Tips (2)
Tivo (2)
TMFTOTHD (1)
To Do (1)
Unlisted (1)
Web (3)
Windows (1)

Local

« MetroBlogs »
DC metroblogs
beltway bloggers

Links


Assorted bits

Blogroll Me!
GeoURL
Listed on BlogShares




March 31, 2003

Forged spam virus

Apparently some jackasses are spamming the net with messsages containing a virus masquerading as a screensaver. To make matters worse they're now forging other people's mailing addresses. So it might look like a message coming from someone you know.

If you get a message and it contains a file with .scr in it DO NOT OPEN IT.

It might be fair to say you should generally /avoid/ using mail with attachments. If want someone to see a file, picture or something that's available on the web, don't send them the whole FILE as an attachment. Just send them a link to the website.

Meanwhile, as you get mail from people take a look at the size of the incoming message. Most of the time viruses will be much larger than a normal text message. Don't even bother to open those messages, just delete them. If you're not expecting someone to be sending you attachments then don't risk opening viruses. Send them a message asking if they meant to send you a big file attachment. There is, of course, the chance they meant to do this.

If you get a message that's been forged, forward it to the abuse departments of the ISPs involved. These spammers hop on the net from various places. Those are listed in the headers of the message. It takes some geek wizardry to open the headers, read them and find the source IP address. But with that you can do a traceroute (or tracert for you Windows folks) and see the path to the source IP address. Look for the ISPs directly 'upstream' from the source address. Visit the ISP website or send mail to 'abuse@' the ISP domain.

Slowly but surely someone will pin down who and where these jackasses are. I, for one, suggest tar and feathering. Or flogging perhaps. Those near maritime areas could perhaps keelhaul them. Speaking of which, when does Talk like Pirate Day come around again? Arrrrrrr......

Nitwits
Perma  | Comments (0) | TrackBack (0) | 10:15 AM  | xml
Comments
Post a comment






* if you do not leave a valid e-mail or URL your comment may be deleted *







Navigation

Recent Entries

America and Europe: Vive la différence?
Server changes afoot
Diet behavior mod
Googling for sensitive info
Outlook 2003 and IMAP, a marriage made in Hell
Bike to Work Day, May 7th
Speakeasy rocks
Zippo USB?
When geographic data is nowhere 'near' correct
Local campaign contributions

User comments
Trackbacks

Contact

send me an e-mail E-mail
chat with me using MS messenger MSN Messenger
chat with me via AIM America Online
chat with me on ICQ ICQ
chat with me on Yahoo! Yahoo
Add my vCard to your electronic addressbook vCard
Friend of a Friend FoaF

Syndication

XML  RDF  CDF

Comments

XFML

Extra Stuff

foaf
vCard
pgp info
Linked In
Powered by
Movable Type 2.64