Everything is GPL.
Tabrix was never detected by VAC when it had a binary release, but I do not know if the protection against string scanning has any effect. I hope it does, but note that it can be countered if VAC updates its detection methods. Currently it returns 0 for any call to VirtualQuery inside the tabrix address space, but since even unallocated memory returns the dwLength parameter this is easily seen as an anomaly by VAC. However I doubt they will ban for this since they have too many compatibility concerns.
Tabrix has two methods to hide from module scanning. First, the method that is used is to fake the moduel checksum of a legitimate application (mirc 6.16, included in the zip). If you don't want this, you can alter the source a little (uncomment a definition and change the loader) so that it simply removes itself from the module list.


Reply With Quote




