Old Nick > wrote in
:

> I "trialled" one of these attachments. I ran a latest update (that
> day's) virus checker over it (CA's AV)...clean. Then I checked it with
> updated malware checkers...clean. I had a firewall running. I started
> the trojan. It broke straight through the firewall, even wehn
> completely blocked, and although the firewall could "see" the trojan
> programme, it simply generated no traffic. I had all sorts of reasons
> and excuses from the makers of the firewall.............ecepe that
> another firewall _did_ catch the trojan every time.
>
> In the end I used an online virus ID service, and it showed up the
> malware in the exe file.
>
> And this was after these things had been floating around for a week.
>
> It appears there are two hand jobs here. The one by the perpetrators
> of this shit, and the other by the purveyors of semi-capable
> "protection".

Which "firewall" were you running?

YG