I have seen many threads regarding whether or not VirusCheckMate is distributing or not. Before deploying out in the field I would like to get the opinion of the members on the proposed testing methodology.
1) Using a base file as a template I will make it rather fud it will or should look rather new, a few detections are infact OKAY we just have to note them.
a) Upload the full file to VirusCheckMate and note any detections as well as identified signatures
2) Divide each section of the file for example .text ..etc and place into new executables which we can upload after a set amount of time from initial upload to VirusCheckMate ( enough time for the AV companies to have time to get their matching if there is distribution)
3) Compare results between VirusCheckMate (having the full file) and NoDistribute/VirusTotal (only sections of the file) noting differences in the number of detections as well as identified signatures.
The reason we upload several small files is so then no one AV maker should have a full payload unless VirusCheckMate does distribute.
Also using common methods such as hyperion or PE Scrambler or common crypters will not be used on any of the files I would hate to have detections due to usage of a crypter. Also if there is distribution well sending out a crypted file isn't the best move. So all obfuscation will be done manually.
Reason for waiting : To allow AV makers to possibly get a signature as well as distribute the file amongst themselves. Also without a set time frame no one will stop all business till such testing is over.
Tools to be used:
---------------------------------
readpe
objdump
objcopy
ghex
file
pedump
pefile
Ensuring file integrity is important and I propose that the file will let us know of any issues with our headers so each file is properly identified as an executable. Second the sections must be the correct size/offset/flags...etc. Using objcopy and objdump we should be able to verify all of this information also we must make sure that each section's hash values match up, using pefile.
I am looking for possible flaws in this testing methodology as to have accurate information and results, which will be published here in full after completion.
1) Using a base file as a template I will make it rather fud it will or should look rather new, a few detections are infact OKAY we just have to note them.
a) Upload the full file to VirusCheckMate and note any detections as well as identified signatures
2) Divide each section of the file for example .text ..etc and place into new executables which we can upload after a set amount of time from initial upload to VirusCheckMate ( enough time for the AV companies to have time to get their matching if there is distribution)
3) Compare results between VirusCheckMate (having the full file) and NoDistribute/VirusTotal (only sections of the file) noting differences in the number of detections as well as identified signatures.
The reason we upload several small files is so then no one AV maker should have a full payload unless VirusCheckMate does distribute.
Also using common methods such as hyperion or PE Scrambler or common crypters will not be used on any of the files I would hate to have detections due to usage of a crypter. Also if there is distribution well sending out a crypted file isn't the best move. So all obfuscation will be done manually.
Reason for waiting : To allow AV makers to possibly get a signature as well as distribute the file amongst themselves. Also without a set time frame no one will stop all business till such testing is over.
Tools to be used:
---------------------------------
readpe
objdump
objcopy
ghex
file
pedump
pefile
Ensuring file integrity is important and I propose that the file will let us know of any issues with our headers so each file is properly identified as an executable. Second the sections must be the correct size/offset/flags...etc. Using objcopy and objdump we should be able to verify all of this information also we must make sure that each section's hash values match up, using pefile.
I am looking for possible flaws in this testing methodology as to have accurate information and results, which will be published here in full after completion.


![[Image: mDF7ZCO.png]](https://i.imgur.com/mDF7ZCO.png)

