I could be wrong but think it was the unofficial v2.26 driver that had that trojan problem and not the v4.x evaluation driver that is needed to be able to update firmware, and as far as i remember that v2.26 driver was intended for users that wanted the small diy hardware volume hack developed by Khadas employees many pages back : )You get a nice Trojan tacked onto one of the files. Oh wait, haven't they fixed it already?