Threat Intelligence

10/1/2018
06:00 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

'Short, Brutal Lives': Life Expectancy for Malicious Domains

Using a cooling-off period for domain names can help catch those registered by known bad actors.

Domain Name System (DNS) pioneer Paul Vixie for more than three years has been calling for a "cooling off" period for newly created Internet domain names as a way to deter cybercrime and other abuses. Domain names registered and spun up in less than a minute only encourage and breed malicious activity, he argues, and placing them in a holding pattern for a few minutes or hours can help vet them and catch any registered by known spammers and other bad actors.

Vixie — who is founder and CEO of threat intelligence firm Farsight Security — and his team have now taken an up-close look at the life cycle of new Internet domains, and their findings shine new light on the lifespan of malicious and suspicious domains. "Most of them die young, and most of them die after living short, brutal lives," he says of newly created domains.

Over a six-month period, Vixie and his team conducted a longitudinal study of 23.8 million domains under 936 top-layer domains from their creation. They found that in the first seven days, 9.3% of new domains died: the median lifespan was four hours and 16 minutes.

The cause of death for 6.7% of those new domains was blacklisting, and most of them were blocked within an hour of their birth. DNS registrars and hosting providers, meanwhile, deleted or revoked malicious domains in three days or more after their creation. Interestingly, new generic top-level domains (gTLDs) suffered three times the rapid deaths than traditional ones such as .com, .net, .org, and .edu, for example.

Vixie's team found in the first week of life for new gTLDs there were 12 cases of more of them dying than living past their first week. "I was not shocked to see them as poster children of the short-lifetime effect," he says. "I don't know if they are more abusable or not," but it's possible the registries who snapped them up to sell aren't getting as much business as they expected. "They're under a good deal of financial pressure," he says, so some may be less choosy over to whom they sell their available domains.

The Internet's biggest TLD, .com, had just 2% of its new domains blacklisted and 3.6% deleted by registrars.

The new research, which Vixie will present on October 5 at the VirusBulletin International Conference in Montreal, underscores how a secure DNS policy is needed both for registrars that issue domains as well as enterprises that register new domains, he says. Putting new domains on ice for hours, days, or a week, is the best approach to ensure there's no malicious intent or ties. Enterprises, too, get the benefit of ensuring their new domains aren't incorrectly blacklisted, for example.

"All new domain should go into a penalty box — good or bad — until they've had a chance to live long enough," he says. Vixie's full report will be released on Friday.

Related Content:

Black Hat Europe returns to London Dec. 3-6, 2018, with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions, and service providers in the Business Hall. Click for information on the conference and to register.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
High Stress Levels Impacting CISOs Physically, Mentally
Jai Vijayan, Freelance writer,  2/14/2019
Valentine's Emails Laced with Gandcrab Ransomware
Kelly Sheridan, Staff Editor, Dark Reading,  2/14/2019
Making the Case for a Cybersecurity Moon Shot
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  2/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8980
PUBLISHED: 2019-02-21
A memory leak in the kernel_read_file function in fs/exec.c in the Linux kernel through 4.20.11 allows attackers to cause a denial of service (memory consumption) by triggering vfs_read failures.
CVE-2019-8979
PUBLISHED: 2019-02-21
Koseven through 3.3.9, and Kohana through 3.3.6, has SQL Injection when the order_by() parameter can be controlled.
CVE-2013-7469
PUBLISHED: 2019-02-21
Seafile through 6.2.11 always uses the same Initialization Vector (IV) with Cipher Block Chaining (CBC) Mode to encrypt private data, making it easier to conduct chosen-plaintext attacks or dictionary attacks.
CVE-2018-20146
PUBLISHED: 2019-02-21
An issue was discovered in Liquidware ProfileUnity before 6.8.0 with Liquidware FlexApp before 6.8.0. A local user could obtain administrator rights, as demonstrated by use of PowerShell.
CVE-2019-5727
PUBLISHED: 2019-02-21
Splunk Web in Splunk Enterprise 6.5.x before 6.5.5, 6.4.x before 6.4.9, 6.3.x before 6.3.12, 6.2.x before 6.2.14, 6.1.x before 6.1.14, and 6.0.x before 6.0.15 and Splunk Light before 6.6.0 has Persistent XSS, aka SPL-138827.