By package I was referring to the latest MSE virus definition update. I'd first tried MSE against its then-latest definition file as of when I posted up thread, and at that point, despite the trojan being around awhile, MSE did not detect it.
But neither did the latest from AVG or Comodo. I followed the same procedure with both: installed their latest version; brought each up to date with the latest virus definitions; then checked the zip file and then the contents of the zip file. Neither AVG, Comodo, or MSE detected the file or file within the zip file, and none worked with my browser to block download/save.
After checking out the latest from both Comodo and AVG, I decided to update again MSE's virus definition files (if any updates had yet been published). Then and only then did MSE detect the virus and at that point it detected it even as it was trying to be saved as a download from Chrome.
Chrome itself believed the link was suspect all along and cautioned against download, but it did not know it to be virus laden.
The particular virus is: Win32/Zbot, a password grabber / key logger. It's not a new trojan but must have a slightly different signature this time around.
PWS:Win32/Zbot
Incidentally the virus link was part of a fairly convincing email purporting to be from a service called eFax. It was well done, without the usual grammar and spelling errors that often come along with spam and some trojan-laden emails. It had links to a legitimate service, as well as a link which looked to be to the service but of course was not. The .SCR file would look convincing to someone not experienced - it presented a PDF icon within Windows Explorer.
As of this writing the virus file link is still up there on the internet but I'm hesitant to link to it here for safety's sake. It's hosted on a server in Argentina on a network operated by one of that country's cable TV operators. The email itself originated from servers in France. I report these things to the network supplier of the originating email and of the destination target via my account at Spamcop; at the time of the email dispatch it wasn't listed in the real time blackhole DNS lists that my mail servers use as part of a weighted algorithm to reject mail before it enters our systems. By now the IP's involved will have been flagged but the people behind these schemes can always find another open mail relay or infected client computer to send their crap through.