Conflicker is the newest worm infecting millions of computers. Some suggest it is waiting to receive new instructions after it is downloaded.
Does it get in through emails.? What do these emails look like? If we get it, how do we remove it?
I guess not.
I think you meant Conficker not Conflicker…
According to McAfee the Risk Assessment is Low. YMMV.
It doesn’t spread via email, it gets onto machines via an unpatched Windows vulnerability - MS08-067. Microsoft has put out a patch to fix this vulnerability, so you should make sure your Windows is up to date.
Problem with this worm is that once it’s infected a computer, it can be difficult to remove. It spreads across local networks, may download other nasties onto your computer or network, and blocks access to security websites to prevent you from updating your AV.
Major AV vendors have detection for Conficker/ Downadup/ Kido, and also have dedicated removal tools.
If your computer is patched, and you have up-to-date AV, you should be fine.
It isn’t really a problem for you, because it doesn’t damage or destroy info on your computer. Instead, it takes over part of your computer, and uses it to send out SPAM emails.
Early malware damaged or erased info on your computer, and wrote sneering messages about it, because that was feeding the ego of the author. This kind of malware is all about making money for them, and so they want your computer to keep working, with you not even aware that it is infected. So generally, most people will only see a slight slowdown in their computer – most won’t even notice that.
I’m going to disagree with everyone here, as a security professional dealing with this on a daily basis. The variants exploiting this vulnerability use three attack vectors (that we know of so far), and can hose anything with weak password authentication (particularly in regard to admin$ shares). Multiple organizations have been met on sunny mornings to find large numbers of account lockouts because the vulnerability is being used to launch brute force attacks.
Patch systems for this vulnerability. We’re still waiting to see what payload deployments may (or, heck, may not) exploit it. This isn’t a good bit of fire to play with.