Ok, but where can I go for more information? Is that a generic sort of concern, or something specific? Based on user reports, automated scanning, behavior?
I see online discussion of “Nullsoft Scriptable Install System (NSIS)” as being the cause of the flag. And VirusTotal says:
Bkav ProW32.AIDetectMalware.64
CynetMalicious (score: 100)
Gridinsoft (no cloud)Trojan.Win64.Downloader.sa
Acronis (Static ML)Undetected
AhnLab-V3Undetected
AlibabaUndetected
ALYacUndetected
Antiy-AVLUndetected
ArcabitUndetected
….
ViRobotUndetected
WebrootUndetected
Avast-Mobile Unable to process file type
BitDefenderFalx Unable to process file type
Page 1 / 1
Hello @iOne
Save a Scan log and post the line that shows the infection! Go to the WSA icon near the clock and right click on it ans select “Save a Scan Log” it should be near the bottom of the log.
I don’t have any in my log but should look like this!
Call 1-866-612-4227 during the week Mon - Fri 7 AM to 5:30 PM (MDT)
Note: When submitting a Support Ticket, Please wait for a response from Support. Putting in another Support Ticket on this problem before Support responses will put your first Support Ticket at the end of the queue.
Thanks,
Hello @iOne
I contacted support and here is what they had to say!
Webroot Support (Oct 3, 2023 19:46)
RE:Is this bad or a FP?
Hello Daniel,
Thank you for providing us the file information. For this file we are keeping our determination as bad and you may allow this locally should you need it.
Regards, Zach P. The Webroot Advanced Malware Removal Team
If it means the program is collecting data and reporting it to a central sever on launch, well, yes…. that’s what it’s supposed to do. If it’s doing more than that, it’s a problem. But what “more”?
Thank you for providing us the file information. For this file we are keeping our determination as bad and you may allow this locally should you need it.
Regards, Zach P. The Webroot Advanced Malware Removal Team
Also the file when installed is much larger! Size: 14264876 bytes
That then brings in the full program. Which, by the way, is a portable EXE that’s not actually installed just dropped into a folder.
The question remains: is the installer triggering these warnings, or some actual behavior of the program?
Contact support and ask them as they would know! @DanP can you add anything here?
Thanks,
Hey everyone!
For this software you will have to just do a local allow (manual override) as stated early in this post.
For reasons as to why our Research Team will not be whitelisting this vendor’s files:
It's unsigned, It escalates privileges, it creates an executable file (exe that creates and exe), it writes executable commands to log files. We have historically reversed single hashes of this file and again it's not that we think it's overtly bad but in the age of BYOV and other supply chain attacks there just isn't enough safeguards for us to whitelist.
They will be discussing this niche of questionable software in broader org meetings so please let us know your feedback!