New OS X Backdoor Malware Roping Macs Into Botnet
An anonymous reader writes New malware targeting Mac machines, opening backdoors on them and roping them into a botnet currently numbering around 17,000 zombies has been spotted. The malware, dubbed Mac.BackDoor.iWorm, targets computers running OS X and makes extensive use of encryption in its routines, Dr. Web researchers noted. What's even more interesting is that it gets the IP address of a valid command and control (C&C) server from a post on popular news site Reddit. The malware is capable of discovering what other software is installed on the machine, opening a port on it, and sending a query to a web server to acquire the addresses of the C&C servers.
There is really no information here. How does it spread? Does it spread through utter user stupidity, or is it actually dangerous? It says infected Macs are added to a botnet of 17,000 computers - is that 16,999 PCs and one Mac, or 17,000 Macs?
Viruses and malware are two different beasts altogether.
So...they get infected just like Windows does? Because at the shop the vast majority I see are either "user installs pirated shit, gets bug" and "Hey u want to see teh hot lezbos for free? Install 'Iz_not_Viruz_is_Codec.exe" so u can watch teh hot womens 4 free!" which it wouldn't surprise me is also being used for this attack....except you know replace lezbos with "oiled up muscle men" ;-)
ACs don't waste your time replying, your posts are never seen by me.
So...they get infected just like Windows does?
Just like ANY OS that accepts 3rd party software does.
Your homophobia is noted.
> There is really no information here. How does it spread?
You're using a Mac. You don't need to know *how* it works. It just works and is pretty! Cheer up!
OS9? When System 7 was out, MS-DOS was at 5.x, and Windows was at 3.1.
Before OS X, MacOS was getting pretty shaky. It had no preemptive multitasking ability (well, except for A/UX and that was a completely different animal), which meant that any program that didn't use WaitNextEvent() often would hang the box, forcing one to reach for the debug/reset switch or power off button. It did show how relatively robust HFS (not HFS+, HFS) was because it handled dirty restarts quite well.
In fact, at that era, restarts were a matter of course. If you had to get a project done, restart beforehand, restart afterwards, and maybe a restart every few hours on a prophylactic basis.
OS X was a major upgrade. It didn't just fix problems with Macs that were issues since the MultiFinder days of System 6, but added real security and user separation which previously could only be put in place by third party software and various hacks (using PBSetCatInfo() to hide folders, etc.)
It's good to note for the uninformed, though, that old MacOS is a completely different codebase from a completely different source than OS X. It's not like they went through some internal process and evolved MacOS into OS X and it's some sort of continuation. Steve Jobs left and founded NeXT computer, which sold graphical workstations with a totally new OS (NeXTStep), which was a Unix derivative in terms of design, API, etc based on a core from BSD. Later, when Steve returned to Apple, he brought NeXTStep back with him. They rebranded and rejiggered NeXTStep a bit and then started calling *that* OS X. The old Mac codebase died and was replaced; it did not evolve.