The main thrust of the article is that Blink will be able to find and detect brand-new viruses by running suspect programs in a virtual machine and observing their behavior:
The Norman SandBox, Maiffret described, is a fast, stand-alone virtual machine, which tests the code of executables to see whether they’ll do interesting things, such as changing the Windows System Registry startup keys, or some very interesting things, such as connect to an IRC chat server somewhere in Russia.
Rather than scan everything all the time, however, the new Blink will scan newly discovered executables, and may perhaps rescan them if, for instance, their patterns or file size appears to have changed. But if it’s the same executable, by default, Blink will only scan it once.
Unfortunately, this approach is pretty easy for a would-be virus writer to avoid. For example, the “virus” could perform its malicious activity only if it receives user input (which it is unlikely to receive in a virtual machine but likely to receive if it pops up a window). Or the virus could check to see if it is running in a virtual machine using technology that is now readily available.
Of course, the real problem with this approach is that it’s theoretically impossible to look at a program and figure out what it’s going to do. This is just another recasting of Turing’s famous “halting problem.” Even running the program in a virtual machine won’t tell you what it’s going to do once you run it in the wild.