Yandex Drops Earbuds Under X-Ray Microtomography: Detailed Internal Analysis of First AI-Powered TWS Headphones
Yandex marked its birthday by allowing engineers to run its first AI earbuds, Yandex Drops, through a high-resolution X-ray microtomograph. The non-destructive scan produced two voxel datasets—one of the charging case with an earbud inside and one of a standalone earbud—capturing internal structures at 24.44 µm and 14.12 µm resolution respectively.
The earbuds contain an eight-layer HDI PCB with blind vias, a QFN-packaged central SoC approximately 2.8 × 2.0 mm that is presumed to house the NPU for always-on voice detection, and a smaller companion QFN die likely serving as memory or PMIC. A 4 × 4 BGA flash-memory candidate sits adjacent to the main processor.
Each earbud integrates three microphones: two external feedforward sensors positioned at the stem ports and one internal feedback microphone located roughly 5 mm from the driver diaphragm. Signal routing was traced from the MEMS elements through spring connectors and flex cables to the main board without any visible hardware switch or disconnect in the accessible layers.
The 11 mm dynamic driver and 46 mAh pouch cell were measured directly from the calibrated slices, matching the manufacturer’s specifications. The charging case houses a 520 mAh cell, USB-C receptacle, and a three-pin Hall-effect sensor on a flex tail that detects lid position; no shielded radio module was observed inside the case.
Capacitive touch electrodes are formed by stamped metalization on the inner surface of the stem, while a miniature SMD tactile switch on a daughter board provides physical button input. Charging contacts on the earbuds are spring-loaded claws that mate with corresponding pads inside the case.
All imaging was performed at the PRODIS facility using a 2 µm-resolution microtomograph; reconstruction and multi-volume analysis were carried out in the Russian-developed VolÅn software. The authors note that while the physical microphone traces appear continuous, any determination of what audio is actually transmitted requires separate RF traffic analysis.
Related articles
Securing 1C Web Client Access with External MFA via Nginx, Keycloak and Active Directory
A detailed implementation separates user browser access from integration traffic by placing MFA enforcement on an external Nginx and Keycloak layer while preserving the original IIS endpoints for automated systems. The architecture uses a new IIS server for employees only, with oauth2-proxy handling OIDC flows against Keycloak federated to Active Directory. Access is restricted to members of a dedicated AD group such as 1C_Web_2FA, and TOTP serves as the second factor. Existing integrations continue to reach the legacy IIS directly from whitelisted IP addresses without triggering interactive authentication. The solution avoids 1C OpenID Authentication, keeps native 1C login intact, and supports desktop shortcuts that launch the web client in a dedicated browser window. Network controls ensure the new IIS cannot be reached directly from the internet, preventing bypass of the MFA gateway.
Avanpost Unveils DAG System for Sensitive File Discovery and Excessive Access Rights Management
Avanpost has launched its new DAG solution designed to control access to unstructured data across file servers, cloud environments, and corporate knowledge bases. The system scans file contents to identify confidential information, maps actual user permissions, and highlights policy violations that official regulations often overlook. Built-in workflow automation routes access review requests to data owners, collects approvals, assigns remediation tasks to IT teams, and verifies changes through follow-up scans. DAG integrates with existing IdM/IAM platforms to factor in employee roles and employment status, automatically triggering access reviews during job changes or terminations. The platform also forwards detected violations to SIEM and SOAR systems for coordinated response and supports both high-load enterprise deployments and simpler mid-market installations. Customers can request on-site pilots to evaluate the solution against their current infrastructure.
Why Complex Password Policies Fail to Protect Companies: Practical Account Security Guidance
Many organizations implement strict password rules requiring at least eight characters with numbers, uppercase letters, and special symbols, plus mandatory changes every 30 days. Employees respond by creating predictable variations such as Company2026!, Company2026@, and Company2026#, which offer little real protection against phishing or credential stuffing. The core issue lies in poor visibility into all accounts across Active Directory, VPN, cloud services, databases, and contractor access rather than password length alone. Effective security begins with full inventory of every account, classification into user, privileged, service, and external types, and clear ownership assignment. Privileged accounts require separate credentials, MFA, minimal rights, and activity logging, while service accounts must avoid hardcoded secrets in configuration files or source code. Password managers must enforce client-side encryption so that even compromised administrator accounts cannot access stored secrets. MFA deployment should prioritize high-risk entry points such as VPN, email, and backup systems, and access revocation must integrate with HR processes to prevent former employees or contractors from retaining credentials.
Wireshark Wi-Fi Traffic Analysis: Diagnosing Connectivity Failures in 802.11 Networks
Wireshark captures help distinguish between radio-layer issues, DHCP failures, and application-layer problems when a device connects to Wi-Fi but cannot load pages. The guide explains how to select the right capture point—client, monitor-mode adapter, or wired side of the access point—and why ordinary Ethernet headers often hide critical 802.11 management and control frames. Detailed sections cover CSMA/CA contention, frame types (Management, Control, Data), EAPOL-Key exchanges for WPA2-Personal, and the limitations of retry flags as loss indicators. Practical Linux commands using iw, dumpcap, and NetworkManager demonstrate how to enable monitor mode on channel 6 HT20 and record a two-minute trace. Filters for wlan.addr, eapol, and wlan.fc.retry allow analysts to isolate association failures, key-handshake problems, or DHCP delays. The article also addresses decryption of WPA2 traffic with a known passphrase and warns that Wireshark cannot replace a spectrum analyzer for detecting non-Wi-Fi interference.