-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Server 2019 sees nc.exe as a virus #6
Comments
As per 2-spyware.com and Norton "nc.exe is a process which is responsible for writing to and reading from network connections by NetCat. This Computer network utility is using Transmission Control Protocol (TCP) which allows completing numerous different actions. NetCat is considered to be a back-end which can be managed by other programs or used directly. Even though TCP/IP employed by nc.exe is used for network testing, software capabilities might be abused by the cybercriminals." thus besically nc.exe can be used as a backdoor |
TL/DR: Seems likely that nc.exe and ncat.exe will always be seen by MS and AV as threat/risk on windows10/11/server. The reason seems only to be "Potentially Unwanted Behavior", perhaps related to software license defeat schemes. So issue#6 seems likely to remain open for a long time and/or be closed-won't fix.Work-around 1. Try adding as exception.You can try "allowing" nc.exe as an exception, but for at least one user, it seems the exception expires and the exact same unchanged nc.exe gets re-quarantined regularly, per https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/any-chance-that-quot-ncat-quot-doesn-t-get-rated-as-threat/m-p/1171947 . So this work-around would be to add the exception, and perhaps re-lobby MS to quit re-quarantining a particular nc.exe signature. But note that MS has been flagging nc.exe as a risk since 2007, even with the "-e" option removed. Work-around 2. Use linux.Or if see if windows allows nc to run inside WSL or a virtual linux machine. I've not attempted yet. Longshot: try to find out if anything we could change in nc.exe to avoid being flagged as threat.We could try to find out from MS or AV folks if there were additional changes in addition to the removing the "-e" option that might remove a (signed?) nc.exe it from the threat list. (Does windows have any signing/approval schemes for developers, perhaps like those in macos and ios?) Some sort of sandbox possible? BTW the nc.exe I saw quarantined for first time today was obtained by
And choco lists this github site as "Software Source":
So if this github site, in future hosted a nc.exe that was not flagged as a threat, then But even if nc.exe (or ncat.exe) is added to exception list, behavior based security software like crowdstrike still blocks execution of nc.exe and ncat.exe (at least on my laptop). In fact, crowdstrike blocked every solution offered at this website: https://superuser.com/questions/14501/are-there-netcat-like-tools-for-windows-which-are-not-quarantined-as-malware For example, crowdstrike blocked 2011-era ncat-static from https://nmap.org/dist/ncat-portable-5.59BETA1.zip |
Trying to use this
nc.exe
on a Windows Server 2019 node yields the following output:Strangely, this was not happening before.
The text was updated successfully, but these errors were encountered: