Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Security Businesses Apple

Mac OS X Trojan Horse Infects MP3s 621

frequnkn writes "The Mac News Network reports that Intego has anounced an update to their anti-virus app for snagging the first Mac OS X Trojan horse, MP3Concept (MP3Virus.Gen), which exploits a weakness in Mac OS X where applications can appear to be other types of files."
This discussion has been archived. No new comments can be posted.

Mac OS X Trojan Horse Infects MP3s

Comments Filter:
  • by stecoop ( 759508 ) * on Thursday April 08, 2004 @03:42PM (#8807270) Journal
    In six years, Intego has made a name for itself in the Internet security and privacy market for Macintosh.

    I always wonder where the sources are for the majority of viruses. It is quite ironic that a company selling you a fix happens to find the problem and releases the solution for the low price of 59.95. Yet a goggle and Symantec Security [sarc.com] search didn't yield anything about MP3Virus.Gen. Hmmm - it's awfully nice they fixed this virus so fast.
    • by Anonymous Coward on Thursday April 08, 2004 @03:47PM (#8807362)
      Somebody on macnn.com pointed out this: http://groups.google.com/groups?hl=en&lr=&ie=UTF-8 &oe=UTF-8&safe=off&frame=right&th=631707378ffe9292 &seekm=blgl-5D750C.02150821032004%40news.bahnhof.s e#link6
      • Second, an OS X application is actually a directory with '.app' trailing the name. This is possibly the dumbest thing that I've ever seen Apple do recently. Not only is it cumbersome and extremely resource intensive, but it is a glaring security hazard.

        A.) Apple didn't do it - NeXT did.

        B.) How is this cumbersome?

        C.) Resource intensive? Bollocks.

        D.) Glaring security hazard? Bollocks again. Double bollocks.
        • by rworne ( 538610 ) on Thursday April 08, 2004 @05:39PM (#8808986) Homepage
          NeXT did it for a good reason:

          NeXTSTEP ran on four different hardware platforms and had fat binaries. Within the foo.app directory, there'd be foo-moto, foo-386, foo-sparc, and foo-hpux binaries. The OS would then attempt to execute the appropriate binary for the hardware platform the OS was running on.

          OS X uses the .app directory so all the resources, bitmaps, and supporting files are in that one directory. That is why I can reinstall OS X and have MS Office X and all my other applications still work without reinstalling everything. I suppose they could still do fat binaries as well if they ever decided to do so.
          • by Mr Pippin ( 659094 ) on Thursday April 08, 2004 @06:17PM (#8809392)

            In NeXTStep V1.0( and I think 2.0), the entire application was stored in a Mach-O format file. Ultimately, there were resource issues involved in trying to keep the entire application and it's resources in a single Mach-O file, which resulted in this being splitup into a diretcory containing the resources, and the Mach-O file retaining the executable data required by the system loader.

            That's not all that different from how classic Mac OS apps were stored in different resource areas of a file.

            • by kabloom ( 755503 ) on Thursday April 08, 2004 @07:24PM (#8810110) Homepage
              I seem to recall that common Macintosh viruses were things like MDEF (menu definition) viruses or MBDF (menubar definition) viruses or WDEF (window definition) viruses. These are the names of certain kinds of code resources on Macintosh systems that could be used to define a custom look-and-feel in certain places where necessary. To hook up an MDEF virus and get it to execute, you would insert an MDEF resource into the program (*very* easy to do), and then modify one of the MENU resources to use that MDEF to draw itself. (similarly for MBARs with MBDFs and WINDs with WDEFs). There were also certain resource numbers you could choose to hide the corresponding system resources while running the program, and you wouldn't have to do anything else to change the program.
          • NeXTSTEP did not run on four different platforms. OPENSTEP might have - NeXTSTEP did not.

            And they never used 'fat binaries'. Apple did, NeXT did not. The whole idea of subdirectories under 'Contents' such as 'MacOS' contravenes this - they had different directories for different binaries at best, but remember, NeXTSTEP did not use HFS+, they used UFS, so there was no way they could have made a fat binary anyway.

            The directory as an app only means you have a different model for application development. They
            • by rworne ( 538610 ) on Thursday April 08, 2004 @09:59PM (#8811333) Homepage
              NS 3.3 ran on four platforms. That was the last version I used, and I distinctly remember it. There were even NeXTSTEP utilities that "thinned" out these fat applications and only left the thin executable you needed.
            • by MarcQuadra ( 129430 ) * on Thursday April 08, 2004 @11:14PM (#8811889)
              Sorry to burst your bubble, but the whole 'app is really a directory' thing is a SOLUTION to the 'resource fork' storage problem. And it allows for cleanly implemented multi-platform 'fat' binaries. Apple's Classic fat binaries were kludgy, the CODE resource fork held the 68K binary and the data fork held the PowerPC binary, hardly extensible.

              I've got an OSX install on purely UFS, and sure enough, it allows you to pack x86 and PPC binaries (or multiple PPC/X86 binaries, for optimization/bitness) into the same *.app so you can have one application file that executes on multiple architectures. It might not be Apple's hacked-up old kludgy way to get a 'fat binary' but it's effectively the same result but done MUCH cleaner and capable of living on many diverse file-systems.

              Imagine how cool it would be to have ONE shared 'applications' folder mounted read-only on all your clients, the x86 clients execute the x86 code from camino.app and the PPC machines execute the PPC code from the same place. It would be an administrator's utopia!
    • by eltoyoboyo ( 750015 ) on Thursday April 08, 2004 @03:52PM (#8807444) Journal
      We needed an OS X virus just to liven things up! The ratio of viruses in the wild to lab viruses leads one to believe that the Anti virus companies created some to keep them in business. The WildList [wildlist.org] should be enough to keep all the Antivirus companies on their toes now.
    • "It is quite ironic that a company selling you a fix happens to find the problem and releases the solution for the low price of 59.95. "

      [ Inigo Montoya ]
      I don't think that word means what you think it means.
      [ /Inigo Montoya ]

      That's not ironic. It may be, to tinfoil-hat-wearers, SUSPICIOUS, but it's not ironic at all.
    • by harlows_monkeys ( 106428 ) on Thursday April 08, 2004 @04:26PM (#8807975) Homepage
      It is quite ironic that a company selling you a fix happens to find the problem and releases the solution for the low price of 59.95

      You find it ironic that a problem is found by people who make their living looking for such problems???

  • Statistics (Score:4, Insightful)

    by Lord Grey ( 463613 ) * on Thursday April 08, 2004 @03:42PM (#8807271)
    One virus or Trojan every three years?

    I can stand that.

    • by Anonymous Coward on Thursday April 08, 2004 @04:19PM (#8807868)
      I chose the Trojan over the virus. My bloodwork came back negative, so it seems to have worked.
  • Conspiracy? (Score:5, Funny)

    by Kris Thalamus ( 555841 ) * <selectivepressur ... AGOom minus city> on Thursday April 08, 2004 @03:42PM (#8807278)
    Does my speculation about the RIAA's involvement in the creation of an MP3 trojan put me in the tin foil hat crowd?
    • Re:Conspiracy? (Score:3, Informative)

      by KingOfBLASH ( 620432 )

      No. The RIAA had a widely publicized program where they hired programers/crackers to create bots to find MP3s (and report them -- there was a slashdot story about a guy with a name similar to some artist who got an automatically generated cease and desist letter, asking him to stop distributing MP3s he made). The WSJ also had an article about "experiments" the RIAA was doing to break into users computers and delete MP3 files that were pirated. (Nevermind that pirated MP3 files would be indistinguishable

    • Re:Conspiracy? (Score:5, Interesting)

      by Anm ( 18575 ) on Thursday April 08, 2004 @05:51PM (#8809097)
      Does my speculation about the RIAA's involvement in the creation of an MP3 trojan put me in the tin foil hat crowd?

      Actually, my bets on on the Mac AntiVirus camp. They've been hurting a lot more recently. ;)
  • by Anonymous Coward on Thursday April 08, 2004 @03:43PM (#8807280)
    So what?

    Mac OS X can have trojans. Mac OS X can have viruses. Mac OS X can have security issues.

    It's just a lot harder to exploit all of these things on Mac OS X for numerous logistical, technical, and statistical reasons.

    It is a real concept. There is an example of the trojan, or "virus" (sic), here: http://www.scoop.se/~blgl/virus.mp3.sit

    However, it seems that this may be at best questionable, as the "proof of concept" is nothing more than a standalone CFM application that has been given a creator type of 'APPL' (recognized by Mac OS X as a Carbon application), but with the file extension '.mp3', the standard mp3 icon, and the contents of an mp3 (which Mac OS X displays to the user an mp3). While the file does indeed appear at first glance to be an ordinary mp3, what can admittedly be potentially dangerous, it is in fact an application.

    Additionally, as a CFM application, the file needs to be transported in such a way as to keep the resource fork intact, massively reducing its utility.

    I predict a future security update with disallow this behavior...

    This does not change the fact that Mac OS X is fundamentally and philosophically far more secure than alternatives.
    • It's just a lot harder to exploit all of these things on Mac OS X for numerous logistical, technical, and statistical reasons.

      They get viruses when you ship them? Maybe sealing the box a little better could help?

      ---
      Antonym, n.:
      • The opposite of the word you're trying to think of.
    • by venicebeach ( 702856 ) on Thursday April 08, 2004 @03:49PM (#8807389) Homepage Journal
      So what? Mac OS X can have trojans. Mac OS X can have viruses. Mac OS X can have security issues.

      Yes, of course we all know that OS X can have viruses, the point is that until now it basically hasn't had any. At least nothing that I've heard of or had to worry about. Now I will have to think twice about opening random mp3 files which somehow appear on my hard drive (?).
    • by Daniel_Staal ( 609844 ) <DStaal@usa.net> on Thursday April 08, 2004 @03:53PM (#8807454)
      It's news because it is the first Mac OS X specific virus/trojan in existence. No one claimed OS X was immune to them, just that they hadn't occurred yet. Now they have. That fact is news.
    • by QJB ( 704194 ) on Thursday April 08, 2004 @03:55PM (#8807481)
      The preview of the file shows no play functionality like an ordinary mp3 file but reads 'Kind: Application'. It may mislead users but it is simply spotted (with the naked eye).
  • by CkB_Cowboy ( 731756 ) * on Thursday April 08, 2004 @03:44PM (#8807298) Homepage
    .. and I just bought a G4 PowerBook too!

    That's it, I'm selling this, maybe I'll get one of those Sparc laptops instead..

    - Cowboy

  • by carpe_noctem ( 457178 ) on Thursday April 08, 2004 @03:45PM (#8807329) Homepage Journal
    I thought in unix, everything was just a file!
  • by faux plastic ( 653097 ) on Thursday April 08, 2004 @03:46PM (#8807336)
    http://groups.google.com/groups?hl=en&lr=&ie=UTF-8 &oe=UTF-8&safe=off&frame=right&th=631707378ffe9292 &seekm=blgl-5D750C.02150821032004%40news.bahnhof.s e#link6 It appears that this is merely a proof of concept virus, hence, it is utterly benign. It was not made with any malicious intent, but to demonstrate one way that OS X could be exploited. The discussion group is concerned with making OS X more secure, not less. Somehow, Intego got wind of it and blew it out of proportion, but I suppose it is theoretically possible that future viruses could be modeled on it. However I'm sure that Apple could, even more quickly, release a security update that fixes this.
  • Well, (Score:5, Insightful)

    by MuckSavage ( 658302 ) on Thursday April 08, 2004 @03:46PM (#8807341)
    I suppose I'll start to panic as soon as apple acknowledges it, rather than take the word of a company trying to sell me anti-virus software.
  • That's it! (Score:5, Funny)

    by Anonymous Coward on Thursday April 08, 2004 @03:46PM (#8807342)
    I'm switching to Windows!
  • Mac? MP3? (Score:5, Funny)

    by Deraj DeZine ( 726641 ) on Thursday April 08, 2004 @03:46PM (#8807343)
    What kind of OS X user would be caught dead using such ancient, PC-originated technology (and I use that term loosely) as an MP3?

    It's bad enough that they'll be shunned by all their iPod-wearing, dual-CPU-owning, Mac cabal member friends, but now their computer get pwned? Talk about kicking them while they're down.
  • by dartmouth05 ( 540493 ) * on Thursday April 08, 2004 @03:46PM (#8807344)
    What this article doesn't mention is how (or if) the code gets around the normal OS X restrictions requiring that one enters an administrator's password. Even if applications can be hidden, I question the amount of damage they can do... Surely nobody will enter an admin password requested by an ".mp3" file.

    Besides, this isn't a virus so much as a security flaw. Why pay $60 for software when Apple will surely release a patch soon?

    Oh, and for all the PC assholes who are currently saying "In your face, mac zealots" or whatnot--nobody claims that OS X is bulletproof--no computer system is. Nevertheless, it seems to be a lot more secure than, say, Windows, which has security problems all of the time.
  • by bughunter ( 10093 ) <(bughunter) (at) (earthlink.net)> on Thursday April 08, 2004 @03:47PM (#8807352) Journal
    ... when Apple abandoned Type and Creator file resources and went back to the old DOS kludge of simple extension typing.

    It was just a matter of time before someone used it maliciously to confuse the line between instructions and data.

    • Actually, this trojan works solely because the file extension isn't used as typing.

      The trojan is an application with its icon set to the default MP3 icon, with a .mp3 extension. The type and creator codes say it's an application, whereas the filename says its an mp3.
    • by psocccer ( 105399 ) on Thursday April 08, 2004 @04:27PM (#8807987) Homepage
      Type/creator is no better than extensions, it's just that you can't see them. So while your APPL/VND type creator is there, it's no different than just naming your file:

      file.mp3.APPL.VND

      And this is precisely how the exact same "information hiding" works in windows with .jpg.vba or whatever, since by default windows hides the extension (same thing as type/creator). And resource forks, being non-standard on most other OS's means that every time you move files around you lose meta-data that has to be rebuilt. Type/creator solves nothing, the only real solution would be using dynamic typing, but that won't work because there are so many files that are similar (look in your magic database, you'll see that stuff like Z machine files are not included because they cause too many false positives)

      Extensions really have been the best solution, though there is room for improvement.
  • by __aavhli5779 ( 690619 ) * on Thursday April 08, 2004 @03:47PM (#8807356) Journal
    Heh... Interesting that the first trojan horse/virus yet to be seen for OS X uniquely exploits the discordance between the "Classic" pre-OS X way of specifying file types (File Type/Creator metadata) and the new, inherited-from-Windows, file extension method.

    The basic gist of this trojan from what I've read so far (there is very little information aside from what Intego has on their own web site) is that it is a file with type AAPL (executable application) but with an .mp3 extension... the Finder thus displays an MP3 icon for it yet launches it as an application when the user double-clicks.

    What this basically comes down to, then, is the Finder making the wrong decision as to how to present the file to the user. Specifically that it presents it in one way, but acts upon it (when double-clicked) in the other. Whether it should first obey the deprecated file type metadata or the file extension is left to be argued about... what's certain is that it should always behave with the file the same way it presents it. I predict a bug fix for this will be in OS X shortly.
  • by PrimeWaveZ ( 513534 ) on Thursday April 08, 2004 @03:48PM (#8807369)
    I have my doubts about this trojan, as I opined on my website at destination-life.com [destination-life.com], but there is one problem: this proof of concept at this link:

    At Google Groups [google.com]

    I opened the file in BBEdit, and it appears that there is in fact executable code in the file, but it doesn't appear evident to me how the binary code would be executed if the audio file is opened inside of a music player.

    Hopefully this ends up being a hoax, or at least some more details come out soon.
    • by HeghmoH ( 13204 ) on Thursday April 08, 2004 @04:50PM (#8808324) Homepage Journal
      It's not executed when you open it in a music player, it's executed when you open it in Finder.

      I haven't looked at this trojan, but I participated in a theoretical discussion of the possibility on usenet a couple of weeks ago (interesting timing, that) and the theory isn't that strange anyway.

      The way it works is that it's actually a full-blown application. It's a Carbon CFM application, which is stored as a single file. There's a resource in the resource fork of the file which tells the OS where the actual executable code can be found; this allows the application's code to be embedded inside a larger chunk of data. The whole thing is then typed APPL with the HFS+ metadata filetype, but given a .mp3 extension; apparently the HFS+ filetype takes precedence over the file's extension on OS X.

      If you open the file from your music player, it's a real MP3 that just happens to have a bunch of junk (trojan code) in an ID3 tag. It plays, nothing else happens. If you double-click it in the Finder, though, the Finder sees that it's an application and launches it, and then you're doomed. The app can do whatever it wants at that point. Presumably one of the very first things it does is open itself with your MP3 player so as to give the appearance of functioning like a regular MP3 file, and then it can go around infecting or deleting files at will.

      This isn't a particularly dangerous trojan. Because of the dependence on HFS+ metadata and resource forks, the app can't be transported raw, it has to be encoded. So you absolutely cannot be infected by double-clicking an MP3 you got from Kazaa. You have to download an archive file, like a Stuffit archive, a disk image, a .zip file with Mac metadata extensions, an xtar archive, a MacBinary file, etc., then decode it, then double-click the MP3 inside. Since there is basically no legitimate reason to encode an MP3 with one of those archivers when transmitting it over the internet, this trojan is extremely easy to avoid; don't double-click MP3s that were extracted from Stuffit archives and similar places.

      For a successful internet worm to result from this, the recipients have to do two steps. First they would have to decompress the file that was sent to them, then they'd have to find the results and open it. Of course, we know from the example of Windows worms that enough users will go through the trouble of opening an encrypted .zip with a password supplied in the e-mail and then running the contents to enable a worm to spread, so it's not entirely implausible. I'd like to think that Mac users have a higher average intelligence when it comes to virus safety, but I'm not too confident.
  • by nanter ( 613346 ) on Thursday April 08, 2004 @03:51PM (#8807422)
    That a trojan such as this came along is irrelevant - like others have said, it can and will happen.

    What's relevant here is now that this has exposure (and we all know that /. == exposure to those who matter), how quickly will Apple respond and rectify this by issuing a patch?

    Here's wagering that they don't sit on it like M$ has been known to do, if not for any other reason that M$ has a far greater volume of virsus/trojan horses/etc. to deal with!

    -Nanter

    • Don't be silly. It's just a technique for hiding malicious data in a benign looking file. There's no reason that you couldn't do something similar with a custom icon.

      How do you expect Apple to stop people from clicking on unknown or untrusted files?

      The only "patch" that will help is one that delivers common sense through the skin (like nicotine or birth-control). Until then, trojans are here to stay.
  • Nothing new here... (Score:3, Informative)

    by Mike Thole ( 628061 ) <mthole@pDEBIANurdue.edu minus distro> on Thursday April 08, 2004 @03:52PM (#8807433) Homepage
    This is nothing new... people have been doing this for years on Windows. OS X lets you hide file extensions too, so MyMusic.mp3.app can show up as MyMusic.mp3. The article seems a little misleading at first -- the ID3 tag isn't executed, its a full fledged application that contains an MP3 file.

    It would take me about 15 minutes to write my own "trojan horse" of this nature... Don't make a big fuss over nothing.

    From the MacNN article:
    The company says that Mac OS X displays the icon of the MP3 file, with an .mp3 extension, rather than showing the file as an application, leading users to believe that they can double-click the file to listen to it. But double clicking the file launches the hidden code, which can damage or delete files on computers running Mac OS X, then iTunes to play the music contained in the file, to make users think that it is really an MP3 file . While the first versions of this Trojan horse that Intego has isolated are benign, this technique opens the door to more serious risks.
  • Ogg? (Score:5, Funny)

    by goMac2500 ( 741295 ) on Thursday April 08, 2004 @03:55PM (#8807474)
    This virus sucks unless it has ogg support. Jeez! Mac OS X is so lame..
  • by Spencerian ( 465343 ) on Thursday April 08, 2004 @04:00PM (#8807553) Homepage Journal
    Trojans aren't new in the Mac world, of course. There have been viruses made for the original Mac OS, but very, very few in comparison to, say, MS-DOS and Windows: Approximately 50 Mac OS viruses compared to 20,000+ viruses and their ilk in the Windows world.

    The method in which this trojan infects isn't new: Windows viruses often hide their true extension in the same way as this empty-payload Mac OS X trojan.

    What is significant is what a payload-laden trojan could do the today's Mac OS world. As a tech, I get to see a fair audience of Macs in use and what software they use. The very concerning part is that very few (my estimate: less than 1 in 50) Macs use ANY kind of antivirus software.

    Not that you can't find any: Aside from Intego (who make a fine firewall as well as their virus products), you can get Norton AntiVirus from Symantec and Virex from Network Associates. Yet, most of us don't own any AV software.

    That's bad for two reasons. One: While most Windows malware we Mac users may receive by mail are harmless to our Mac OS X systems, we remain Typhoid Mary-esque carriers to other PCs. Two: Our complacency in saying that "Macs don't get viruses" does not ensure that we will not experience one later.

    That "later" is now.

    Further, the "security through obscurity" protection is gone with the move to OS X. It's just a UNIX OS now, no longer a relatively-closed OS, which means there are more people who are UNIX-savvy who can create malware than before. (Fortunately that also means there are plenty of Good Guys who can spot this stuff before Apple or AV vendors are made aware.)

    While I doubt there will be lots of new Mac attacks soon, I would not wait until one shows up with a nasty payload. Buy some AV software and keep puttering along. I'm sure there's some ass out there with too much time on their hands who, like the guy who took the Word Macro "Concept" virus, added a payload and sent it on its way, who will love to make some pitiful Mac users suffer.

    Also, consider creating a regular user account, which cannot install software. In the event that you do open something with a payload on that account, hopefully OS X's permissions will stop any attempts to change any file or program except those in that account's home folder. Thank God for the UNIX permissions system.
    • How about you just not open any archived email attachments (.sit or .zip files) that you're not expecting? If the file is transferred bare, without being in a compressed archive, the resource fork is stripped, and the application is rendered inoperable. If you're downloading and opening .sit and .zip files you're not expecting, then you got what you deserved. The low marketshare of Macs practically assures that you won't really affect anyone but your own dumb self.
  • by toupsie ( 88295 ) on Thursday April 08, 2004 @04:13PM (#8807735) Homepage
    On of the many woes of being a Mac user is that we do not have the multitude of viral applications that Windows users have. Now that we have our first trojan, we are on the path of being like Windows users. However, it is my fear like most Windows applications, we are going to have to wait months and months before we get our next one...
  • by SoopahMan ( 706062 ) on Thursday April 08, 2004 @04:18PM (#8807850)
    The Trojan description is:

    1) Make a valid MP3 file
    2) Make the beginning of the file a JMP instruction (assembly code) that tells it to jump to the point in the MP3 where the ID3 tag is stored.
    3) Put a virus in the ID3 tag.

    What's to prevent this from working on Windows? It's a brilliant, and scary plan... . It would be especially effective if linked on a website, as Windows accepts MIME-types first and extensions second now.
  • by droleary ( 47999 ) on Thursday April 08, 2004 @04:20PM (#8807897) Homepage

    From my read of their PR page [intego.com] about this, it sounds like something they entirely fabricated themselves to sell their software. There is nothing in the wild and no reports on respectable security sites, just Intego saying they "isolated" something and you should buy their FUD^H^H^Hproduct. As others have pointed out, a trojan is possible on any system if you can get the user to jump through elaborate enough hoops. So the next time you download an unknown MP3 (or whatever) file with an intact resource fork from an anonymous source and give it executable status so you can double-click it instead of just adding it to your iTunes library (or playing it in Finder with a single click in column view), be glad you also shelled out money to Intego so that you are protected from your own stupid and unnecessary actions! That it's come to this shows just how hard it is for anti-virus types to make money on the Mac.

  • Use the Forks, Luke! (Score:3, Informative)

    by frankie ( 91710 ) on Thursday April 08, 2004 @04:46PM (#8808260) Journal
    It's cute that they wrapped this app with a valid mp3 file, but also demonstrates the classic weakness of internet trojans for Mac. The mp3 is in the data fork, the trojan is in the resource fork, and that's a big hurdle for propagation.

    If you throw virus.mp3 into your favorite p2p sharing system (or a web site, or most sharing methods other than AFP) the downloader will only get the data fork. That's why they had to put it in a .SIT archive first. Now you have to include code to rearchive the trojan before passing it on.

    To do self-propagation right, go for pure data fork. Maybe AppleScript. A simple version would just read from AddressBook.app and spew to Mail.app. Bonus points if you detect/use other email clients too, including OS 8/9.

  • by Wingsy ( 761354 ) on Thursday April 08, 2004 @05:19PM (#8808749)
    I downloaded this sample virus and tried to open it, but Panther told me I didn't have permission to open it. So, unless you're logged as admin it looks like it ain't gonna work.
  • by santiago ( 42242 ) on Thursday April 08, 2004 @05:24PM (#8808811)
    The file is a CFM application. As others have pointed out, this means that it has a resource fork which it needs in order to be able to run. Thus, it must be downloaded as a compressed file. If the resource fork is stripped, it is harmless, as the payload will never be executed.

    Its name ends in ".mp3", and the included icon is copied from an iTunes MP3 file, but its type code is APPL, an application. The data fork is a valid MP3 with PowerPC executable code inside the ID3 tags. When given to iTunes or another MP3 player, it simply plays the included sounds without executing code. When double-clicked on from the Finder, the surrounding bits of MP3 file appear to be ignored and the code is executed. The payload for the proof-of-concept displays a dialog box, then tells iTunes to play the file itself, presumably via AppleScript.

    When double-clicked, it shows up in the dock as an application, though this could be suppressed in an actual hostile trojan just like many utility programs do. In the Finder, if one is using column view, it is identified as an Application instead of an MP3 File, and its icon is shown instead of a QuickTime-style playback bar for previewing the contents.

    In terms of an actual exploit, the only thing going on that is even possibly questionable at an OS level is the presence of other stuff in the data fork before the Joy!peffpwpc tag. I am not certain if this is allowed in the definition of what a PEF executable is supposed to look like. Aside from that, there is nothing else that is tricking the OS into doing something it shouldn't do, only legally included information that is deceptive to a user who is not looking carefully at things.
  • by acoustiq ( 543261 ) <acoustiq@NoSPAm.softhome.net> on Thursday April 08, 2004 @05:38PM (#8808972) Homepage
    A quick Google search brings up a topic I remember from years ago:
    BeOS virus ? Something to keep you awake at night... [google.com]
    So if someone wanted to activate some malicious code on a BeOS machine it seems to me that an easy way to do it would be to bulk mail a file called "funnypic.jpg" with its attribute set to executable. That way as soon as the hapless recipient clicked on the file the code would run.
    BeOS could also set arbitrary icons for files to disguise their real types. This problem is nothing new.
  • LaserJet 1012 (Score:4, Insightful)

    by Graymalkin ( 13732 ) * on Thursday April 08, 2004 @05:39PM (#8808983)
    Process to catch execute a worm of this sort:
    1. Download file with a name like Yeah-Usher.mp3.sit with your favorite downloader.
    2. Decompress said StuffIt file. If you use Safari and have "Open "safe" files after download" or use Camino and have "Automatically open downloaded files" checked you can skip this step
    3. Open up the file in attempt to view/listen to it
    4. Suffer ill effects of worm
    I'm not too worried even if a Security Update isn't released to fix the problem. I suppose a worm of this sort will affect the sort of people that open attachments from strangers and type in their administrators passwords despite warnings against such actions. For them there isn't much you can do except take their computer away.
  • by JeffTL ( 667728 ) on Thursday April 08, 2004 @06:03PM (#8809199)
    On Windows we had Trojans of this level of complexity -- really little more complex or interesting than distributing an AOL password phisher as porn and/or a game -- ten years ago. This can effect anything from Palm OS up to a mainframe. It'd be something to be scared about if a worm came out for OS X that can infect without any user action.
  • by amdg ( 614020 ) <amdg&mac,com> on Thursday April 08, 2004 @07:30PM (#8810163) Homepage

    The linked article (and most coverage of this trojan) is very misleading. This trojan does not delete files, propagate itself, or infect other files. The press release from Intego just says that a trojan like this could do those things. Read the press release for yourself.

    Intego Press Release [intego.com]

    The important thing to realize here is that Mac OS X, while very secure, is not perfect. And no matter what OS you are using, you should be very careful what you double click! Let's hope Apple nails this quickly!

Our OS who art in CPU, UNIX be thy name. Thy programs run, thy syscalls done, In kernel as it is in user!

Working...