Distributed Crawler Poses as Human Visitor to Evade Analytics and Ad Filters
A site owner watching traffic graphs climb while advertising revenue stayed flat would normally celebrate algorithmic success. In this case the numbers told a different story: Google Analytics recorded new sessions, the server performed full TLS handshakes and dynamic page generation, yet no corresponding ad impressions were billed.
The discrepancy arises because GA4 accepts events via the Measurement Protocol, a server-to-server channel originally intended for offline interactions. A crawler that crafts the correct payload can register a session without ever rendering advertisements or executing the full browser resource chain of CSS, JavaScript, fonts and favicons.
Operators of a network of unrelated sites noticed the same subtle footprint on each property. Individual requests carried ordinary modern browser strings, arrived from search-engine referrers, and followed internal links at a human-like pace. Only when events were aggregated into a cross-site graph did the coordinated pattern emerge: dozens of IP addresses replaying nearly identical sequences while rotating User-Agent strings and never loading supporting page assets.
One particularly convincing candidate, masked as 203.0.113.0/24, produced roughly one hundred events over eight days. Its profile included search transitions, internal navigation, and a modest set of static resources. Raw logs, however, showed that almost half the requests openly declared themselves with the string “crawler” and that the supposed resources were exclusively images returning 404 responses without Referer headers.
Further examination of referrer data exposed additional contradictions. The same addresses claimed simultaneous arrivals from Google, Yandex, Bing and Baidu within minutes, an impossible sequence for any single human reader. Internal-link Referers were fabricated to simulate article-to-article reading, yet no stylesheets, scripts or actual page images were ever requested.
The investigation relied on a continuously updated graph whose vertices represented addresses, network blocks, browser masks and requested resources. Edges captured temporal and causal relationships, allowing analysts to test whether short, seemingly natural sessions on separate sites actually belonged to the same automated actor. GPU-accelerated processing made parallel comparison of hundreds of candidate biographies feasible.
The episode illustrates that server logs remain the only immutable record when analytics platforms and advertising systems can be fed synthetic events. By focusing on missing resource chains and contradictory origin stories rather than any single IP or country, defenders can surface distributed crawlers that have studied human browsing patterns in detail.
Related articles
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.
Researchers Deploy Cowrie Honeypot Disguised as NVIDIA H100 Server to Study SSH Botnet Tactics
A cybersecurity team set up a realistic Cowrie honeypot on a fake server equipped with four NVIDIA H100 GPUs, 128 AMD EPYC cores, and terabytes of storage to observe what SSH brute-force bots actually do after gaining access. The trap used a custom StickyAuth module that allowed entry only after several failed attempts and locked in the successful credential pair per IP address. Over the first 12.5 hours the system recorded 1,846 connections from 126 unique IPs, 175 successful logins, and 1,524 commands executed, with the majority of activity traced to a single botnet linked to the Outlaw group. The attackers deployed SSH keys signed mdrfckr, changed the root password, killed competing processes, installed cron jobs, and downloaded a mining archive called dota3 containing an IRC backdoor and its own SSH scanner. The researchers also identified three realism issues in the base Cowrie setup—limited grep flags, outdated filesystem paths in Debian 12, and inconsistent hostname reporting—and patched them to keep sophisticated bots engaged longer. An auxiliary LLM service later summarized each session in Telegram for easier analysis.
Hirudo Android Banking Trojan Uninstalls Legitimate Bank Apps and Installs Attacker-Controlled Fakes
Researchers at ThreatFabric have detailed Hirudo, a sophisticated Android banking trojan that also serves as a remote access tool and replaces genuine bank applications with attacker-controlled copies. The malware spreads through decoy apps themed around shopping, adult video, and short series, including Shopora, 1V1 X, ZoyaTV, and KoiShort. Once installed, it uses accessibility services to detect target banking apps, verify their signatures, display a fake update prompt, and force uninstallation of the real application before installing a malicious replica signed with a publicly known test key. The trojan employs components from the open-source YAHFA and Dobby projects to intercept signature checks, hide accessibility services, bypass screenshot restrictions, and forward Play Integrity attestations to the attacker’s server. Eight ready-made replicas target seven Indonesian banks, while credential theft focuses on users in China, India, Mexico, Morocco, and Thailand. Server logs collected in August 2026 contained thousands of credentials, device data, and financial profiles, with the attestation key set confirmed as publicly leaked and partially revoked by Google.
Over 300 Tor Exit Nodes Hijacked to Intercept SSH Passwords and Deploy Ebury Backdoor
Attackers compromised hundreds of Tor exit nodes and repurposed them to perform man-in-the-middle attacks against SSH connections. Instead of reaching the intended server, users were redirected to attacker-controlled infrastructure where they could be tricked into accepting a forged host key and revealing their credentials. Researcher kaba identified 333 malicious exit nodes routing traffic through the same 12 interception servers after noticing an unexpected host-key warning on October 2. The campaign also attempted to install the Ebury Linux backdoor designed to steal authentication data. The Tor Project confirmed that operators' servers had their configurations altered and some middle relays were converted into exit nodes. The initial access vector remains unknown, but the activity window was limited to October 1-5. Users who connected via Tor during this period, accepted an unfamiliar key, and entered a password should treat their credentials as compromised.