Skip to main content
added 20 characters in body
Source Link
Rory Alsop
  • 61.7k
  • 12
  • 120
  • 325

According to Symantec's write up "it also infects .exe and .scr files in folders containing [RANDOM CHARACTERS].t". What if one of the .exe/.src files is run on the same computer - then all the same files would be infected again and eventually would all be corrupted, or is there a check against this?

If one of those infected files were manually transferred to a new computer and run, that computer will now be compromised?

Reguarding the fact "the worm ends security-related processes, if one of the following words is included in the window title: [lengthy list follows]" how does an AV defend against this? How is removal possible if each time a program starts it's knocked out?

  1. What if one of the .exe/.src files is run on the same computer - then all the same files would be infected again and eventually would all be corrupted, or is there a check against this?

  2. If one of those infected files were manually transferred to a new computer and run, that computer will now be compromised?

  3. Regarding the fact "the worm ends security-related processes, if one of the following words is included in the window title: [lengthy list follows]" how does an AV defend against this? (3a) How is removal possible if each time a program starts it's knocked out?

According to Symantec's write up "it also infects .exe and .scr files in folders containing [RANDOM CHARACTERS].t". What if one of the .exe/.src files is run on the same computer - then all the same files would be infected again and eventually would all be corrupted, or is there a check against this?

If one of those infected files were manually transferred to a new computer and run, that computer will now be compromised?

Reguarding the fact "the worm ends security-related processes, if one of the following words is included in the window title: [lengthy list follows]" how does an AV defend against this? How is removal possible if each time a program starts it's knocked out?

According to Symantec's write up "it also infects .exe and .scr files in folders containing [RANDOM CHARACTERS].t".

  1. What if one of the .exe/.src files is run on the same computer - then all the same files would be infected again and eventually would all be corrupted, or is there a check against this?

  2. If one of those infected files were manually transferred to a new computer and run, that computer will now be compromised?

  3. Regarding the fact "the worm ends security-related processes, if one of the following words is included in the window title: [lengthy list follows]" how does an AV defend against this? (3a) How is removal possible if each time a program starts it's knocked out?

edited title
Link
Rory Alsop
  • 61.7k
  • 12
  • 120
  • 325

Two questinos reguardingquestions regarding Mixor worm

Source Link
Celeritas
  • 10.2k
  • 24
  • 88
  • 150

Two questinos reguarding Mixor worm

According to Symantec's write up "it also infects .exe and .scr files in folders containing [RANDOM CHARACTERS].t". What if one of the .exe/.src files is run on the same computer - then all the same files would be infected again and eventually would all be corrupted, or is there a check against this?

If one of those infected files were manually transferred to a new computer and run, that computer will now be compromised?

Reguarding the fact "the worm ends security-related processes, if one of the following words is included in the window title: [lengthy list follows]" how does an AV defend against this? How is removal possible if each time a program starts it's knocked out?