Security firm Cyren issued a new report, “Botnets: The Clone Army of Cybercrime,” that described a new method of circumventing security blocking efforts. The researchers referred to this evasive technique as a “ghost host.”

Ghost Host in the Machine

SecurityWeek noted that, to carry out the procedure, malware authors place unknown host names in the HTTP host fields of a botnet’s communications. These host names can be registered and unregistered. Because of the indeterminate state of the included host names, which may or may not resolve in the Domain Name System (DNS), this can easily fool usual web security and URL-filtering systems.

The total IP range associated with a bad URL is not usually blocked because legitimate domains may also exist at the IP. Blocking the entire IP would block those legitimate domains.

The impetus for this discovery originated when Cyren detected communications between bot and server even after it blocked the malware server’s URL in the filters protecting a system. It noticed that a botnet member informed the command-and-control (C&C) server that a new infection had occurred. The researchers said they were unsure just how this communication took place at all.

Playing the Name Game

While the destination IP address of the communication packet was still known to be a bad server, the HTTP host fields that were used for requests were assigned to completely different domains. These domains are stuffed into the host fields that Cyren referred to as ghost hosts.

In one case, the researchers noted, the fake domains were “events.nzlvin.net” and “json.nzlvin.net.” The resolved domains were blocked, but not the ghost hosts. Changing the ghost host name sent in a communication might prompt different response actions from the C&C server. One host might document a new addition to the botnet, but another ghost name could serve new exploit code.

This is a novel technique that establishes a side-channel communication with a malware’s C&C server, survives a primary blacklist and delivers a resiliency that could impact the overall malware landscape. The increase in resiliency that it brings to malware will have to be evaluated in the near future.

More from

Who Carries the Weight of a Cyberattack?

Almost immediately after a company discovers a data breach, the finger-pointing begins. Who is to blame? Most often, it is the chief information security officer (CISO) or chief security officer (CSO) because protecting the network infrastructure is their job. Heck, it is even in their job title: they are the security officer. Security is their responsibility. But is that fair – or even right? After all, the most common sources of data breaches and other cyber incidents are situations caused…

Transitioning to Quantum-Safe Encryption

With their vast increase in computing power, quantum computers promise to revolutionize many fields. Artificial intelligence, medicine and space exploration all benefit from this technological leap — but that power is also a double-edged sword. The risk is that threat actors could abuse quantum computers to break the key cryptographic algorithms we depend upon for the safety of our digital world. This poses a threat to a wide range of critical areas. Fortunately, alternate cryptographic algorithms that are safe against…

Abuse of Privilege Enabled Long-Term DIB Organization Hack

From November 2021 through January 2022, the Cybersecurity and Infrastructure Security Agency (CISA) responded to an advanced cyberattack on a Defense Industrial Base (DIB) organization’s enterprise network. During that time frame, advanced persistent threat (APT) adversaries used an open-source toolkit called Impacket to breach the environment and further penetrate the organization’s network. Even worse, CISA reported that multiple APT groups may have hacked into the organization’s network. Data breaches such as these are almost always the result of compromised endpoints…

How Do You Plan to Celebrate National Computer Security Day?

In October 2022, the world marked the 19th Cybersecurity Awareness Month. October might be over, but employers can still talk about awareness of digital threats. We all have another chance before then: National Computer Security Day. The History of National Computer Security Day The origins of National Computer Security Day trace back to 1988 and the Washington, D.C. chapter of the Association for Computing Machinery’s Special Interest Group on Security, Audit and Control. As noted by National Today, those in…