Existing executables are not modified. Only created and deleted.
As the article says, it shares its engine with Forefront Endpoint Protection, an enterprise solution used by thousands of businesses world-wide. This is a once-off mistake for an otherwise stellar programme - it happens to the best of us - and isn't indicative of the entire solution.
I understand that the main upside for Chrome is the unobtrusive automatic updates. What I would like to know is what are the possible downsides. Do you or anyone else know about any discussion about that or research into that?
(By the way, another modern app that uses appdata instead of programfiles on Windows is Dropbox.)
If there was system-wide vendor neutral update mechanism, (like apt in Debian/Ubuntu, for example), I'm sure that Chrome team would use it in place of their own home-grown solution.
More importantly, they have no control over what comes in and goes out of the repositories. I doubt Google would want to deal with every single distribution personally.
We've had a few internal executable test applications get flagged(and then nuked from orbit) by Trend's virus scanner before while the compiler was finishing the linking step.
I'm guessing that it's based on something much simpler than what you describe since it's identified it specifically as Zbot.
Too bad MSE isn't open source :)
It's like the "I'm logging in as root and can change other people's files." sort of security 'flaw'.
It's always unpleasant when you get flagged by a virus scanner. Antivirus vendors basically ignore you unless enough of your customers complain to get their signature database updated. Hopefully in this case, since it's a high-profile application (Chrome), Microsoft will address the problem quickly.