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 6/5/2020
How AI and Automation Can Help Bridge the Cybersecurity Talent Gap
Peter Barker, Chief Product Officer at ForgeRock,  6/1/2020
Cybersecurity Spending Hits 'Temporary Pause' Amid Pandemic
Kelly Jackson Higgins, Executive Editor at Dark Reading,  6/2/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: What? IT said I needed virus protection!
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13890
PUBLISHED: 2020-06-06
The Neon theme 2.0 before 2020-06-03 for Bootstrap allows XSS via an Add Task Input operation in a dashboard.
CVE-2020-13889
PUBLISHED: 2020-06-06
showAlert() in the administration panel in Bludit 3.12.0 allows XSS.
CVE-2020-13881
PUBLISHED: 2020-06-06
In support.c in pam_tacplus 1.3.8 through 1.5.1, the TACACS+ shared secret gets logged via syslog if the DEBUG loglevel and journald are used.
CVE-2020-13883
PUBLISHED: 2020-06-06
In WSO2 API Manager 3.0.0 and earlier, WSO2 API Microgateway 2.2.0, and WSO2 IS as Key Manager 5.9.0 and earlier, Management Console allows XXE during addition or update of a Lifecycle.
CVE-2020-13871
PUBLISHED: 2020-06-06
SQLite 3.32.2 has a use-after-free in resetAccumulator in select.c because the parse tree rewrite for window functions is too late.