ILOVEYOU worm (fwd)

Alex A. Emanov alex at
Fri May 5 01:23:21 GMT 2000

Forwarded message from bugtraq:

The worm spreads via email as an attachments and via IRC as a DCC download.

The first thing the worm does when executed is save itself to three
different locations. Under the system directory as MSKernel32.vbs and
LOVE-LETTER-FOR-YOU.TXT.vbs and under the windows directory as

It then creates a number of registry entries to execute these programs
when the machine restarts. These entries are:


It will also modify Internet Explorer's start page to point to a web page
that downloads a binary called WIN-BUGSFIX.exe. It randomly selects between
four different URLs:

I've not been able to obtain copy of the binary to figure out what it does.
This does mean the worm has a dynamic components that may change its
behavior any time the binary is changed and a new one downloaded.

The worm then changes a number of registry keys to run the downloaded binary
and to clean up after itself.

HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\Start Page

The worm then creates an HTML file that helps it spread,
LOVE-LETTER-FOR-YOU.HTM. This is the file DCC'ed to others on IRC.

The worm then spreads to all addresses in the Windows Address Book by
sending the file LOVE-LETTER-FOR-YOU.TXT.vbs as an attachment. The
email starts:

	kindly check the attached LOVELETTER coming from me.

Then the virus searches for attached drives looking for files with
certain extensions. It overwrites files ending with vbs, and vbe.
It overwrites files ending with js, jse, css, wsh, sct, and hta, and
then renames them to end with vbs. It overwrites files ending with jpg
and jpeg and appends .vbs to their name. It finds files with the name
mp3 and mp3, creates vbs files with the same name and sets the hidden
attribute in the original mp* files.

The it looks for the mIRC windows IRC client and overwrites the script.ini
file if found. It modifies this file to that it will DCC the
LOVE-LETTER-FOR-YOU.HTM file to any people that join a channel the
client is in.

You can find the source of the worm at:

More information about the samba-ntdom mailing list