Website Protection Against Bots: Six Years of Traffic Filtering Evolution from Behavioral Bots to Multi-Layer Analytics
The author first encountered the issue of web traffic quality in 2020 while working on web development and SEO. Normal traffic patterns in analytics were replaced by storms of anomalous visits that showed identical behavior impossible for real users. Detailed inspection of Yandex Metrika Webvisor reports confirmed these were not genuine visitors but automated scripts aimed at manipulating behavioral factors.
Initial experiments relied on Cloudflare custom rules because no other tool offered comparable technical flexibility. The first published article on the topic documented cases of social-network bot traffic and its negative SEO impact. Research across multiple client projects consistently linked the appearance of this traffic with organic position drops and pessimization.
Between 2020 and 2021 the first wave manifested as 30–60 daily visits from social platforms where the site had no real presence. Blocking referrers via .htaccess simply caused bots to switch to direct entries or endless external domains. Server-side JavaScript and cookie validation forced bots to change their reported source but did not halt the traffic.
Two mobile IP ranges belonging to MegaFon were temporarily blocked with short-term success, yet the bots immediately migrated to new pools. The same pattern repeated with IPv6 traffic, proving that static IP blacklists become a losing race against rotating proxies.
Digital fingerprints proved equally unreliable. Each bot visit presented a fresh browser profile, rendering fingerprint-based detection ineffective. The author coined the term “behavioral bots” to distinguish this class of automation from classic crawlers because the scripts actively imitated human navigation and actions.
Excluding suspicious IPs from Yandex Metrika reports created an illusion of clean statistics while the actual requests continued to hit the origin server. The author repeatedly warned that visual cleanup of analytics does not equal protection and that genuine filtering must occur before requests reach the application.
Related articles
Cloudflare Blocks 18.2 Million DDoS Attacks in Q3 2026 Amid Shifting Attack Patterns
Cloudflare reported blocking 18.2 million network-layer DDoS attacks between July and September 2026, marking a 208% increase from the same period in 2025. The company recorded an average of roughly 8,200 attacks per hour, with 96% lasting under ten minutes and 98% staying below 1 Gbps. Large-scale attacks exceeding 1 Tbps dropped sharply from 805 in Q2 to 251 in Q3, a decline Cloudflare links to early 2026 law enforcement actions against four IoT botnets. Attack vectors shifted notably, with CLDAP reflection falling 99.5% while DNS amplification rose 215% and UDP floods grew 122%. The United States led targeted countries, followed by China and Indonesia, while media and publishing remained the most affected industry. Mirai variants accounted for 46.5% of network-layer bytes, with new families such as Dysphoria and Evooo1Bot emerging to replace dismantled botnets.
Freshko: Open-Source Rust Tool Offers Local File and URL Scanning Without Data Upload
A developer has released Freshko, a compact 400x640 pixel desktop application built in Rust that performs quick local checks on files, folders, and URLs without sending data to external services. The tool uses YARA-X rules for file scanning, follows up to eight redirects while querying Cloudflare's filtering DNS, and scores processes for potential cryptocurrency miners based on names, arguments, and launch paths. It explicitly avoids acting as a full antivirus solution, instead providing transparent results that list any skipped items or incomplete checks. Freshko runs on macOS and Windows, keeps all scan results in memory only, and disables system proxies during URL checks to prevent DNS rebinding attacks. The project includes performance benchmarks on Apple Silicon and addresses common pitfalls such as high CPU usage false positives and incomplete disk scans. Unlike VirusTotal or Cloudflare URL Scanner, Freshko performs all file analysis locally and never makes scan reports public.
Yoba Campaign Uses Signed ChatGPT and Claude Binaries for DLL Sideloading and XMRig Deployment
Researchers at Check Point Research have uncovered the Yoba malware campaign that distributes fake desktop clients for ChatGPT and Claude through GitHub repositories. The attackers bundle legitimate signed executables from OpenAI and Anthropic with a malicious DLL that gets loaded via classic sideloading. Once executed, the loader establishes persistence using the Windows Task Scheduler and retrieves additional payloads through Telegram, DNS over HTTPS, and the Catbox file hosting service. The campaign ultimately deploys the XMRig cryptominer, which pauses mining activity when user interaction is detected to avoid detection. No compromise of OpenAI or Anthropic infrastructure was found; the attackers simply repurpose the companies' signed binaries and reputation. The operation primarily targets home users and small-to-medium businesses with Windows systems.
uCreator Spyware Infiltrates Modified Telegram, WeChat and GCash Builds on Android
Security researcher Ovi has published a detailed analysis of uCreator, also known as YingGai, a commercial Android spyware platform designed for surveillance and remote app control. The malware intercepts messages, verification codes and account data directly inside legitimate applications without requiring root privileges. Infection vectors include tampered Telegram, WeChat and GCash APKs distributed through unofficial sources, as well as the Onion Box container that launches the target app inside a controlled environment. Once active, uCreator hooks into the host process, reads Telegram’s local message database through client interfaces, captures two-factor authentication passwords and hides its own session from the user. The operation is supported by cloud-based command panels and exposed GitLab repositories that revealed server-side code and development history. Compatibility problems have been noted on Android 17, and the total number of victims remains unknown.