Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

Bytes over DNS, (Mon, Oct 27th)

0
Low
Malware
Published: Mon Oct 27 2025 (10/27/2025, 09:10:01 UTC)
Source: SANS ISC Handlers Diary

Description

I was intrigued when Johannes talked about malware that uses BASE64 over DNS to communicate. Take a DNS request like this: label1.label2.tld. Labels in a request like this can only be composed with letters (not case-sensitive), digits and a hyphen character (-). While BASE64 is encoded with letters (uppercase and lowercase), digits and special characters + and /. And also a special padding character: =.

AI-Powered Analysis

AILast updated: 10/27/2025, 09:13:03 UTC

Technical Analysis

The analyzed threat describes a malware communication technique leveraging DNS queries to transmit arbitrary byte values covertly by encoding data within DNS request labels. DNS labels traditionally allow only letters, digits, and hyphens, but this research demonstrates that by crafting DNS packets and using third-party DNS resolvers such as CloudFlare (1.1.1.1) and Google (8.8.8.8), it is possible to transmit a broader range of byte values, including all ASCII characters (0x00-0x7F) and even extended byte values (0x80-0xFF) with custom packet crafting. The malware encodes data using a modified BASE64 scheme, replacing characters like '+' and '/' with '-' and '_', and omitting padding characters to comply with DNS label restrictions. CloudFlare's DNS infrastructure allows reliable transmission of these bytes when custom DNS packets are crafted and parsed, while Google's DNS modifies letter casing as an anti-spoofing measure, reducing reliability for letters. The attacker controls both the querying client and the authoritative DNS server, enabling a covert command and control (C2) channel that can bypass traditional network defenses since DNS traffic is typically allowed and trusted. The research includes detailed testing on Windows and Ubuntu platforms, showing differences in DNS resolver behavior and the impact of DNS infrastructure on data transmission reliability. The threat does not currently have known exploits in the wild but highlights a novel covert channel technique that could be leveraged by malware for stealthy communication and data exfiltration. Detection is difficult because the DNS queries appear legitimate and conform to DNS protocol standards, albeit with unusual label content. The author suggests future research into detecting abnormal DNS traffic patterns indicative of such covert channels.

Potential Impact

For European organizations, this threat presents a stealthy communication and data exfiltration vector that can bypass conventional network security controls due to the legitimate nature of DNS traffic. Organizations relying on third-party DNS resolvers like CloudFlare and Google are particularly at risk, as these services are widely used across Europe. The covert channel can be used by malware to maintain persistent command and control, exfiltrate sensitive data, or receive instructions without raising immediate suspicion. Critical infrastructure sectors, financial institutions, and government agencies are especially vulnerable due to the high value of their data and the potential impact of undetected breaches. The difficulty in detecting such DNS-based covert channels complicates incident response and forensic investigations. Additionally, the use of DNS for covert communication can lead to data leakage, intellectual property theft, and prolonged undetected intrusions. While the current severity is low to medium due to the complexity of crafting and parsing custom DNS packets, the potential for stealthy, persistent attacks makes this a significant concern for European cybersecurity.

Mitigation Recommendations

European organizations should implement advanced DNS traffic monitoring and anomaly detection systems capable of analyzing DNS query label patterns for unusual encodings or frequency anomalies indicative of covert channels. Deploy DNS security solutions that support DNS over HTTPS (DoH) or DNS over TLS (DoT) with trusted resolvers to reduce reliance on third-party DNS infrastructure and limit exposure to manipulation. Network segmentation and strict egress filtering should be enforced to restrict DNS queries to authorized resolvers only. Security teams should develop or adopt tools to decode and inspect DNS query labels for non-standard encodings such as modified BASE64 or unusual character sets. Endpoint detection and response (EDR) solutions should be configured to monitor for suspicious DNS query generation behavior from hosts. Regular threat hunting exercises focusing on DNS traffic anomalies can help identify early signs of such covert channels. Collaboration with DNS service providers to understand and monitor DNS traffic patterns can enhance detection capabilities. Finally, educating IT staff about this novel threat vector will improve preparedness and response.

Need more detailed analysis?Get Pro

Technical Details

Article Source
{"url":"https://isc.sans.edu/diary/rss/32420","fetched":true,"fetchedAt":"2025-10-27T09:12:45.721Z","wordCount":918}

Threat ID: 68ff378d8ee3628e2d779a80

Added to database: 10/27/2025, 9:12:45 AM

Last enriched: 10/27/2025, 9:13:03 AM

Last updated: 10/30/2025, 1:55:49 PM

Views: 30

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats