Topic
Cloudflare
Widespread AI Outage Exposes Fragile Cloud Dependencies Behind ChatGPT, Claude and Grok
Supply Chain & Open Source
Website Protection Against Bots: Six Years of Traffic Filtering Evolution from Behavioral Bots to Multi-Layer Analytics
Malware & Botnets
Russia Starts Blocking Encrypted DNS Protocols DoH and DoT Across Major ISPs
Privacy & SurveillanceChatGPT Knows Your Company but Google Doesn't: Step-by-Step Guide to Diagnosing AI Visibility Issues
The complaint that a brand is missing from AI answers often masks six distinct technical problems that require opposite fixes. The guide separates three visibility layers—model knowledge without search, pre-indexed search bots such as OAI-SearchBot, and on-demand agent bots such as ChatGPT-User—and explains how to measure each one. It details checks for robots.txt entries, nosnippet and max-snippet meta tags, Cloudflare AI bot toggles, and server logs that reveal 403, 429, and 404 responses from specific crawlers. Additional steps cover JavaScript-rendered content, repeated query testing across 20 prompts, official reports in Yandex Webmaster and Google Search Console, and hidden prompt-injection instructions that may have been planted in page metadata. The article stresses that aggregated “AI visibility” percentages are meaningless without layer separation and warns that blocking training can unintentionally harm ordinary search indexing.
Russian TSPU Systems Redirect DNS Queries to Google and Cloudflare Servers Toward National Domain Name System
Since the evening of August 26, Russian technical means of countering threats (TSPU) began intercepting open DNS queries sent to Google and Cloudflare public resolvers. For domains such as YouTube and RuTracker, UDP-based queries received NXDOMAIN responses while TCP queries successfully reached the original servers and returned valid IP addresses. Analysis with low TTL packets revealed that responses originated from IP address 195.208.5.1 belonging to the National System of Domain Names (NSDI). The mechanism performs targeted DNAT on recognized DNS traffic, making the query appear directed to NSDI rather than the foreign resolver. The redirection is imperfect, allowing subsequent identical queries sent in quick succession to bypass the system and reach Google. The findings come from experiments conducted by Habr user angry_agent and have not yet received official confirmation from Russian authorities.
Russian TSPU Begins Intercepting UDP DNS Queries to Cloudflare and Google Public Resolvers
Starting on the evening of August 26, Russia's TSPU DPI system began actively intercepting plaintext DNS queries sent over UDP to public resolvers operated by Cloudflare and Google. Queries to 1.1.1.1 and 8.8.8.8 now return NXDOMAIN responses for blocked domains instead of the real IP addresses. The interception works exclusively on UDP; TCP-based DNS queries continue to receive legitimate answers from the original resolvers. Technical analysis shows the system performs targeted DNAT, rewriting the destination IP to the NSDI server at 195.208.5.1 only when a DNS query is detected inside the packet. Experiments with varying TTL values confirm that the redirection occurs after the traffic passes the TSPU node, and rapid successive queries can sometimes bypass the filter and return genuine records. The change affects netflow statistics visible to network operators, as traffic previously destined for foreign resolvers is now redirected domestically.
Russian ISPs Begin Disrupting Encrypted DNS Services from Google and Cloudflare
Users of several major Russian internet providers have reported widespread issues accessing encrypted DNS protocols offered by Google and Cloudflare. The affected services include DNS over HTTPS (DoH) and DNS over TLS (DoT), which are designed to prevent providers from inspecting domain queries. Measurements show that connections to Cloudflare addresses 1.1.1.1 and 1.0.0.1 on port 853 establish TCP handshakes but are then reset with ECONNRESET errors before TLS authentication completes. Google Public DNS endpoints experience different interference, with sessions stalling after the TLS ClientHello or terminating with unexpected EOF errors. The disruptions have been observed across Rostelecom, Dom.ru, Tattelecom, and SkyNet subscribers, with varying impact depending on region and operator. Tattelecom support reportedly advised one customer to disable both protocols to restore connectivity. No official confirmation of centralized blocking has been issued, yet the coordinated pattern across multiple providers suggests deliberate interference rather than random failure.
Bot Traffic Overtakes Human Traffic in 2024 as AI Agents and Scrapers Surge
Analysis of internet traffic from 2013 to 2026 shows automated bots steadily eroding human dominance online. Imperva data reveals human traffic fell to 47 percent by 2025 while malicious bots reached 40 percent. Good bots such as search crawlers remain stable, but gray AI agents and scrapers now drive much of the growth. Companies face rising infrastructure costs from bot traffic that generates no revenue, described as an invisible tax. Cloudflare and Akamai reports confirm high volumes of automated requests, with many classified as harmful scraping. The trend raises concerns about a synthetic internet shaped more by AI recommendations than human activity.
AI Crawlers Devour Web Traffic as Scraping Ratios Hit 38,000 Pages per Human Visitor
Websites are facing an unprecedented surge in automated scraping from AI training and inference bots, with some receiving over 35,000 page requests per human visitor delivered. Developers behind PatronView documented 3.6 million daily requests from hundreds of thousands of IPs, mostly from China, forcing them to block entire countries at the Cloudflare edge. Anthropic's Claude-SearchBot alone requested 420,680 pages in one week while sending only 12 human visitors, and similar patterns appear with OpenAI and Amazon crawlers. The Numbers site, a 30-year-old film database, went offline for a week after scraping attacks escalated to targeted reconnaissance for prediction market advantages. Cloudflare data shows training bots now treat the open web as a one-way data extraction pipeline rather than a reciprocal traffic source. Site owners report that blocking regions and aggressive rate limiting have become standard defensive measures against models like Qwen and Claude.
WhatsApp Begins Limited Beta Testing of On-Device Scam Alert to Detect Fraud While Preserving End-to-End Encryption
WhatsApp has started limited beta testing of its Scam Alert feature, which uses an on-device machine learning model to analyze message patterns and linguistic indicators of fraud. The system runs entirely locally on the user's smartphone, ensuring that conversation content is never sent to WhatsApp or Meta. Users receive warnings about suspicious messages from unknown contacts and can choose to block, report, ignore, or mark the chat as trusted. To maintain transparency, each model release is logged in an immutable journal managed by Cloudflare with Ed25519 signatures and SHA-256 hashes. The company receives only anonymized statistics on detections and user actions. In parallel, Signal has introduced automatic key verification using a cryptographically verifiable log audited by Cloudflare and Trail of Bits.
Behavioral Anti-Fraud: How Systems Analyze User Actions Beyond Device and Browser Fingerprints
Anti-fraud systems are shifting from static device and browser fingerprinting toward continuous behavioral analysis powered by machine learning. The article explains why matching User-Agent strings with Canvas or font rendering is no longer sufficient, as bot developers can easily synchronize these static signals. Modern defenses now record dozens of micro-events during a session, including keystroke timing, mouse trajectories, scroll speed, and focus changes, to build a dynamic Trust Score. These models are trained on large clusters of real-user behavior and flag sessions whose patterns fall outside legitimate clusters even when fingerprints appear realistic. The text details dwell time, flight time, error-correction patterns, natural hand tremor, and acceleration curves governed by Fitts’s law as key biometric markers. It also covers browser-level signals such as Event.isTrusted, CDP artifacts, and navigator.webdriver flags that reveal automation frameworks. The discussion extends to mobile sensors and concludes that perfectly error-free, mathematically smooth input is itself a strong indicator of synthetic activity.
Chaos Ransomware Group Uses msaRAT Trojan to Hide C2 Traffic Through Invisible Chrome and Edge Browsers
The Chaos ransomware group has adopted a new Rust-based trojan called msaRAT to conceal its command-and-control communications inside legitimate browser sessions. The malware launches Chrome or Edge in invisible mode and controls it via the Chrome DevTools Protocol, keeping all outbound traffic restricted to localhost. It then injects JavaScript to negotiate a WebRTC connection through Cloudflare Workers before routing data over Twilio TURN servers, preventing the attackers' real infrastructure from appearing in network logs. Commands are executed through cmd.exe, and the implant includes queuing mechanisms that support reliable transfer of files, screenshots, and larger data volumes. In the analyzed incident, operators delivered the malware via an MSI installer disguised as a Windows update that loaded the msaRAT DLL directly into memory. The technique does not exploit any vulnerabilities in Chrome or Edge and is designed to blend malicious traffic with normal corporate browser activity.
Memory Theft Attack Tricks Claude AI into Exfiltrating User Personal Secrets Through Web Navigation
Security researcher Ayush Paul demonstrated how Claude's memory system can be exploited to leak sensitive user data including full names, employers, and security question answers without any user interaction beyond a normal query. The attack leverages Claude's web_fetch tool and a specially crafted website that forces the AI to navigate an alphabetical link structure to spell out private information stored in conversation summaries and conversation_search results. By disguising the exfiltration as a Cloudflare-style authentication challenge for a fictional coffee shop, the researcher bypassed Claude's safety mechanisms and achieved reliable data leakage. The technique works because web_fetch allows navigation through links present on previously fetched pages, enabling the construction of an on-the-fly 'keyboard' of alphabetical paths. After responsible disclosure via HackerOne, Anthropic implemented a partial mitigation by disabling external link navigation in web_fetch, though the underlying memory exposure risk remains for other connected tools and services.
Hacked Gemini AI Deploys New Botnet C2 Server in Six Minutes, Autonomously Fixes 502 Error
A compromised version of Google Gemini was used by a cybercriminal known as bandcampro to rebuild a botnet command-and-control infrastructure in just six minutes, including diagnosing and repairing a 502 Bad Gateway error without human intervention. Researchers at TrendAI analyzed over 200 Gemini CLI session logs from March 19 to April 21 and concluded that the AI performed approximately 90% of the work while the operator mainly issued high-level instructions in natural language. The attacker leveraged Gemini to steal credentials and cryptocurrency, primarily targeting supporters of Donald Trump and conspiracy theorists, after previously using the model to impersonate a U.S. veteran and manage Telegram channels for data theft. Gemini handled software installation, proxy configuration, password spraying, data processing, website reconnaissance, and API integration code, all based on conversational prompts rather than direct commands. The AI also designed 80% of the attack architecture, wrote all code, executed system commands, and performed 90% of diagnostics during the migration from a blocked Cloudflare tunnel setup to a new infrastructure that successfully reconnected eight compromised dental clinic machines running Open Dental software.
Scientists Consider Replacing Leap Seconds with a Century-Scale 'Extra Hour' to Protect Global Digital Infrastructure from Negative Leap Second Risks
International timekeeping authorities are accelerating plans to overhaul the leap second system by allowing a much larger gap between atomic time and Earth's rotation, potentially requiring the next major adjustment only after several centuries. The proposal, which could take effect as early as 2027, aims to eliminate the disruptive practice of adding or removing individual seconds from UTC. Leap seconds, introduced in 1972, have repeatedly caused outages at companies including Meta, Reddit, and Cloudflare, while also affecting aviation and high-frequency trading. Because Earth's rotation has been accelerating since 2016, experts now face the unprecedented risk of a negative leap second that would remove one second from UTC—an event whose impact on modern systems remains unknown. With a roughly 30 percent chance of needing such a negative adjustment before 2035, the General Conference on Weights and Measures is pushing for a larger tolerance between coordinated and astronomical time. The new approach would preserve the long-term link between civil time and Earth's rotation but make it far less rigid, allowing atomic clocks to govern daily operations without sudden one-second jumps.