{"id":22385,"date":"2021-12-01T01:26:53","date_gmt":"2021-12-01T00:26:53","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=22385"},"modified":"2021-12-01T01:26:53","modified_gmt":"2021-12-01T00:26:53","slug":"microsoft-defender-version-1-353-1874-0-meldet-flschlich-trickbot-emotet","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2021\/12\/01\/microsoft-defender-version-1-353-1874-0-meldet-flschlich-trickbot-emotet\/","title":{"rendered":"Microsoft Defender Version 1.353.1874.0 version 1.353.1874.0 incorrectly reports Emotet"},"content":{"rendered":"

\"Sicherheit[German<\/a>]A brief note for administrators. Microsoft Defender reportes a PowEmotoet.SB <\/em>infection has been blocked and quarantined and possibly triggers Microsoft Office? This is a false alarm, which was triggered by an update of the signature files to version 1.353.1874.0. Here is some information on what is known so far. <\/p>\n

<\/p>\n

\"\"German blog reader Constantin contacted me by email an hour ago (thanks for that) and alerted me to a problem on Windows related to Microsoft Defender for Endpoint with the following lines:<\/p>\n

\n

Hello,<\/p>\n

Definitely worth a nice article ,how Microsoft screwed up again and scared all admins. <\/p>\n

Microsoft has gone into the toilet with a Defender definition and every Office start is now probably a Defender false positive…. <\/p>\n

PowEmotet we recognized. <\/p>\n

Twitter explodes just to it.  Since all admins are happy tomorrow morning….<\/p>\n<\/blockquote>\n

In addition, Constantin has sent me a link to the following tweet<\/a> from security researcher Kevin Beaumont, which addresses these observations. Defender seems to trigger something so that Microsoft Office opens.  <\/p>\n

\"Microsoft<\/a><\/p>\n

Christopher Mage then recreated this in a virtual machine. On 11\/30\/2021, Defender alerted a Behavior:Win32\/PowEmotet.SB<\/em> finding to him while printing. Defender then blocked the PowEmotet.SB (signature) file in question. Beaumont quickly came to the conclusion that it was a rolled-out change in the virus signature that basically triggered a false positive on any Office DDE control.<\/p>\n

On Twitter, there is this tweet<\/a>, where a user posts something similar. In this tweet<\/a>, a user writes that \"PowEmotet\" is currently being flagged as a false positive by Microsoft Defender via \"C:\\Windows\\splwow64.exe\"<\/em> when users try to print from Office365 applications. On reddit.com there is this post<\/a>:<\/p>\n

\n

MsDefender detect Emotet in Microsoft Excel<\/p>\n<\/blockquote>\n

\n

For the last 40 minutes we have 5-6-7 windows device that MSDefender detected Win32\/PowEmotet.SB . If we update the antivirus definition and open a new Excel file after we will have detection.<\/p>\n<\/blockquote>\n

who complains about an Emotet infections in Microsoft Excel and asks if he is alone. In the meantime,Within the thread more and more users are reporting this observation. Quite quickly, users state that these findings occur with the virus definition v.1.353.1874.0 of Defender. Meanwhile, Microsoft has posted the following information, which I found in the reddit thread. <\/p>\n

\n

\"Starting on the evening of November 29th, customers may have experienced a series of false-positive detections that are attributed to the Behavior:Win32\/PowEmotet.SB malware detection. Microsoft has investigated this spike of detections and determined they are false positive results. The affected Security Intelligence builds began with 1.353.1842.0. Microsoft has suppressed the detection preventing future alert spikes for those customers connected to the cloud. An upcoming Security Intelligence build to address the issue will be released shortly.\"<\/p>\n<\/blockquote>\n

So confirmation that a flawed Defender Antivirus signature 1.353.1842.0, rolled out Nov. 29, is responsible for these false alerts. Microsoft suppressed the detection to prevent future spikes in alerts for customers connected to the cloud. A new security intelligence build to fix the issue is expected to be released soon. Addendum: Bleeping Computer colleagues also report the same issue here<\/a>. A week ago, there has been also an issue with Defender, see Windows Server 2019\/2022: Microsoft Defender for Endpoint fails after Nov. 2021 updates<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

[German]A brief note for administrators. Microsoft Defender reportes a PowEmotoet.SB infection has been blocked and quarantined and possibly triggers Microsoft Office? This is a false alarm, which was triggered by an update of the signature files to version 1.353.1874.0. Here … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[580,2],"tags":[773,69,194],"class_list":["post-22385","post","type-post","status-publish","format-standard","hentry","category-security","category-windows","tag-defender","tag-security","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/22385","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=22385"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/22385\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=22385"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=22385"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=22385"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}