Nathan
Apr 13 2008, 04:57 PM
Is there any way of testing this product? I would hate to find out after the fact that I wasn't protected like I thought I was.
RubbeR DuckY
Apr 13 2008, 05:36 PM
I take it this is from the post at Wilders? Feel free to point them at the thread already started.
I am getting the trial code coordinated with the other developers as we speak.
John L. Galt
Apr 13 2008, 05:36 PM
Setting up a VM and then finding some of the malicious products in the wild would probably be your best bet, unless you have a disposable system around that you can temporarily install an OS on and test openly, with the full knowledge that you'll be formatting it and getting rid of the malicious files you encountered.
I am sure that Bruce will have a more apt (and specific) method of giving you test procedures for testing Malware.
RubbeR DuckY
Apr 13 2008, 05:39 PM
John, I think he meant protection, which we are in the process of.
John L. Galt
Apr 13 2008, 05:40 PM
ahh, testing the protection module prior to purchasing it - sorta like the trials you were discussing....
gotchya.
Nathan
Apr 13 2008, 05:56 PM
QUOTE (John L. Galt @ Apr 13 2008, 10:40 AM)

ahh, testing the protection module prior to purchasing it - sorta like the trials you were discussing....
gotchya.
Kind of. Although, sa I've said in another thread, I purchased AM yesterday. So this would be more like self-assurance.
John L. Galt
Apr 13 2008, 06:00 PM
See, I thought you had already purchased it - so in effect, what you want is to actually test it against known malware, right?
Nathan
Apr 13 2008, 06:08 PM
QUOTE (John L. Galt @ Apr 13 2008, 11:00 AM)

See, I thought you had already purchased it - so in effect, what you want is to actually test it against known malware, right?
No, not quite. I guess I'm looking for something that might not exist. AVs have the eicar test file, in many form too so that the user can see that not only was the .com file detected but so was the .zip file and the .zip2 file. Someething like that would be nice, if indeed it exists, to where AM could showoff.
RubbeR DuckY
Apr 13 2008, 06:09 PM
Aha. You can rename an executable to d.exe and place it in your root drive. That is our little testing file.
John L. Galt
Apr 13 2008, 06:12 PM
nice. Gonna create a blank d.exe file in root right now and see if MBAM goes crazy or not.
Thanks for the info, Marcin!
Tigger93
Apr 13 2008, 06:22 PM
Heh.
I just created d.exe in the Root Drive (C:\) and scanned with MalwareBytes. It didn't find anything.

Just saw post below: Nevermind.
RubbeR DuckY
Apr 13 2008, 06:22 PM
It has to be executable. A blank EXE will not execute. I suggest you just rename HJT or another program to name it d.exe
File has to be bigger than 0 bytes as well for scanner to pick it up.
John L. Galt
Apr 13 2008, 06:26 PM
good point - thanks for the tip.
I might be funny and RAR up a *nix distro, then make it self extracting and then rename it to d.exe and place it in the root - jsut to see what MBAM does....
I am starting with a 180 MB ISO....wish me luck
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.