For the spycar case: Obviously other vendors are blocking the .exe files offered by spycar.
This is completely missing the point, since that does NOT protect you from other malware that performs the same actions from a different binary (or script).
So, blocking these files gives a false sense of security. Also spycar is not meant as a reference in Anti-Spyware like EICAR is for Anti-Virus, even if the name would suggest that.
Regardless of the usefulness, we may start to block these files in the future too ...
Tom, the point of eicar and spycar is that they can be used to make sure that the anti-malware systems are at least basically functioning. Therefore it's more helpful if a given system identifies the test files.
For Spycar, this is only true for desktop products, since a gateway product can't hook into registry write attempts on the individual desktops, for example.
Desktop-Anti-Spyware does not block the executable itself, it must block the actions it tries to perform on the target system.
For Spycar, this is only true for desktop products, since a gateway product can't hook into registry write attempts on the individual desktops, for example.
Desktop-Anti-Spyware does not block the executable itself, it must block the actions it tries to perform on the target system.