Slashdot Mirror


New, More Destructive Love Bug Variant

Everyone and their brother wrote in to say that a new and more destructive version of the ILOVEYOU virus has hit the net. Instead of deleting on a few files, this one deletes every file not in use. And even more amusing, rather then using a hardcoded subject line, it uses the host's email archive to cause the subject to change while it propogates. Intelligent mail client users continue to be unaffected (although the ILOVEYOU sympathy virus has been annoying the heck out of us for days now... it works on the honor system: Please delete some files and mail to all your friends).

28 of 404 comments (clear)

  1. Re:virus vaccine by Anonymous Coward · · Score: 4

    could someone please alter this virus so that its payload turns off the registry setting that allows it to propagate, and end this mess once and for all? a self-vaccinating virus, what a concept. then we can safely ignore this problem (for a while).

  2. If you want to see something scary . . . by Straker+Skunk · · Score: 5

    . . . check out this file, on the Samhain project. This is basically a polymorphic-stealth worm system, that was developed as a proof-of-concept (and was never finished).

    It's cross-platform (as in, Unix and NON-Unix), it goes really far to evade detection and analysis (not to mention removal), and the freakiest part of it is, the whole system was designed to work in a distributed, intercommunicable fashion ("wormnet"). It's scary shit. Especially an observation the lead programmer makes near the end-- "sure, we didn't release this, but what if some other intelligent but deranged programmer out there has?"

    --
    iSKUNK!
    1. Re:If you want to see something scary . . . by Matts · · Score: 4
      Damn slashdot - many moons ago Extrans worked for links...

      Sorry I already debunked this virus when the details were posted to Linux Today. You can read my post at http://linuxtoday.com/news_story.php3?ltsn=2000-05 -12-003-06-SC.

      If you don't want to click the link, the summary is this virus is stopped by firewalls. It would be dead in the water in the modern internet.

      --

      Matt. Want XML + Apache + Stylesheets? Get AxKit.
  3. Who will be the hero... by Wakko+Warner · · Score: 4
    ...who releases an email "virus" that shuts off the real virus -- VBScript -- after sending itself to everyone in the user's address book?

    - A.P. (seriously, folks, WHAT ELSE is VBscript for?!)
    --


    "One World, one Web, one Program" - Microsoft promotional ad

    --
    "Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
    1. Re:Who will be the hero... by Vanbo · · Score: 4

      > DEL C:\WINDOWS\SYSTEM\WSCRIPT.EXE
      > DEL C:\WINDOWS\SYSTEM\CSCRIPT.EXE

      This is really the solution if people refuse to switch from lookout. (I had switched everyone I could when I arrived at the company, but some refuse to leave "what they know.")

      So here is my solution in a Novell Netware enviroment.

      -Using NAL (Novell Application Launcher), create a new application object in NWAdmin. Don't have it launch any program, Name it something like "Remove VBS."

      -Modify the "Files" tab by adding "wscript.exe" and "cscript.exe" to be deleted (In otherwords click file, in target select those programs, and put the check in "Target to be deleted.)

      -Associate with everyone group with force run status

      Now everyone is going to be better off. Some would complain that now people can't write scripts in VB on their machines, but guess what I never got any complaints. Maybe it has something to do with the fact that anyone writing scripts knows better then to open unknown attachements, or even to use outlook.

      Note- This process could be done with the login script but NAL gives you more control. For instance I have used NAL to remove registry entries (or add), reset Netscape preferences, and similar to above, have NAL delete "normal.dot" every login to help prevent the spread of Macros. At my previous job, I even went so far as to have NAL rename the vbe folder in office to turn off macros all together, and created a NAL application called "Word with Macros, Excel with Macros" that would rename the directory before launching, and rename it at close, but alas, they use the macros in Excel at the current place...

      --
      VANBO
    2. Re:Who will be the hero... by ucblockhead · · Score: 5

      A less drastic action:

      (For those forced to do Windows/Outlook.)

      My Computer
      -Tools
      -Folder Options
      -File Types
      -VBScript Script File
      -Advanced
      -Click on "Edit" in the list box
      -Set Default

      After you do this, the default action for a VBS file is to edit it in notepad. (And you can still run it by right clicking and selecting "open" from the menu.)

      Repeat for any other dangerous filetypes.

      --
      The cake is a pie
  4. Here's a NEW idea: by paRcat · · Score: 5

    Why don't we start taking the usefullness of a virus back?

    What I mean is, why doesn't someone write a virus that does good? It could auto-run and disable all of the cheesy security holes that MS hasn't fixed yet. It could spread like a worm, and just go on a rampage fixing problems.

    Why must virii always be bad?

    1. Re:Here's a NEW idea: by Wanker · · Score: 5

      This topic comes up in virtually all intelligent virus discussions. In summary, it is not a good idea to use viral properties, even for something useful. I refer you to item F7 in the comp.virus FAQ (circa 1995):

      A very hotly debated topic that has flared-up dramatically several times in Virus-L/comp.virus. The answer to this is not simple and largely hinges on your definition or interpretation of the term computer virus.

      By definition (see B1), viruses do not have to do something "bad" (although many people argue that the uninvited "resource wasting" that is almost inherent in viral activity is necessarily bad). From this point (and based on his somewhat esoteric definition of the term computer virus) Fred Cohen has argued that "good" or "useful" computer viruses are a serious possibility. In fact, Dr. Cohen offered a reward of $1000 for the first clearly "useful" virus--despite several potential claimants, however, he hasn't paid up.

      Although there has never been a position that was widely agreed upon as a result of any of these discussions, many contributors to this forum believe that there are serious problems with the idea of implementing useful computing functionality through self-replicating programs. Vesselin Bontchev's paper originally delivered at the 1994 EICAR conference, titled "Are `Good' Computer Viruses Still a Bad Idea?", is available by anonymous FTP from ftp.informatik.uni-hamburg.de (IP = 134.100.4.42), as pub/virus/texts/viruses/goodvir.zip. *Anyone* wishing to raise this discussion in Virus-L/comp.virus again should read and carefully consider this paper before posting. It contains many strong arguments against the idea of "good computer viruses", and some prescriptions of how good viruses would have to be implemented and distributed to deserve the label "good". To date no strong arguments countering the points in this paper or otherwise arguing in favor of the concept of good viruses have been posted to the group.

      The summary of points made in this paper are:

      1. Lack of Control
        Even features such as defined lifetimes, central verification, etc. can't control self-replicating code perfectly. It is very easy for viruses to "get away". A great number of the viruses in the wild started out as merely research projects and were never intended to be released.
      2. Recognition Difficulty
        Allowing one program which has viral properties through one's defenses makes it easy for other programs to exploit the same hole. It's hard to tell when a "good" virus is doing its work versus a "bad" virus.
      3. Resource Wasting
        The process of infection will use up system resources-- what happens when the program hits a host that has few resources to spare?
      4. Bug Containment
        What happens if you discover a bug in the viral code? How do you update all the installed copies?
      5. Compatibility Problems
        The software could break certain systems while it works fine on others. This could make for difficult-to-track problems.
      6. Effectiveness
        There are always increased risks with viral code, and they can't do anything that nonviral code couldn't do with lower risks.

      Vesselin even goes so far as to describe some mechanisms to help mitigate the above problems, but the crux of the story is that it's still simpler and safer to rely on non-replicating code.

      There are some examples of failed attempts at "good" viruses in Vesselin's brief. They include The "Anti-Virus" Virus, The "File Compressor" Virus, The "Disk Encryptor" Virus, and The "Maintenance" Virus. Some of these same ideas have been brought up in this very Slashdot discussion.

      Amazing what history can teach. Damn, I'm starting to feel old...

  5. Re:Procmail filter to protect your users (tool) by skull · · Score: 4

    I'm surprised noone has mentioned this wonderful procmail setup/script that has been around for some time to protect against HTML or file attachments in email.

    I've been using it for some time and it has protected myself and my users against almost any macro viruses I have heard about.

    http://www.wolfenet.com/~jhardin/procmail-securi ty.html

  6. Re:Linux is at fault here... by Matts · · Score: 4

    Funny yes, but people seem to be missing the fundamental reason why this happened.

    It has nothing to do with MS letting people run attachments without saving them first.

    This is all about mapping extensions to applications.

    This is a broken idea - totally. For starters it is quite simply dangerous, as the mappings happen everywhere. And installing an application might setup random mappings. But add onto that the fact that its used to associate scripts with their executor, much like the shebang line, only worse - the file needs no execute privileges. If you like, every mapped file extension automatically sets execute privileges. It is this functionality that is broken - not the mail client. And this has been in existance since DOS days, IIRC. So removing or fixing this "feature" is next to impossible.

    Good luck MS fans - it's a rocky road ahead.

    --

    Matt. Want XML + Apache + Stylesheets? Get AxKit.
  7. Re:When will microsoft users learn? by mackga · · Score: 5

    You can get a freebie add-on from:
    Nemx called Power Tools. It runs as a service under exchange and allows stripping of attachments via extensions.

    --

    "shop smart:shop s-mart" ash

  8. Here'e the real problem by HomerJ · · Score: 5

    The real problem here with these kinds of things isn't just Outlook. Or just moronic users.

    The whole security system in Win9x is flawed. Windows9x was never intended to be on a network. Win98 is just a rehashed version of Win95, wich is just a rehashed Win 3.1. Single user OS's that had "root" access everywhere were fine in the early and mid '90s. That's not the case anymore. Now that everyone is hooked up to the itnernet, and other people have access to these single-user OS's such as Win9x. it's didn't matter that you had "root" back in the day, you were the only one using the system. Now many people can run code on you computer. Be it a vbs, java, etc.

    A *nix variant doesn't have this problem. Unix was deigned with networks and network security in mind for over 30+ years. I couldn't if I tried to screw up my system like these vbs files do to Windows computers.

    Even Win2k security is lax. For instance, how many times does a typical linux install(be it Redhat, Debian, or anything else) go "DON'T USE ROOT AS A USER!" and foces you to make a regular user account? Now look at Win2k's installation, that gives you your user name with admin. privs.

    If Microsoft really wants to stop stuff like this, they need update their entire network security model to the 21st century....or at least the 1970's. Windows9x was not designed to be on a network. That's the reason it has no security. "access zones" and what have you in programs like Outlook are just a cheap hack to hide the real problem of the Windows security model. The problem being, it wasn't designed to have one.

  9. Re:In theory. . . by Pig+Hogger · · Score: 4

    and since Macintosh uses a less visible means of specifying file types,

    Macintrash files have, in fact, two invisible 4-character extensions.

    The filetype -- it contains the file type which says what kind of data is in the file.

    The creator -- which identifies the application that created the file, and which should be used to work with the file.

    Applications have a file type of 'APPL' and the creator field identifies the application; that is, it is what ends up in the "creator" field of files generated by this application.

    Additionnal trivia: Beige toaster files are, in fact, divided in two. There is a data fork , and a ressource fork . The ressource fork contains information that can be easily edited by a resource editor program, allowing to change certain aspects of, say, an executable file, like the icons, fonts, sounds and strings it uses. The data fork contains, well... (drum roll) data... (In the case of an APPLication, it is the actual binary code. GUI details are in the ressource fork). Either (of both) of those data fork can be of zero length.

    It is not a bad system, except that it is totally shielded from lusers and, although it can prevent them from doing mayhem on their filesystems, it is a royal pain in the ass to change if you don't have the proper utilities.

    I suppose it could be desirable to have a filesystem that allows you to have as many forks on your files as you want (did I hear somewhere that Windoze NT has something like that? Or is it Novell?), but in my opinion, nothing beats the simplicity of a "flat file" filesystem such as we enjoy so much on Linux.

    However, I still don't dislike the concept of embedding file type information and whatnot within the directory entry/fdn.


    --
    Here's my mirror

  10. Re:I'm curious... by iCEBaLM · · Score: 5

    You can't possibly consider a virus writer to be an artist? I'm sure that some of code they produce is elegant, or at least quite advanced and technical. But to call the result of that work 'art' is just fallacy.

    Unfortunately, destruction is creative.

    -- iCEBaLM

  11. I'm curious... by Psiren · · Score: 5

    Do any virus writers read Slashdot? And if so, would any of you care to explain *why* you do it? Ignoring the simple macro viruses, some stuff, especially the polymorphic ones are incredilbly clever pieces of code. Why put that talent to waste?


    Now weary traveller, rest your head. For just like me, you're utterly dead.

    1. Re:I'm curious... by segmond · · Score: 5

      You can not tell an artist that what he has produced is a waste just because you do not understand it or find it useful. There is some excitement in creating something that is sort of "alive". I have seen very smart virus writers, crackers and shit, and they are very clever, but don't think by putting them into a different environment, they will start cranking out really impressive code. Nah, they have the ability, but what drives them to write their viruses or crack a software is probably not what drives them to write "productive software". As a matter of fact, they probably feel that their viruses is an utilization of their talents.

      --
      ------ Curiosity killed the cat. {satisfaction brought it back | it didn't die ignorant | lack of it is killing mankind
  12. Next Version by Anonymous Coward · · Score: 4

    The changing subject line helps its messages avoid being deleted by the Spam filters, but since the message does not change, the user is not likely to thinkt that it actually came from the person it says it does. What these viruses need to do is examine the context of all of the messages in the user's Inbox that come from the individual who it is being sent to and generate a context-sensitive reply to that individual.

    In addition, these viruses will ultimately not be limited to VBA. A program could easily open the default Netscape inbox text file and scan for the @ character--extracting all e-mail addresses in the entire Inbox file. The virus could also discriminate against which users it destructively effects--deleting only the files of people whose identity says they are in the aol.com domain, for instance.

    I think that we have only seen the tip of the iceberg as far as intelligent viruses that are distributed by e-mail.

  13. Procmail filter to protect your users by qi3ber · · Score: 5

    I posted this filter up on freshmeat as well, but now that there is a more destructive version of this floating about, it should be distributed more. All you admins who are using procmail can add these two rules to your global procmailrc to prevent the execution of .vbs attachments to email messages. The email isn't deleted, just that the files extention is changed so that it will not execute on the end users system.

    :0 Bf
    *!^X-Loop: viruscheck
    *^Content-Disposition:[> ]+.*[Aa]ttachment.*\.[Vv][Bb][Ss].*
    |/usr/local/bin/sed -e '/Content-Disposition:/{N; s/filename=\(.*\)\.vbs\(.*\)/filename=\1.vbs.txt\2 /i;}' -e '/Content-Type:/{N; s/name=\(.*\)\.vbs\(.*\)/name=\1.vbs.txt\2/i;}' | /usr/local/bin/formail -i "X-Loop: viruscheck"

    :0:
    $ORGMAIL

    If you have any questions, please feel free to contact me about it.

  14. Heh by CAIMLAS · · Score: 4
    Humorous how such things are called sympathy viruses in linux. I'd hash in the lot of stupid forwards as a type of sympathy virus - they 'delete', so to speak, bandwidth.

    I woke up this morning to my radio. (Which is unusual. It usually takes my alarm going off at full volume for about 10 minutes. The alarm goes off after 10 minutes of full-volume radio.) I heard the announcer state that there was a new strand of the ILOVEYOU virus released, much more deadly. I just rolled over and went to sleep. I pitty the fool who subjects himself to such things.

    What type of real-life virus might computer viruses be comparable to? STD's? You 'sleep around' without protection, you'll get em. What might that make Microsoft products, then? :)

    -------
    CAIMLAS

    --
    ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
  15. Warning: ILOVEYOU virus spreads to Unix systems! by babbage · · Score: 5
    received in my mailbox recently:

    -- forwarded text begins --

    This is the Unix version of 'I Love You' which works on the honor system.

    If you receive this mail, you should delete a bunch of GIFs, MP3s and binaries from your home directory, then send a copy of this e-mail to everyone you know.

    -- forwarded text ends --





  16. Re:When will microsoft users learn? by Rico_Suave · · Score: 4
    Uh, I run a MS Exchange server for over 100 users. I simply filter out anything with a vbs attatchment. Didn't have a problem two weeks ago, don't have a problem today.

    It has NOTHING to do with the OS used, and everything to do with the administrator.

    --

  17. We need more tecnological diversity... by jonr · · Score: 5

    If I may quote my favorite CEO: "Pursuing the biological simile, observers pointed out another problem caused by Microsoft's monopoly: the lack of genetic diversity in the PC ecosystem. Because PCs and their software are too similar, one noxious automaton can do much more damage than would occur if we had several alternative life forms.
    This argument deserves closer examination. True, BeOS, MacOS, and Linux users were not infected by the Love virus. Had each system had 25% market share, a single virus could only infect 25% of the population."

    The ILOVEYOU virus is kindergarden stuff compared to what a real programmer could really do if he/she put their mind to it, but since experienced programmers are (most of the time) fairly matured individuals, but it would only take one fairly good hacker to release a plague on the world...

  18. A certain amount of turbulence is good by gelfling · · Score: 4

    It helps to thin out the herd. What you want is a more or less constant nonzero low probability of catching and incurring damage from one worm/virus/trojan or another. This will serve to harden the resistance of the community and cull out the weaklings. Just like in the solid world the most destructive virulent phages do not have the best logevity because they kill too many of their hosts too quickly. Ergo the liklihood of some super Marburg or Ebola with 97%+ mortality spreading all over the world is rather low. Of course the garden variety with 70%+ mortaility is none to good either. OTOH a continual exposure less virulent forms of other types of phages actually hardens both the individual and the community leavingit better prepared to resist the next variant. Exhibit the indigenous peoples of the Americas in the 15th-16th C. exposed to Smallpox for the first time. Infected populations decreased by 90% in <10 years whereas the Europeans were already largely resistant and could survive even many epidemics with <25% mortality.

    So it is with a dynamic community of computers. Somebody who doesn't have a scanner will die. Somebody who rarely updates the sig files will die. Somebody who doesn't think it can happen to them will die. Someone who doesn't pay attention and goes on as normal will die. Somebody who is more thorough and less trusting or ignorant will survive. Remember not all of these screaming headlines are about viruses at all. They are simply a matter of benhavior and social engineering. Do you think as many people would have been infected if the ILY worm had a heading that said "opening this note will destroy or damage your machine and the machines of everyone in your addressbook." OF course not.

    Which leads me off in another tangent. How to get more people to open destructive messages since everyday we're more jaded and suspicious? Well if I was a badguy what I'd do is use the message header to refer to some online purchase. Sure, if you didn't buy anything then you'd be less likely to open the message but the people who did would probably open the message approaching 100%. So what is a poor website to do? It seems that one avenue that should be pursued for this and for eComm generally is a way to generate a CRC at the point of purchase and then send the confirmation/receipt with the CRC in the header so that before you do anything you manually cross check the numbers to insure they match. Or something like that. I guess I'll stop blathering now.

  19. You think that's bad. by basscomm · · Score: 5

    Check out the virus warning I recently came across:

    Pay close attention to this warning!

    If you receive an email entitled "Bad-times," delete it immediately. Do
    not open it. Apparently this one is pretty nasty. It will not only erase
    everything on your hard drive, but it will also delete anything on disks
    within 20 feet of your computer through the use of subspace field
    harmonics. It demagnetizes the stripes on ALL of your credit cards. It
    reprograms your ATM access code, screws up the tracking on your VCR and
    uses subspace field harmonics to scratch any CD's you attempt to play. It
    will program your phone auto dial to call only your mother-in-law's
    number. This virus will mix antifreeze into your fish tank. It will drink
    all your beer. (For God's sake man are you listening?) It will leave
    dirty socks on the coffee table when you are expecting company. It will
    replace your shampoo with Nair and your Nair with Rogaine, all the while
    dating your current boy/girlfriend behind your back and billing their
    hotel rendezvous to your Visa card. It will cause you to run with
    scissors and throw things in a way that is only fun until someone loses an
    eye. It will rewrite your backup files, changing all your active verbs to
    passive tense and incorporating undetectable misspellings, which grossly
    change the interpretations of key sentences. If the "Bad-times" message
    is opened in a Windows95/98 environment, it will leave the toilet seat up
    and leave your hair dryer plugged in dangerously close to a full bathtub.
    It will not only remove the forbidden tags from your mattresses and
    pillows; it will also refill your skim milk with whole milk.

    *********WARN AS MANY PEOPLE AS YOU CAN.*********

    Hope I don't get that one.

    --
    http://crummysocks.com
  20. Ah, the sweet symmetry of cross-pollination by jabber · · Score: 4

    I LIKE IT!

    We're genetically engineering bacteria to eat oil spills, and designing cancer cells to secrete insulin. We're cloning sheep and making real viruses to attack malignant tumors.

    Somehow, the symmetry of a worm that scours the Internet exploiting M$ security holes in an effort to fix them is.. poetic. Sort of like autonomous garbage collection.

    Arguably, any virus/worm that deletes Windows system files is already trying to do this; but in a very heavy-handed way. A lighter touch is called for. Disabling the registry settings that allow auto-invokation of scripts attached to email is one good way to make the world a better place.

    And hey! How could anyone (besides Micros~1) get upset over a benevolent virus?

    Maybe it could even open a pop-up on the screen every 20 minutes, to remind the user to stretch their hands to prevent RSI? :)

    Maybe it could replace the talking paper-clip with a talking Penguin? "I see you're trying to write a letter. Wouldn't you rather write it on actual paper, and add some humanity to your interpersonal communicaton?" "I noticed your key-stroke rate drop over the last hour. You seem tired. Shall I have some pizza delivered?"

    --

    -- What you do today will cost you a day of your life.
  21. It's a *worm*, not a virus! by dmuth · · Score: 4
    I hate to bitch, but I really wish people (namely the media) would get the terminology right when writing about these things. This isn't a virus, it's a worm.

    Viruses infect other executables, such that the original functionality is still there, but the viral code is executed when the program is first run, which gives it a chance to spread to other executables and/or become resident in memory.

    Worms, on the other paw, are self-contained programs which contain nothing but the worm itself.

    The definitions of these things are hardly new, they have been around for YEARS. I suggest reading section B2 of the comp.virus FAQ for more information.

  22. Re:These are great for Linux - we need more by SoftwareJanitor · · Score: 4

    As has been thoroughly hashed out in the threads of the articles following the last virus/worm outbreak, Linux isn't 100% immune from viruses/worms, but it is much more resistant due to a few reasons:

    First, executability is determined by access bits, not by file extension. This means that normally downloaded files like attachments get saved un-executable, meaning that users have to intentionally try to change the access bits on the files to execute them, not just click on them.

    Secondly, unless the root user is the one reading the email and running attachments, the virus/worm is limited by security/permissions rights to what it can do. While it can do damage to a single user's files, it can't very easily blast other user's files or system files. On Windows 9x, there is basically no security, so viruses/worms like ILOVEYOU are free to twink with the registry, etc.
    Thirdly, the homogenous nature of the Windows world makes it a much easier and more attractive target for virus/worm authors. It is pretty safe to assume that virtually all Windows 9x clients will have Outlook and all the associated DLLs on their system. There is no single email client in the Linux world that is so ubiquitous. That makes it more difficult to write viruses/worms that will affect a large percentage of Linux users because the virus/worm creators can't make the kind of assumptions about how to read things like address books, etc. that they can under Windows. This is unlikely to change any time soon, because the Linux world is much more diverse than the Windows world.

    While you are right up to a point that in many ways it is the users that are stupid, Outlook and Windows make the problem worse by making it so much easier for the users to shoot themselves in the foot. And to a certain extent, Windows is plagued with a much higher percentage of stupid users because it intentionally caters to the least common denominator. To a certain extent, as Linux gets easier to use, it may start to see more of the semi-stupid users.

  23. Linux is at fault here... by finkployd · · Score: 5

    Hear me out. Linux is Microsoft's main competition right now. Because of this we are forcing them to "innovate", something they would usually avoid.

    Now if MS Bob has taught us anything, Microsoft is not a company that should be innovating. When they do, they don't come up with things like "better security" or "stability", they come back with "talking paperclips", and "throw in every usless feature we can think of, memory footprint be dammed".

    Unfortunatly, they also come up with the bright idea of executing email. Now MIME attachments aren't enough, they want you to be able to run/open attachments right when you get them (presumably to make sure you EXECUTE .exe files to make DAMN SURE you read any EULA contained within). This sounds like a good idea to people who believe renaming directories to folders made computing possible for the common man, but security wise it's like vigorously shaking a package from the Unibomber.

    So my friends, we are to blame. We pushed them into frantically trying to invent "necessary" features to stay on top, and look where it got us. Many of us are watching our beloved mail servers go down under the strain and rebuilding our company's PC because of our pointless competition with Micosoft.

    I implore you all, please just drop this Linux thing before Micosoft innovates again.

    Finkployd