MSU Listserv


MSUNAG Archives

MSUNAG Archives


MSUNAG@LIST.MSU.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV at MSU

LISTSERV at MSU

MSUNAG Home

MSUNAG Home

MSUNAG  April 2004

MSUNAG April 2004

Subject:

Re: Outgoing alert from the MSU Abuse team

From:

Rich Wiggins <[log in to unmask]>

Reply-To:

Rich Wiggins <[log in to unmask]>

Date:

Tue, 6 Apr 2004 20:57:53 EDT

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (101 lines)

Steve,

NAG told us clearly that we need to give a "heads up" whenever
we do a mass mailing to end users, so that computer support people
would not be caught unaware.   Hence the note about the key logger...

As for this mailing, I think it IS going to the address of the person
whom the DHCP registration shows is the owner.  I'm not sure we have
a database that also shows "the entity" that is responsible as well.
I think you really mean the computer support person for that entity;
mailing the chair of the department or college might lead to even more
confusion. In many cases the computer might already be registered to
the computer support person in question, so s/he IS the one who receives
the e-mail.

In any event, I think it's going to be hard to give a heads up to
NAG before we send out a mailing, AND send a mail to the affected
end users while simultaneously mailing their respective computer
support staff...

Maybe this is something to discuss at a face to face NAG meeting?

In this case, as I understand it, there are only a few affected
users, and most are in dorms.  Let's hope this key logging incident
doesn't expand to involve more end users and their NAG support folks.

/rich


>Here's a policy question, based on the mail going to people who
>have the keylogger trojan installed.
>
>If this isn't already happening, I think it would be an excellent idea
>to include the person who is responsible for those machines to be
>CC'd on the mail.
>
>I would love to get a notice of any and all machines that I maintain
>that  have problems.  Sending mail to the entity that dhcp registered
>the machine, would be great, or to the person listed for static IP
>address machines.
>
>Apologies if this is already being done.
>
>--STeve Andre'
>Political Science
>
>On Tuesday 06 April 2004 06:10 pm, Jeff Goeke-Smith wrote:
>> We have been informed of a number of hacked machines on campus.
>> These machines have been compromised with a keylogger.  Below is the
>> message we will be sending out to the registered owners of those
>> machines.
>>
>> ----- Forwarded message from MSU Abuse Response <[log in to unmask]>
>> -----
>>
>> From: MSU Abuse Response <[log in to unmask]>
>> Subject: [MSU Network Abuse] Your machine infected with KEYSTROKE LOGGER
>>
>> To:  realname
>>
>> URGENT:
>>
>> This machine has been infected with a "keystroke logger" which is
>> capable of stealing all passwords or credit card numbers typed in
>> through it.   This machine was found to be part of a network of
>> compromised machines, so the risk to your personal information
>> is VERY HIGH.
>>
>> - -----
>>
>> We have received one or more reports indicating that a computer under
>> your control or associated with your user id is infected with a virus.
>>
>> The computer was located in <location>              on 03/  /2004
>> and is registered via DHCP as follows:
>>
>>   (replace with DHCP registration info)
>>
>> This virus is causing your computer to behave in a disruptive manner,
>> either by sending virus-laden e-mail messages, by sending network
>> probes, or both.  Depending on the virus, it may also allow remote
>> access to your computer system, or it may delete files or damage the
>> operating system on your computer.
>>
>> In order to stop these actions, you need to update your virus software
>> and make sure that it eliminates this virus from your system.  If you
>> need help with this task, you should contact the Computing Service
>> Centers, at 432-6200 or "[log in to unmask]".  You may also want to consult
>> the following web sites for more details:
>>
>>      http://help.msu.edu/virus/
>>
>> You must also ensure that your computer's operating system
>> has all the current patches.  For Windows computers, Microsoft
>> is releasing critical security patches almost every month;
>> you need to run Windows Update regularly to install them.
>>
>> If we receive further complaints concerning your computer, your network
>> access may be disabled for the protection of your computer and others.
>>
>> Please respond to "[log in to unmask]" when the problem has been corrected.

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2023
June 2023
May 2022
April 2022
March 2022
February 2022
December 2021
January 2019
August 2018
June 2018
May 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001

ATOM RSS1 RSS2



LIST.MSU.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager