Is WebMonitor compatible with Protectors / Crypters?

We understand that you may find it time-consuming and complex having to deal with the hassle of playing around with the complicated settings of Anti-virus or other relevant security software to whitelist your WebMonitor client.

It’s common practice that almost all tools capable of hidden remote tech are flagged as false positives by anti virus, especially tools having been established on the market for a while, including WebMonitor.
We have been fighting with false positives since the beginning of our protection and actively co-operating with Anti-virus companies too to rectify false-positive detections.

Many Antivirus software rely primarily on static engines, automatically triggering false-positive results of applications with unorthodox PE headers. Unfortunately, they don’t analyse other aspects of applications, nor their credibility. Many Antivirus software also flag applications that aren’t digitally signed as false-positive.

If you can afford to digitally sign your WebMonitor client executable with a certificate issued from a trusted CA (not self-signed), then that should be the very best solution to fight against false-positives. Most serious and major Antivirus software almost always trust digitally signed files and wont flag such as false-positives.

A protector/crypter may also help fighting against false-positives, ensuring that security software may not interfere with your application.

Technically, WebMonitor should be compatible with almost any Protector/Crypter. You should keep in mind that WebMonitor is coded in a native language, meaning it has absolutely no dependencies.

Many third party tools, such as protectors/crypters are coded in .NET, while still supporting native executables.
To ensure better compatibility, the protector/crypter should preferably be coded in a native language. It’s recommended if it has nothing to do with .NET what so ever.
However, this doesn’t mean a .NET protector/crypter won’t  work. Whether or not it works is up to the programmer of the protector/crypter, not Revcode.

Thus, our recommendation is if you really need to use a Protector/Crypter, it should preferably be fully coded/programmed in a native programming language, such as C/C++, Delphi, VB6, MASM, FASM, etc.

Note: WebMonitor does not endorse illicit intentions of using a third party applications with our applications, i.e. Protectors/Crypters, but solely for educational, research and personal purposes.
Detected violation of the terms may result in a suspension of your service(s).

Additional notes:

  • If you are using a third party tool, such as a protector/crypter with your WebMonitor client executable, then you should select the relevant checkbox during the build process in your WebMonitor panel.
  • Refunds may not be granted for requests regarding incompatibilities of third party tools, with respect to the Refund policy, paragraph 9.