I dont think this really matter.
How do you think companies test samples? Open one-to-one in explorer?
Test Procedure
The Malware Protection Test assesses a security program’s ability to protect a system against infection by malicious files before, during or after execution. The methodology used for each product tested is as follows. Prior to execution, all the test samples are subjected to on-access and on-demand scans by the security program, with each of these being done both offline and online. Any samples that have not been detected by any of these scans are then executed on the test system, with Internet/cloud access available, to allow e.g. behavioural detection features to come into play. If a product does not prevent or reverse all the changes made by a particular malware sample within a given time period, that test case is considered to be a miss. If the user is asked to decide whether a malware sample should be allowed to run, and in the case of the worst user decision system changes are observed, the test case is rated as “user-dependent”.
www.av-comparatives.org
Then i ask to you. How we supposed to test 10124 sample? I really ask to do right.I know. However, assuming something is not the same as being right.
Why TPSC using test script? what's difference with my tool?Here is an example that shows differences with your test:
![]()
Malware Protection Test March 2025
AV-Comparatives' Consumer Malware Protection Test for March 2025 is now released!www.av-comparatives.org
This test is not a scanning test, Sorry but we have to run directly for testing. (We tried to scan and after run 1 year ago, 500-1000 viruses left by antivirus, We still cant open one to one.)Here is an example that shows differences with your test:
![]()
Malware Protection Test March 2025
AV-Comparatives' Consumer Malware Protection Test for March 2025 is now released!www.av-comparatives.org
So it would be more appropriate to change the thread title from "Testing real-time protection of antiviruses with 10.124 Sample" to "Testing post-execution protection of antiviruses with 10.124 Sample" as "real-time" protection encompasses both pre-execution (scanning) and post-execution (behavioral).This test is not a scanning test
Thank you.So it would be more appropriate to change the thread title from "Testing real-time protection of antiviruses with 10.124 Sample" to "Testing post-execution protection of antiviruses with 10.124 Sample" as "real-time" protection encompasses both pre-execution (scanning) and post-execution (behavioral).
Then i ask to you. How we supposed to test 10124 sample? I really ask to do right.
Why TPSC using test script? what's difference with my tool?
Rather unrealistic? It's completely unrealistic and will never happen in the real world. If my system was hit with 10,000 malware at once id pull the shotgun out of the closet and redecorate my wall with fine particles.You do not use Python, which can be an advantage for your tool. However, the idea of running many samples one by one in a short time by a single tool is rather an unrealistic scenario. It is hard to reliably interpret the test results in the context of in-the-wild protection. Of course, such tests may be interpreted as a "load (stress) test", as @Trident already mentioned.
.. which rather will not happen.If my system was hit with 10,000 malware at once id pull the shotgun out of the closet and redecorate my wall with fine particles.
Probably not computers are getting rather expensive to replace, not to mention the price of ammo now days... which rather will not happen.![]()
Totally agree. Running a malware test via a script would yield questionable results as it won't account for things that use Sleep functions or just plain old multi-stage malware. A malware tester MUST be very familiar with the malware used and not just be a collector.We've already said it, but bombarding an antivirus in real-time is useless, especially with tools or scripts....
If you want to execute, it's best to do what I do: execute, wait for the actions (Malware or AV) and then move on to the next one.
Testing an AV with a "horde" of malware is like testing computers by dropping them off a 10-story building. In both scenarios, you might see which one survives the initial, brutal impact, but this crude test tells you nothing about the real-world performance.I'm just a noob, far be it from me to play the arbiter of truth at MWT.com. But I am a huge fan of logic, even though I lack the skills on display at this forum.
OK I'll concede to your knowledge :"This isn't the proper way to test"... BUT
If I were testing using the horde method, and I tested 5 well known, respected AV's, and threw 50k bad actors at them all , and 2 survived. That would still seem to me, to say something about the 2 that made it through the test.
Then if those same 2, could manage a proper test, with flying colors, that would add even more evidence to the results.
OR am I missing this by a long shot?
Yes, you're exactly right. The same principle applies to zip folder on desktop execution, perhaps even more so.Totally agree. Running a malware test via a script would yield questionable results as it won't account for things that use Sleep functions or just plain old multi-stage malware. A malware tester MUST be very familiar with the malware used and not just be a collector.