Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Partner Perspectives  Connecting marketers to our tech communities.
12/15/2015
02:50 PM
Vincent Weafer
Vincent Weafer
Partner Perspectives
100%
0%

Detecting the Undetectable: Windows Registry Attacks

Fileless attacks are becoming more sophisticated, requiring a team of defenses.

Attackers are constantly looking for new ways to evade detection. New malware techniques take advantage of operating system features to inject malicious code into memory or the operating system registry without leaving a file on the disk. Traditional detection tools that rely on analyzing disk files need to be augmented with memory analysis and memory protection mechanisms, behavioral analysis, and broader intelligence sharing.

A current trend in fileless malware attacks is to inject code into the Windows registry. Most of these attacks enter a system as a file or link in an email message; this technique serves to emphasize the continued importance of email scanning and user awareness training. When the link or attachment is clicked, the malware writes its payload into the Windows registry and then disappears.

The payload written into the Windows registry contains a script hidden by several layers of tricks. The script is masked from view by removing the user’s access privileges or including a null character in the registry key name. The script calls a legitimate Windows program such as PowerShell to insert malicious code into the memory space of standard Windows processes such as svchost, dllhost, or regsvr32, so that the code cannot be detected by scans for malicious processes.

Examples that McAfee Labs has seen so far, including Kovter and Powelike, connect with websites and click-through ads, transforming the infected system into a click bot. The more resources the system has, the more ad traffic it generates, and the more money it makes for the criminals. Some analyzed variants have also downloaded ransomware payloads.

Fileless malware registry attacks leave no malware files to scan and no malicious processes to detect. Further, evidence of malicious registry keys is hidden by removing access controls and encrypting the values. Operating system updates and patches will not prevent attack because no vulnerabilities have been targeted. Specific rules are available that write-protect registry keys and processes, but more generic write-protection rules are not advised as many legitimate programs need to make registry changes.

The defense to this and other new types of fileless attacks is not just an updated virus definition file or even a single “silver bullet” tool. We need to look at user and system behavior, not individual devices, files, and processes. Humans are often the weakest defensive link, and this type of attack relies heavily on that vulnerability.

Email and Web gateways can also help protect users from the initial malware. As soon as a malicious link is detected by a gateway, it should not only be shared with others, but a network traffic analysis should scan for recent traffic to the URL to identify computers that may be already infected. Because early emails may get through before the URL is convicted, endpoint security should watch for registry changes, as well as script-based execution of management tools such as PowerShell and Windows Management Instrumentation. Hardware-based memory protection is an emerging security category that brings another layer to the defender’s side. Finally, behavioral analysis will help to quickly contain the infection by identifying infected computers shortly after automated ad clicking begins. Detecting the undetectable requires a team of defenses.

For more information on fileless malware, please visit http://www.mcafee.com/November2015ThreatsReport.

 

Vincent Weafer is Senior Vice President of Intel Security, managing more than 350 researchers across 30 countries. He's also responsible for managing millions of sensors across the globe, all dedicated to protecting our customers from the latest cyber threats. Vincent's team ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
gsatpathy
50%
50%
gsatpathy,
User Rank: Apprentice
1/22/2016 | 4:30:30 AM
Registry Attacks
I feel AV scanner should include scanning the injected system processes. It could reduce such fileless malwares from spreading.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13295
PUBLISHED: 2020-08-10
For GitLab Runner before 13.0.12, 13.1.6, 13.2.3, by replacing dockerd with a malicious server, the Shared Runner is susceptible to SSRF.
CVE-2020-6070
PUBLISHED: 2020-08-10
An exploitable code execution vulnerability exists in the file system checking functionality of fsck.f2fs 1.12.0. A specially crafted f2fs file can cause a logic flaw and out-of-bounds heap operations, resulting in code execution. An attacker can provide a malicious file to trigger this vulnerabilit...
CVE-2020-6145
PUBLISHED: 2020-08-10
An SQL injection vulnerability exists in the frappe.desk.reportview.get functionality of ERPNext 11.1.38. A specially crafted HTTP request can cause an SQL injection. An attacker can make an authenticated HTTP request to trigger this vulnerability.
CVE-2020-8224
PUBLISHED: 2020-08-10
A code injection in Nextcloud Desktop Client 2.6.4 allowed to load arbitrary code when placing a malicious OpenSSL config into a fixed directory.
CVE-2020-8229
PUBLISHED: 2020-08-10
A memory leak in the OCUtil.dll library used by Nextcloud Desktop Client 2.6.4 can lead to a DoS against the host system.