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.

Network Security

8/23/2019
10:45 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Newly Registered Domains Mean New Problems – Palo Alto

Why NRDs should matter to the security community.

Unit42 of Palo Alto Networks has been at it again. This time, they are looking at newly registered domains (NRD)and their propensity for delivering malicious malware.

Their post explains why NRDs should matter to the security community. "Our analysis," they say, "shows that more than 70% of NRDs are 'malicious' or 'suspicious' or 'not safe for work.' This ratio is almost ten times higher than the ratio observed in Alexa’s top 10,000 domains. Also, most NRDs used for malicious purposes are very short-lived. They can be alive only for a few hours or a couple of days, sometimes even before any security vendor can detect it. This is why blocking NRDs is a necessary, preventive security measure for enterprises."

Palo Alto defines NRDs as any domain that has been registered or had a change in ownership within the last 32 days. Its analysis indicated that the first 32 days is the optimal timeframe when NRDs are detected as malicious.

Time-variant instantiations should always be a red flag for a sysadmin. But with an NRD total volume that fluctuates between 150,000 and 300,000 a day, some instantiations can be missed in-between system scans.

NRDs are also associated with the distribution of malware. The Emotet malware family can serve an example. Emotet is a banking trojan well-known for sniffing network traffic for banking credentials. First discovered in 2014, it remains widely prevalent today.

Palo Alto says in the post that they have observed 50,000 unique samples at this point in 2019. The initial delivery is typically done through a phishing email or from a compromised website. This poisoned attachment often act as a downloader for a payload which is then executed to create the trojan. The downloading is performed via HTTP. Many of the URLs for the trojan were found to be hosted on NRDs. Phishing campaigns can also routinely use NRD URLs in moving their data about.

A domain generation algorithm (DGA) is a common approach used by many malware instantiations to periodically generate a large amount of domains. These can serve malicious purposes like command and control and data exfiltration. Most DGAs generate domains based on the date and the time. The idea is to make a law enforcement takedown harder to implement by making the range of targets more random. The attackers will only have to register a few of the ones that have been created for their criminal uses. But they will show up as an NRD.

Palo Alto Networks recommends blocking access to NRDs with URL Filtering. Some may think it's aggressive due to potential false-positives, but they say that the risk from threats via NRDs is much greater. At the bare minimum, if access to NRDs are allowed, then alerts should be set up for additional visibility.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/30/2020
'Act of War' Clause Could Nix Cyber Insurance Payouts
Robert Lemos, Contributing Writer,  10/29/2020
6 Ways Passwords Fail Basic Security Tests
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/28/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How to Measure and Reduce Cybersecurity Risk in Your Organization
In this Tech Digest, we examine the difficult practice of measuring cyber-risk that has long been an elusive target for enterprises. Download it today!
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15703
PUBLISHED: 2020-10-31
There is no input validation on the Locale property in an apt transaction. An unprivileged user can supply a full path to a writable directory, which lets aptd read a file as root. Having a symlink in place results in an error message if the file exists, and no error otherwise. This way an unprivile...
CVE-2020-5991
PUBLISHED: 2020-10-30
NVIDIA CUDA Toolkit, all versions prior to 11.1.1, contains a vulnerability in the NVJPEG library in which an out-of-bounds read or write operation may lead to code execution, denial of service, or information disclosure.
CVE-2020-15273
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. The issue affects the following components: Edit feed settings, Edit widget area, Sub site new registration, New category registration. Arbitrary JavaScript may be executed by entering specific characters in the account that can ac...
CVE-2020-15276
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is vulnerable to Cross-Site Scripting. Arbitrary JavaScript may be executed by entering a crafted nickname in blog comments. The issue affects the blog comment component. It is fixed in version 4.4.1.
CVE-2020-15277
PUBLISHED: 2020-10-30
baserCMS before version 4.4.1 is affected by Remote Code Execution (RCE). Code may be executed by logging in as a system administrator and uploading an executable script file such as a PHP file. The Edit template component is vulnerable. The issue is fixed in version 4.4.1.