Slashdot Mirror


Self-Destructing Virus Kills Off PCs

mpicpp sends word about particularly bad virus making the rounds, with this snippet from the BBC: "A computer virus that tries to avoid detection by making the machine it infects unusable has been found. If Rombertik's evasion techniques are triggered, it deletes key files on a computer, making it constantly restart. Analysts said Rombertik was 'unique' among malware samples for resisting capture so aggressively. On Windows machines where it goes unnoticed, the malware steals login data and other confidential information. Rombertik typically infected a vulnerable machine after a booby-trapped attachment on a phishing message had been opened, security researchers Ben Baker and Alex Chiu, from Cisco, said in a blogpost. Some of the messages Rombertik travels with pose as business inquiry letters from Microsoft. The malware 'indiscriminately' stole data entered by victims on any website, the researchers said. And it got even nastier when it spotted someone was trying to understand how it worked. 'Rombertik is unique in that it actively attempts to destroy the computer if it detects certain attributes associated with malware analysis,' the researchers said."

65 of 107 comments (clear)

  1. You mean, ensures detection by penguinoid · · Score: 2, Insightful

    A virus that evades detection is supposed to have no noticeable effects, not obvious ones like rebooting. And how well does something on your email attachment really "resist capture"?

    --
    Don't waste your vote! Vote for whoever you want, unless you live in a swing state it won't matter anyways
    1. Re:You mean, ensures detection by gstoddart · · Score: 1, Interesting

      Honestly though, a borked Windows box often just gets re-imaged because people aren't all that surprised by one which has gone flaky.

      So, you know your machine is having problems, but that doesn't mean you know you have malware.

      And, as TFA says:

      The code replacing the MBR makes the machine print out a message mocking attempts to analyse it.

      Restoring a PC with its MBR deleted involves reinstalling Windows, which could mean important data is lost.

      Basically it sounds like there's not much left to look at.

      --
      Lost at C:>. Found at C.
    2. Re:You mean, ensures detection by cheater512 · · Score: 1

      It isn't about trying to hide the malware, it is very obvious that it is there.

      It is about thwarting any further analysis, or at least making it a pain in the butt.
      So you know for a fact you've found a bit of malware, but as soon as you probe it to find it's secrets it kills its self.

    3. Re:You mean, ensures detection by wisnoskij · · Score: 1

      More like ensures self-destruction. You kill the host, and you die. The virus might as well have been cleaned being on an OS that no longer boots properly.

      --
      Troll is not a replacement for I disagree.
    4. Re:You mean, ensures detection by BoogieChile · · Score: 3, Insightful

      No, it just means that Windows can't boot. Mount it on another machine and all the data is still there, ready to be analysed

    5. Re:You mean, ensures detection by norpy · · Score: 1

      The MBR is trivially easy to recreate, you can even do it from a windows install disk without installing windows.

      This sounds like some high school student prank.

    6. Re:You mean, ensures detection by Mashiki · · Score: 1

      The article is terrible. Bootrec /FIXMBR to the rescue.

      --
      Om, nomnomnom...
    7. Re:You mean, ensures detection by gstoddart · · Score: 4, Interesting

      Sure, but by which point you're doing much more involved forensics and hunting this down.

      In many companies, a misbehaving computer is just re-imaged.

      We used to have a receptionist who put so much crap on her PC that every couple of months when she decided she'd broken it enough, they'd just re-image it.

      Why nobody ever told her to stop putting that crap on in the first place I'll never understand.

      In that kind of scenario, nobody would even know she had any specific malware or what it did.

      --
      Lost at C:>. Found at C.
    8. Re:You mean, ensures detection by un1nsp1red · · Score: 5, Insightful

      It sounds like the receptionist is the malicious part of this scenario.

    9. Re:You mean, ensures detection by MouseTheLuckyDog · · Score: 1

      The Linux TestDisk utility will scan your hd and make an attempt to repair your HD.

      Most people I know, when they see the missing MBR call a techie friend.

    10. Re:You mean, ensures detection by sjames · · Score: 1

      You could at least try to read the entire summary.

    11. Re:You mean, ensures detection by rtb61 · · Score: 2

      Except of course altering bios boot queue and shifting it to USB and booting say an Ubuntu image to fix and clear the hard disk drive. So still pretty much targeted at amateurs. Infected computer, once discovered, immediately reboot from a secure stable OS image on a thumb drive, Linux preferable as way to expensive to pay for a second copy of windows just for emergency boots. Then have a good hard look at what is going on with regard to that OS image on the hard disk drive, what files are where and, what they actually are. That lesson was learnt many years ago, getting caught deleting bad stuff only to have it reappear on reboot was to be expected. So normal tactic was to have a non aggressive look around, see what protective software was actually doing and based upon that do a reboot to CD and fix the problems on the hard disk drive, with thumb secure response and repair thumb drives properly set up, the fix is much easier now.

      --
      Chaos - everything, everywhere, everywhen
    12. Re:You mean, ensures detection by steelfood · · Score: 4, Funny

      Sounds to me just like the viruses of the 80's and 90's, pre-internet days. Back then, it wasn't about stealing passwords or holding data for ransom. It was about causing mayhem, and wiping a computer some time after infection, or otherwise damaging the computer's ability to operate normally was the norm (until Windows 95 came along and called it a feature).

      It's not just a virus. It's a retrovirus.

      *ducks*

      --
      "If a nation expects to be ignorant and free in a state of civilization, it expects what never was and never will be."
    13. Re:You mean, ensures detection by mysidia · · Score: 1

      FIXMBR only works if the bootcode is wrong or missing. It doesn't help if the entire MBR has been cleared, since the disk's partition table is also stored in that sector.

    14. Re:You mean, ensures detection by mysidia · · Score: 1

      So you know for a fact you've found a bit of malware, but as soon as you probe it to find it's secrets it kills its self.

      This is not something that would thwart sandbox analysis, however...

      In fact... as soon as the software does something, you know that there is actually malicious software, then you can in a single click roll it back, skip the instruction, and run again!

      Doing things aids analysis..... it's software that detects an analysis environment and then silently changes behavior to conceal malicious operation; that is more challenging to begin to analyze, Or at least to determine the answer to one of the most important questions: Is the file malicious?

      If the MBR gets overwritten by it, then you can immediately be certain that it is malicious, and with the obvious messaging, you can be pretty confident that it is a response to detecting a debug environment.

    15. Re:You mean, ensures detection by tlhIngan · · Score: 3, Interesting

      FIXMBR only works if the bootcode is wrong or missing. It doesn't help if the entire MBR has been cleared, since the disk's partition table is also stored in that sector.

      It's curious why the virus would clear the MBR - if you have a large drive (> 2TB) or Windows 8, your hard drive uses GPT and not MBR. Sure a GPT disk has an MBR (called a "protective MBR") that basically blocks out the GPT partitions, but that's to prevent existing partitioning tools from screwing up the GPT partitions as they'll see a fully partitioned disk.

      If you have GPT, an MBR wipe out means absolutely squat - your partitioner might complain that the protective MBR is missing, but that's trivial to recreate since it basically covers the entire disk (or the first 2TB, the maximum MBR can cover).

    16. Re:You mean, ensures detection by sg_oneill · · Score: 1

      Oh god yeah. There where some nasties back then. I still remember one that would at a random time write junk to the bios effectively permabricking the computer.

      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    17. Re:You mean, ensures detection by l0ungeb0y · · Score: 2

      Damn, that receptionist must have been seriously hot

    18. Re: You mean, ensures detection by Anonymous Coward · · Score: 4, Funny

      Yeah, he was.

    19. Re:You mean, ensures detection by someone1234 · · Score: 1

      I don't think any expert antivirus writer would be delayed by this. This sounds more like simple dickery.

      --
      Patents Drive Free Software as Hurricanes Drive Construction Industry
    20. Re:You mean, ensures detection by Waccoon · · Score: 3, Insightful

      Yup, my Amiga days were the first thing to come to mind.

      Upon reading the headline, my first thought was that the virus was wiping out the firmware, which really kills most devices as hardly anything has a ROM backup. Overwriting system files? Yawn.

    21. Re:You mean, ensures detection by Anonymous Coward · · Score: 1

      I lived through the early times of computing and Windows 95 was a lot more stable for me than Windows 3.1, especially when doing the things that computers were most commonly used for in those days: playing games and typing documents. I dreaded the General Protection Fault.

      In my memory, DOS was more stable, but I'd still prefer 3.1. In DOS you needed to quit the current application in order to consult data in a file the current application couldn't read, which was frankly as annoying, and I spent countless hours editing irritating batch files just trying to get some recalcitrant program to work.

    22. Re: You mean, ensures detection by ArsenneLupin · · Score: 2

      We used to have a receptionist who put so much crap on her PC

      Damn, that receptionist must have been seriously hot

      Yeah, he was.

      :-)

      Apart from that, female sysadmins (or company owners) do exist...

    23. Re:You mean, ensures detection by ArsenneLupin · · Score: 4, Interesting

      This sounds like some high school student prank.

      Speaking of high-school pranks. One funny MBR-related thing we did back in the day was creating a loop in the chain of logical partitions (the MBR can only define 4 primary partitions. If you want more than 4 partitions, you created an extended partition which contains a linked list of logical partitions. And we made this linked list loop back to its beginning).

      Windows (or DOS) versions back in the day were so buggy that they didn't notice the loop, and kept scanning, and scanning, and scanning until they reached the end of the list (which happened never, because it was a loop).

      Result: unbootable machine. Even from a floppy. Because the DOS on the floppy was also doing the inventory of all storage media attached to the machine and stumbled upon the same partition loop. And if you removed the (internal) hard disk, well, then you couldn't obviously reinstall Windows on it.

      The only fix was to boot Linux from a floppy, and remove the loop from there. However, back in the day Linux was still obscure enough that the "powers that be" didn't know about this fix...

    24. Re:You mean, ensures detection by hairyfeet · · Score: 1

      I take it they never heard of the "Fix MBR" command?

      That said any PC shop worth its salt will just pull the drive, try to save any personal data by mounting it as a data drive, then just reinstall the system. Since all this does is wipe MBR its really not a threat, not like TFA makes it sound which is that it bricked PCs.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    25. Re:You mean, ensures detection by Mashiki · · Score: 1

      Of course we already know that this virii/trojan/whatever you want to call it isn't messing around with the partition table, so your point is moot. Since fixmbr can rebuild even a ruined boot sector or bad boot code, that solves the majority of the issue in question. Deleting the partition table however would cause more of an issue for most people, since most people have no idea how to rebuild a partition table manually.

      --
      Om, nomnomnom...
    26. Re: You mean, ensures detection by Flavianoep · · Score: 1

      We used to have a receptionist who put so much crap on her PC

      Damn, that receptionist must have been seriously hot

      Yeah, he was.

      :-)

      Apart from that, female sysadmins (or company owners) do exist...

      Yeah, they do exist, but women are less susceptible to hormones, so it's more likely that if the receptionist were a male, the sysadmins (or company owners) would be gay.

      --
      Linux is for people who don't mind RTFM.
    27. Re: You mean, ensures detection by alex67500 · · Score: 1

      ACs get less upmods than real accounts... but you're right, it made me laugh :-)

    28. Re:You mean, ensures detection by LordLimecat · · Score: 2

      An IT department equipped to do reimaging is probably equipped with at least one IT guy dedicated to security who would want to find out what happened and how to prevent it.

    29. Re:You mean, ensures detection by Wraithlyn · · Score: 1

      > Windows (or DOS) versions back in the day were so buggy that they didn't notice the loop

      That's your idea of "buggy"? Intentional sabotage causing issues?

      That's rather like saying your car is buggy for not working when you disconnect the sparkplugs.

      --
      "Mind, as manifested by the capacity to make choices, is to some extent present in every electron." -Freeman Dyson
    30. Re:You mean, ensures detection by drinkypoo · · Score: 2

      That's your idea of "buggy"? Intentional sabotage causing issues?

      Rule 1: Always check your inputs.

      Rule 2: It comes after rule 1.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    31. Re: You mean, ensures detection by Anonymous Coward · · Score: 1

      Except for the fact that the grandparent specifically mentioned that this was a female receptionist five fucking times, numbnuts!

      SJW Epic Fail! DIAF!

    32. Re:You mean, ensures detection by tlhIngan · · Score: 3, Informative

      Of course we already know that this virii/trojan/whatever you want to call it isn't messing around with the partition table, so your point is moot. Since fixmbr can rebuild even a ruined boot sector or bad boot code, that solves the majority of the issue in question. Deleting the partition table however would cause more of an issue for most people, since most people have no idea how to rebuild a partition table manually.

      From the Cisco link, it does wipe the partition table. In this case, MBR doesn't mean just initial boot code, but the whole boot sector of the system, which contains the partition table as well. (Probably one of those legacy PC things we're still living with... most other sane systems generally move the boot code or the partition table elsewhere.).

      Basically it rewrites sector 0.

      Which on a modern Windows system, does squat since we're using EFI boot which no longer does the sector chainboot the old BIOS does. Plus, modern systems don't use MBR partitioning, they use GPT, which while having an MBR, the MBR is marked as protective so MBR aware tools won't try to inadvertently create a MBR partition table over the GPT one.

      GPT tools can reasily rebuild the protective MBR without even reading the GPT since the protective MBR partition is fixed type, and spans the whole disk (or first 2TB, maxing out MBR).

    33. Re:You mean, ensures detection by slashmydots · · Score: 1

      I agree. Analyze the virus without running it. Let's see it defend itself then.

    34. Re:You mean, ensures detection by Anonymous Coward · · Score: 1

      In most versions of Windows, a disagreement between the MBR and the GPT results in the MBR being used instead.

    35. Re:You mean, ensures detection by Hamsterdan · · Score: 1

      Tchernobyl? learned how to hot-flash a BIOS thanks to that one...

      --
      I've got better things to do tonight than die.
    36. Re:You mean, ensures detection by Triklyn · · Score: 1

      no simple about it. it sounds like monumental, epic dickery.

    37. Re: You mean, ensures detection by Flavianoep · · Score: 1

      The fedora is strong on this one.

      No, I don't use Fedora. I've tried some times, but I've been choosing Mandrake (or its successors) since 2005, and now I use Mageia.

      --
      Linux is for people who don't mind RTFM.
    38. Re:You mean, ensures detection by Maritz · · Score: 1

      Why nobody ever told her to stop putting that crap on in the first place I'll never understand.

      If only there were some way of stopping people from installing shit on their work computers. ;)

      --
      I do not want your cheap brainburning drugs. They are useless for work. And I am a working man today.
    39. Re: You mean, ensures detection by RockDoctor · · Score: 1
      So the hot female receptionist had the hot female sysadmin sucking up to her ( I chose my words carefully) by repairing her computer instead of caning her pert little behind (I choose, etc) and telling her she's a naughty girl and to never do that again.

      Perfectly reasonable scenario. I'm sure I've seen it in some of those "training videos".

      --
      Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
    40. Re:You mean, ensures detection by Agripa · · Score: 1

      That is pretty evil.

      Being a hardware guy, I would have tried either pinning one of the ATA I/O bits to corrupt the data during enumeration or disabling the ATA interface until after DOS is booted. Back then I had an ISA ATA interface card which was just discrete logic bus transceivers, buffers, and some simple decoding logic which could do either easily. I used it for debugging ATA interfaces.

      The ATA interface was originally a buffered version of the ISA bus with some decoding. You can build one with a few TTL logic ICs.

  2. Virtual machine template by Kobun · · Score: 2

    This seems like it would be incredibly simple to analyze the second time around. Offline backup into a VM and snapshotting would render the auto-destruct very educational.

    1. Re:Virtual machine template by ArsenneLupin · · Score: 1

      Couldn't you patch the VM software to hide the VM API's which make it recognizable as such?

  3. This was foretold... by damn_registrars · · Score: 4, Funny
    --
    Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
  4. "Kills Off PCs" -- Um, no it doesn't. by Anonymous Coward · · Score: 1

    Did the submitter even bother to read the article?? It can effect a *very* narrow range of Windows PCs, all of which can be restored by replacing any modified files.

    1. Re:"Kills Off PCs" -- Um, no it doesn't. by Bomarc · · Score: 1

      Did the submitter even bother to read the article??

      Actually he did. The article has the quote "kill off"... (I was going to post the same thing when the article was in Firehose -- but decided not to) however if you read the article the PC isn't killed (reality nothing is) just the MBR is nuked. Anyone ever hear of "backup" ?

      The only thing "exciting" about this one is the detection that is being removed ... then it removed the MBR. But there is no elaboration on this action.

    2. Re:"Kills Off PCs" -- Um, no it doesn't. by BoogieChile · · Score: 1

      > It first attempts to overwrite the Master Boot Record (MBR) of PhysicalDisk0, which renders the computer inoperable. If the malware does not have permissions to overwrite the MBR, it will instead destroy all files in the user’s home folder (e.g. C:\Documents and Settings\Administrator\) by encrypting each file with a randomly generated RC4 key. After the MBR is overwritten, or the home folder has been encrypted, the computer is restarted. The MBR also contains information about the disk partitions. The altered MBR overwrites the bytes for these partitions with Null bytes, making it even more difficult to recover data from the sabotaged hard drive.

      I know somebody around here who didn't even read the article....

    3. Re:"Kills Off PCs" -- Um, no it doesn't. by ArsenneLupin · · Score: 1

      The MBR also contains information about the disk partitions. The altered MBR overwrites the bytes for these partitions with Null bytes, making it even more difficult to recover data from the sabotaged hard drive.

      Nowadays, most drives only contain a single partition (especially those of unsophisticated users), so even that is easy to recover. Or else, look for signatures of partition boot sector in the likely places (aligned on a cylinder start).

  5. meh by Revek · · Score: 1

    Take the drive out and scan it in a dock. Side load the drives registry and scan it. Its happened before for less capitalist reasons.
    CIH

  6. Should have gone ninja... by BoogieChile · · Score: 1

    As soon as it detects attempts to analyse it, it deletes itself completely, so the victim is left never knowing if it was really there or not.

  7. Is that all??? by EmeraldBot · · Score: 3, Interesting

    Of all the destructive things one could do, it rewrites the MBR? That's it? That's fairly easy to fix, and your data is still easily intact by copying it with a second machine.

    To be honest, a much more dangerous one would be one that sits dormant for, oh, say six months or so. In doing that, it gets itself into all of your backups (if you have any), and now you're going to have trouble separating your data from the virus. If it then activates a random amount of days (1-14) after being restored, it's not obvious which backups are infected and which ones aren't.

    Of course, this is all purely theoretical, and I highly discourage anyone from actually implementing this - it's just an idea...

    --
    "Set a man a fire, he'll be warm for the rest of the night. Set a man afire, he'll be warm for the rest of his life."
    1. Re:Is that all??? by mlts · · Score: 1

      I wouldn't be surprised to see far worse things come down the pipe, especially malware that exploited domain admin rights to compromise the entire AD forest.

      However, we have one big defense against all of this: Virtualization. Not just VM farms, but VDI (so a compromised desktop can just be rolled back to a known good snapshot almost instantly.) If the malware can't touch hardware, it can still destroy/corrupt files, but VMs have a lot more tools available for mitigating/reversing such attacks, even if it is just a simple snapshot of files taken daily which persists a week before expiring. Of course, snapshots are not backups, but they are a tool to help with RTO/RPO.

      Another defense is separation. The AD domain used for authenticating to the NetBackup server, SAN, and tape drive is completely separate than the AD forest used for day to day user work. This way, a domain or enterprise admin account that gets compromised on a user's desktop cannot be used to destroy all data on a silo, SAN, or NAS. It will still be pure hell rebuilding the AD structure if malware does use it as a propagation vector, but at least the core appliances won't be affected.

      Of course, the final defense are good backup and archival policies. For example, a backup is done daily, and is kept 7-14 days. Another backup is done weekly, kept 4-8 weeks. A monthly backup is fired off, kept 12-24 months, and a quarterly backup is kept 7-20 years on WORM media. Of course, offsite and verification policies go without saying as well. It also doesn't hurt to run a hash of stored files and cryptographically sign that on an offline machine, just as a last resort for detecting tampering.

      I have a feeling we will not just see more destructive attacks, but more subtle ones. A simple change in a purchase order can bankrupt a company. So, because this actually hurts businesses (as opposed to the previous "copy data and leave everything alone" intrusions of the past), we might see actual money spent for handling data integrity as part of enterprise security.

    2. Re:Is that all??? by rudy_wayne · · Score: 1

      So, because this actually hurts businesses . . . we might see actual money spent for handling data integrity as part of enterprise security.

      You obviously don't have any understanding of business in the real world.

    3. Re:Is that all??? by wbo · · Score: 1

      Of all the destructive things one could do, it rewrites the MBR? That's it? That's fairly easy to fix, and your data is still easily intact by copying it with a second machine.

      On top of that on modern UEFI-based systems the MBR doesn't do anything anyway (it is just there to prevent older partition tools from messing with the disk). It wouldn't surprise me at all if a variant of this appeared that attempts to wipe all copies of the partition information on GPT disks as well making it potentially more dangerous.

      Also it looks like if it can't write to the MBR, it proceeds to encrypt all files in a user's profile with a random key which I would consider to be significantly more destructive.

  8. Just a different way to be DickWare by Tablizer · · Score: 1

    How is this different than a PC with a non-closable prompt that says, "Your PC is infected. Enter your credit card number to order our cleaning software".

    I suppose it could be even worse by deleting all your files and THEN locking up.

  9. Another "news for tabloids" article. by edibobb · · Score: 4, Informative

    A computer is not "destroyed" if you have to repair the MBR or reinstall Windows. It may be a pain to do, but the computer itself is fine.

    1. Re:Another "news for tabloids" article. by ArsenneLupin · · Score: 3, Informative

      A computer is not "destroyed" if you have to repair the MBR or reinstall Windows.

      Not to mention, you don't have to re-install Windows. You can install a proper OS instead.

      ... and if your goal is to analyze the virus, install it in a VM instead, or does it detect that one as well?

    2. Re:Another "news for tabloids" article. by CAOgdin · · Score: 1

      Of course, if you make 100% off-line backups of every computer, every night, you can roll-back one or two days and be back in operation in less than an hour. BTW, this is another argument for keeping programs and data separated. I HATE "user profiles" in Windows for storing data adjacent to the O.S. We keep data elsewhere, so software can be restored without losing valuable data. (This happened just yesterday with a new software utility update that trashed the test system. We just rolled back to last-night's backup, then wrote to the vendor, and in our newsletter to clients, saying: Don't Use It!)

    3. Re:Another "news for tabloids" article. by RockDoctor · · Score: 1

      install it in a VM instead, or does it detect that one as well?

      Since TFA (more than TFS) mentions that these various attacks are in response to the virus "realising" that it is running in a "sand box" type environment, then I's expect it to detect many un-stealthed VM environments too.

      I read TFA for about 5 minutes before I came across something remotely interesting. I got it that the malware had substantial checks to make it *harder* for an investigator (virus researcher, forensics investigator after a break-in) to understand what the virus is doing, and that the virus writer wasn't particularly interested in hiding from the user, but in avoiding being analysed by specialists. Fixing an MBR - trivial. User's home directory encrypted - well whoopie-dee, as if that's going to faze a decent investigator (they'll probably put the home directory on the network and sniff to record write instructions but not necessarily carry them out). So that's a [SHRUG]. But this :

      If Rombertik detects an instance of Firefox, Chrome, or Internet Explorer,

      So, virus writers really are getting over the IE monopoly? I hadn't noticed, not having used Windows for myself for several years, and not having used IE for even longer, if at all possible to use anything else.

      --
      Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
  10. Kills PC, by making the machine unusable... by JasterBobaMereel · · Score: 2

    Does nothing to the machine at all, just attacks the operating system ...not news ...

    --
    Puteulanus fenestra mortis
    1. Re:Kills PC, by making the machine unusable... by CastrTroy · · Score: 2

      That has to be the stupidest virus on the planet. Why would you want to do this I mean, sure, you annoy somebody for a day or so, possibly make them spend money to get it fixed, but then the problem is solved. The most successful viruses are ones that nobody knows are there. You can then spread to other machines silently without anybody knowing. Then the virus gives you remote control over the machine so you can collect valuable information. If you really just want to annoy the user and break their computer, you could probably just have the virus flash the BIOS with some invalid firmware.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
  11. Not new. by Lumpy · · Score: 1

    There was one that would attempt to find the BIOS flash and write FFFF to the first 2 bytes making the computer never boot again until the flash was pulled and re-written.

    --
    Do not look at laser with remaining good eye.
  12. Destruction is in response to detection attempts by bdwoolman · · Score: 3, Informative

    This malware is very hard to detect under normal conditions. But it is outfitted with counter measures. When it detects activities that are consistent with malware detection, study and or/and removal it responds in many destructive ways. It makes it difficult for a white hat to suss it. But, no, it does not give itself away by cutting up rough. It only starts the visible signs of infection when it deems the jig is up anyway.

    There is a very good (and somewhat scary) article from The Register. on Rombertik.

    This is as nasty a piece of work as you will ever not wish to see anywhere near your equipment.

    --
    "No fear. No envy. No meanness." Liam Clancy
  13. NSA Please Help !. by hamsterz1 · · Score: 1

    Just imagine a helpful e-mail from the NSA . Dear Sir, it has come to our attention, in scanning your e-mail, that a virus, or malware is hidden in your e-mail claiming to be from Microsoft, please delete this e-mail ASAP. Sincerely The NSA. "We Spy Because We Care".

  14. Moderators... by ArsenneLupin · · Score: 1
    ... how can a comment about the article (linked to in the summary) be off-topic? Is there even something which could be more on-topic that a commentary about the article?

    (Even if it's just about a presentational aspect?)