Please fix the issues in the exe file and provide a new wealth lab executable which addresses these security concerns.
I could not find a help email for Wealthlab and hence, posting this here.
I downloaded the Wealthlab executable. As a standard due diligence procedure, I submitted it to VirusTotal.
2 of the 68 vendors have highlighted this as Trojan.
Steps to replicate:
1. Goto virustotal.com
2. Submit the wealthlab executable file to VirusTotal for analyses.
3. Outcome is as per the image attached/below.
I could not find a help email for Wealthlab and hence, posting this here.
I downloaded the Wealthlab executable. As a standard due diligence procedure, I submitted it to VirusTotal.
2 of the 68 vendors have highlighted this as Trojan.
Steps to replicate:
1. Goto virustotal.com
2. Submit the wealthlab executable file to VirusTotal for analyses.
3. Outcome is as per the image attached/below.
Rename
It does happen when sophisticated software protection triggers a false positive - especially with third tier AV vendors. They mistakenly treat our dynamic protections as 'Trojan.Generic' by its nature. Simply disregard it or submit the file to the vendors if you care about it (which probably won't make great sense as a new build may trigger the same error).
You're on the right track: the forum is the "help email".
QUOTE:
I could not find a help email for Wealthlab and hence, posting this here.
You're on the right track: the forum is the "help email".
I see.
Most reputable AV vendors passed the installation exe - especially the likes of Avast, SentinelOne, Palo Alto Networks, Bitdefender, Kaspersky, MalwareBytes and Mcafee.
I guess you are aware that the 'dynamic protections' trigger it. Please provide details of the dynamic protections that are triggering this issue.
Most reputable AV vendors passed the installation exe - especially the likes of Avast, SentinelOne, Palo Alto Networks, Bitdefender, Kaspersky, MalwareBytes and Mcafee.
I guess you are aware that the 'dynamic protections' trigger it. Please provide details of the dynamic protections that are triggering this issue.
QUOTE:Look, as a customer you don't have to care about the ins and outs of the software protection. Providing details is out of question because this isn't a support matter anyway. Simply put, there may be traits that are misinterpreted by seldom AV engines as techniques used by some malware.
I guess you are aware that the 'dynamic protections' trigger it. Please provide details of the dynamic protections that are triggering this issue.
Your Response
Post
Edit Post
Login is required