Hi @ozarc,
Thank you for reaching out to us regarding the issue you’re experiencing. Based on your message, it seems that you’ve encountered an error message from Windows Defender stating that a Trojan has been blocked while attempting to update WooCommerce on your local computer.
Please note that WooCommerce is actually installed on your WordPress website and not on your local computer. Therefore, the error message you’re seeing is likely caused by another application on your computer.
We recommend running a thorough virus scan on your computer to identify any potential threats that may be causing the error.
If you continue to experience the same issue, please share a screenshot displaying that WooCommerce is creating the above error so we can troubleshoot further and guide you in the right direction.
Looking forward to your reply!
Just encountered the same trojan warning from Defender on a new install of WP via Local, for local development. The initial WC install was via a Kadence theme starter package that attempted to install WC.
I then attempted to install WC manually via download from the plugin repository, but Defender blocked it after finding the same malware. So, it seems there is a problem with the WC package, either with an actual malware or Defender throwing a false positive. Either way, it should be investigated.
WooCommerce 7.6.0
WordPress 6.2
-
This reply was modified 1 year ago by
KhakiMan.
I had the same problem, when trying to download wc from here. Not from within the admin.
Hi @hnloi and @khakiman,
Sorry to hear that you both had the same issue.
There is no Trojan within WooCommerce and this seems like a possible false positive from your Anti Virus.
For safety, have you tried installing a fresh copy of our WooCommerce plugin from here just in case the installation was compromised in some way and files have been altered?
I am getting the same error on Windows 10 when I try to install WC from the plugin-install page. I am using XAMMP to run WordPress as a local service for development porpuses.
-
This reply was modified 11 months, 1 week ago by
andrescol24.
Hello everyone!
Thank you for bringing this to our attention!
We appreciate all the reports received regarding this issue. We have already reported it on GitHub and have also flagged it as a false positive to Microsoft for their review. Hopefully, they will update their definitions as soon as possible.
To stay informed about any updates as they occur, we recommend subscribing to the GitHub thread. This way, you will be kept in the loop regarding any developments regarding this matter.
I hope this helps!
