Gesture Dynamics CAPTCHA Emerges as Privacy-Focused Drop-in Alternative to reCAPTCHA
A new open-source project introduces a gesture-dynamics CAPTCHA designed as a drop-in replacement for reCAPTCHA. Instead of forcing users to identify buses or traffic lights, the system asks visitors to draw an arbitrary gesture lasting roughly ten seconds.
The core idea is to classify motor behavior rather than visual content. Eight statistical features, including velocity variance, pause entropy, rhythm irregularity, and correction count, are extracted from the gesture. A local gradient-boosting model handles clear cases in milliseconds, while an LLM is invoked only for uncertain borderline decisions.
The widget is delivered inside an iframe served from the vendor origin. This architecture avoids CORS restrictions and Origin-based bot filters that would arise if the client page called the API directly. Each integration uses a public key bound to an allow-list of domains and a secret key kept on the customer server for token verification.
Privacy protections are explicit: raw coordinates never leave the browser, no image datasets are collected, and no biometric templates are stored. The resulting token carries no user identity and expires after 120 seconds. Because no Google services are involved, sites avoid both data-transfer concerns under GDPR and the need for additional cookie banners.
Integration requires two lines on the client side and a single server-side verification call modeled after reCAPTCHA. On success the loader injects a hidden field named aptogon-response; the backend then posts the token to the verification endpoint using the secret key.
The project acknowledges its limitations. A motivated attacker could eventually imitate human dynamics, and the widget alone does not stop distributed floods through residential proxies. Accessibility accommodations for motor impairments are included, with ongoing collection of feedback to refine the models.
In the Russian market the solution positions itself against Yandex SmartCaptcha, targeting developers who need self-serve privacy controls and cannot rely on reCAPTCHA due to availability or regulatory constraints. Source code, documentation, and live demos are available under the AGPL-3.0 license with a free tier of one thousand verifications per month.
Related articles
Amnezia VPN Survives Coordinated Russian Censorship Campaign Targeting AmneziaWG Protocol Fingerprints
Amnezia VPN has published a detailed post-mortem on the multi-wave blocking campaign conducted by Russian authorities against its Amnezia Free and Amnezia Premium services during June and July. The company describes a shift from simple protocol blocking to sophisticated fingerprinting of AmneziaWG traffic combined with infrastructure DDoS attacks and automated IP-subnet blacklisting. Engineers closed multiple detection vectors including zero-length UDP packets, fixed-size keepalive messages, handshake timing patterns, and nonce zero bytes. The incident forced accelerated migration to AmneziaWG 2.0, discontinuation of legacy client support, and development of AmneziaWG 3.0 while expanding VLESS infrastructure as a backup. Self-hosted users largely avoided direct protocol blocks but still faced subnet-level restrictions. The report highlights how Roskomnadzor now applies cumulative scoring across multiple traffic features rather than single definitive markers.
Data Masking: 8 Critical Questions Businesses and Developers Ask About Protecting Sensitive Data
Garda expert Dmitry Larin addresses common challenges in data masking during a recent webinar titled 'Data Masking: Battle of Opinions'. The discussion covers why masking remains essential even when encryption is deployed, how to preserve application functionality after anonymization, and the performance trade-offs of processing large databases such as 5 TB PostgreSQL instances. Different masking types including static, dynamic, selective, and streaming are explained with specific use cases for DevOps pipelines, external contractors, and BI systems. The article also examines why machine learning alone is insufficient for discovering personal data and why custom scripts fail at scale across heterogeneous environments like PostgreSQL and Oracle. Practical recommendations include combining masking with encryption, using deterministic transformations for deduplication, and separating replication from masking tasks to avoid production impact.
MAX Desktop Client Tested for VPN Detection on Windows, No Tracking Signs Found
A Habra user named Slava_B conducted an experiment on September 8, 2026, to determine whether the MAX desktop client on Windows could detect or route traffic through a VPN configured at the router level. The setup used a Keenetic router that directed Russian resources directly while sending other connections via an OpenConnect tunnel to a European VPS, with no VPN client or virtual adapter present in Windows itself. Monitoring tools including Process Monitor, Wireshark, TCPView, and tcpdump revealed that MAX.exe and MAX-service.exe processes communicate locally and connect to MAX/ONEME infrastructure along with AppTracer services. The application repeatedly accessed MachineGuid, computer name, proxy settings, device IDs, and microphone/camera information, though these reads may support diagnostics and anti-fraud functions. No connections appeared on the VPN interface, and the client did not attempt to reach IP-checking services, Telegram, or WhatsApp. The researcher noted that TLS traffic was not decrypted, so actual transmission of identifiers could not be confirmed, and results apply only to this router-based configuration.
PII-Guard: Open-Source Detector for Personal Data in Russian Text
Andrey Ivanov, an NLP researcher at red_mad_robot, has released PII-Guard, an open-source system that detects and masks personal data in Russian text before it reaches language models. The tool combines rule-based checks with a fine-tuned ruBert-base NER model to handle names, addresses, phones, passports, INN, SNILS, bank cards and other entities. It replaces detected PII with structured XML-like tags that preserve grammatical information such as gender and entity ID, allowing models to generate coherent responses that are later restored with real values. The hybrid pipeline first applies normalization, pattern matching, Luhn and weighted checksum validation, and context windows with positive and negative keywords, then merges results with model predictions via an arbitration module. Evaluation on four public datasets, including Hivetrace, alexen2 and alrosait, shows PII-Guard outperforming other open solutions on both strict span matching and type-overlap micro-F1 metrics. The project, including datasets and code, is available on GitHub and aims to reduce leakage risks while maintaining downstream model utility.