Jump to content


  • Posts

  • Joined

  • Last visited

About Robbb

  • Rank

Profile Information

  • Location
  1. I think some regression error is going on. Did you see the date on the spiceworks thread? And the fact getting off detection engine v20199 resolves it. When was 20199 released?
  2. No worries. I believe someone else on that SW thread has opened a ticket with ESET, so hopefully they're working on it. I figured putting it here where admins go first would give some visibility. We're an MSP and found this issue on multiple servers - but not all Exchange 2010 servers - no correlation between OS Exchange version - eg we have one 2012/Exchange 2010 server with the false alert, and another without, even running same version of Mail Security and the same v20199 detection engine.
  3. We have been receiving false positives from a dynamic .dll generated by Exchange/IIS for OWA on detection engine 20199. It is occurring on different OSes, (2008 R2, SBS2011, 2012) with the common denominator being Exchange 2010 with OWA. Threat type: trojan Threat name: MSIL/Webshell.C Computer name: server.domain.local Logged user: Object: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/Temporary ASP.NET Files/owa/c60e4757/114626a/App_Web_yvgyrxbc.dll This file is generated on the fly when accessing OWA We rolled back to latest snapshot of detection engine until this is resolved. Is ESET aware of this issue? Any further info we can provide? See this SpiceWorks thread for more reports: https://community.spiceworks.com/topic/2237907-threat-found-in-event-viewer-shutting-off-access-to-exchange-via-deletion?page=1#entry-8609072
  4. So why is ESET the only AV that is failing this file's signature?
  5. I only started seeing these errors once upgraded to 7.0.12018.0, so it's not just that. Still getting these errors as of 20 mins ago.
  • Create New...