For the second time, Prevx is incorrectly flagging our software as "Malicious". (See the previous correspondence from 2006 for details for their past mistakes)
PrevxCSI V1.2.101.104 incorrectly flags the file,
C:\Program Files\BurnInTest5.3\bit.exe (3.98MB)
as Malicious, with the Adware.Betterinternet malware.
It appears Prevx looking at the file name (bit.exe) and not the content of the file, nor the code signing checksums, nor any malware signatures, nor even the directory in which the file is found. Which would seem to be a somewhat flawed method to detect malware, to say the least.
It means the Prevx CSI scan is fast, but hopelessly superficial.
Real malware would only need to re-name the file to avoid detection. And legitimate software gets incorrectly flagged if the name of the file co-incidentally happens to be the same as some malware.
To verify this we renamed the bit.exe to bitnew.exe, then rescanned, and detection was avoided. The way Prevx promote this CSI product will surely, in my opinion, give people a misplaced sense of security.
We have contacted Prevx on the issue, and await their response.
PrevxCSI V1.2.101.104 incorrectly flags the file,
C:\Program Files\BurnInTest5.3\bit.exe (3.98MB)
as Malicious, with the Adware.Betterinternet malware.
It appears Prevx looking at the file name (bit.exe) and not the content of the file, nor the code signing checksums, nor any malware signatures, nor even the directory in which the file is found. Which would seem to be a somewhat flawed method to detect malware, to say the least.
It means the Prevx CSI scan is fast, but hopelessly superficial.
Real malware would only need to re-name the file to avoid detection. And legitimate software gets incorrectly flagged if the name of the file co-incidentally happens to be the same as some malware.
To verify this we renamed the bit.exe to bitnew.exe, then rescanned, and detection was avoided. The way Prevx promote this CSI product will surely, in my opinion, give people a misplaced sense of security.
We have contacted Prevx on the issue, and await their response.
Comment