detecting test files
Recently, i came across a set of files that were only flagged by one of the av products as being possibly malicious, specially as a trojan.
The sandbox output from the above tools didn't show anything malicious in the executables, even with my low level of assembly language knowledge.
I also used VirusTotal and Jotti's malware Scan to get the scanning results from scanners that i do not use, and the results were the same. Only one of the scanner sets (the same one that triggered my initial analysis) on both sites flagged the files.
After doing these analysis, and it was truly a "DUH" moment, i re-examined the scanner log file.
Next to the flag of trojan, was an additional note of testfile. In the log, it was shown like (format changed somewhat below):
xxx.exe - a possible trojan--testfile
This led me to switch my train of thought. Assuming that these were indeed correct flags by this one single product, could these files be created to show that the product can detect the set of files, and that the product (at least its detection) works? Think of it as a scanner's own version of the Eicar test file.
I have not verified whether these are indeed files created for this purpose, but assuming that they are, what do this set of file truly represent? Probably in the hands of the marketing folks of that product, it could be used as a demonstration of how good the product is, no matter how one-sided it is.
Would these files be eventually detected by other antimalware products? Why would they do so? If they do not, would that just add ammunition to this company's salesforce?
In the hands of the uninformed, would the testing results be skewed unfairly to one product vs the others?
Don't we have enough confusion already?