{"id":75971,"date":"2016-04-12T12:24:15","date_gmt":"2016-04-12T19:24:15","guid":{"rendered":"https:\/\/cloudblogs.microsoft.com\/microsoftsecure\/?p=75971"},"modified":"2023-05-15T23:06:46","modified_gmt":"2023-05-16T06:06:46","slug":"msrt-april-release-features-bedep-detection","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2016\/04\/12\/msrt-april-release-features-bedep-detection\/","title":{"rendered":"MSRT April release features Bedep detection"},"content":{"rendered":"
As part of our ongoing effort to provide better malware protection, the Microsoft Malicious Software Removal Tool <\/a>(MSRT) release this April will include detections for:<\/p>\n In this blog, we\u2019ll focus on the Bedep<\/a> family of trojans.<\/p>\n Win32\/Bedep<\/a> was first detected in November 25, 2014 as a malware family made up of DLLs which has been distributed by Angler Exploit Kit. Microsoft detects Angler as:<\/p>\n JS\/Axpergle<\/a> and HTML\/Axpergle<\/a> have been known to carry and drop Bedep<\/a> around by redirecting unsuspecting users to compromised websites.<\/p>\n Bedep<\/a> is bothersome not only because it is carried around by an exploit kit, but because it also connects to a remote server to do the nasty:<\/p>\n All of the above malware families have these in common: they steal your personal information and send them to the hacker, watch what you do online, drops other malware onto your PC, and update them too.<\/p>\n The good thing is, Windows Defender<\/a> detects and removes Bedep<\/a> and its variants.<\/p>\n This threat has been prevalent in North America, and various parts of Latin America, Europe, and Southeast Asia.<\/p>\n The exploit shellcode sometimes loads Bedep<\/a> directly in the memory from the Angler Exploit Kit, without being written to disk. However, it gets written to disk at other times.<\/p>\n It can either be installed as 32bit DLL (Backdoor:Win32\/Bedep.A<\/a>) or 64bit DLL (Backdoor:Win64\/Bedep.A<\/a>), depending on the affected Windows OS version.<\/p>\n This<\/a> threat is initially loaded by shellcode running in an exploited browser process (for example, iexplore.exe<\/em>). Then, the threat downloads a copy of itself and injects that into explorer.exe.<\/em><\/p>\n We have observed that the first exploit is not enough. The attacker needs more exploits to bypass the OS or browser’s layered defenses. As a precaution, you should always be careful on clicking the User Account Control (UAC) prompts.<\/p>\n We’ve also seen that Bedep<\/a> can drop itself as %ProgramData%<\/em><\/a>\\<{CLSID}>\\<filename>.dll<\/em><\/p>\n Example path and file names: C:\\ProgramData\\{9A88E103-A20A-4EA5-8636-C73B709A5BF8}\\acledit.dll.<\/em><\/p>\n It then creates the following registry entries:<\/p>\n In subkey: HKEY_CURRENT_USER\\CLSID\\%Random CLSID%\\InprocServer32<\/em><\/p>\n Example: HKEY_CURRENT_USER\\CLSID\\{F6BF8414-962C-40FE-90F1-B80A7E72DB9A}\\InprocServer32<\/em><\/p>\n Sets value: “ThreadingModel<\/em>“<\/p>\n With data: “Apartment<\/em>“<\/p>\n Sets value: “”<\/p>\n With data: %Bedep Filename%<\/em><\/p>\n Example: “C:\\ProgramData\\{9A88E103-A20A-4EA5-8636-C73B709A5BF8}\\acledit.dll<\/em>“<\/p>\n In subkey: HKEY_CURRENT_USER\\Drive\\ShellEx\\FolderExtensions\\%Random CLSID%<\/em><\/p>\n Example: HKEY_CURRENT_USER\\Drive\\ShellEx\\FolderExtensions\\{F6BF8414-962C-40FE-90F1-B80A7E72DB9A}<\/em><\/p>\n Sets value: “DriveMask<\/em>“<\/p>\n With data: dword:ffffffff<\/em><\/p>\n For details about various Bedep variants, see the following malware encyclopedia entries:<\/p>\n To help stay protected from Bedep and other threats, use an up-to-date<\/a> Windows Defender<\/a> for Windows 10 as your antimalware scanner, and ensure that MAPS has been enabled<\/a>.<\/p>\n Though trojans have been a permanent fixture in the malware ecosystem, there\u2019s still something that you or your administrators can proactively do:<\/p>\n Jonathan San Jose<\/em><\/p>\n Questions, concerns, or insights on this story? Join discussions at the Microsoft community<\/a> and Windows Defender Security Intelligence<\/a>.<\/p>\n\n
The bothersome Bedep<\/h2>\n
\n
\n
\n
\n
\n
Mitigation and prevention<\/h2>\n
\n
\nTalk to us<\/strong><\/h4>\n