verification process

AppWizard
July 31, 2026
Bitsight's investigation revealed that inexpensive Android TV boxes are being shipped with applications that can change their hardware identity, allowing them to impersonate popular smartphone brands like Samsung and Huawei. This operation, named Fuyao, is linked to Zhejiang Fengwo IoT Technology Co., Ltd., a Chinese company established in 2019. The H96MAXV11 model was frequently reported among the affected devices. In one day, the operation received 65,957 reports from about 38,000 unique MAC addresses, with many devices misidentified as phones due to spoofed identifiers. Fengwo has also promoted over 120,000 "AI digital humans," though details on this marketing term are vague. The command-and-control server for Fuyao sends phone profiles to devices, masking their actual hardware specifications. The operation uses machine vision technology and a YOLOv8s object-detection model to identify advertisements. Bitsight documented 40 fraud tasks, 21 unique campaigns, and 166 modules across four devices. The operation's payout structure involves 144 operator-owned domains, with an estimated gross return of .25 per device daily, potentially leading to annual revenues in the millions. Attribution to Fengwo is supported by shared TLS certificate data and public patent records, although the patents do not directly address advertising. There is uncertainty about how the fraudulent apps were installed and at what point in the supply chain they were introduced. Device owners are advised to verify Play Protect certification and disconnect suspicious devices.
AppWizard
July 30, 2026
Google has announced the global rollout of its Age Signals API for the Google Play platform, aimed at helping parents manage age-appropriate content for their children across Android applications from a single interface. Initially launched in Brazil, the tool will be extended to users in Australia and Canada by mid-August, with a full worldwide release expected later this year. The Age Signals API allows developers to customize in-app experiences based on the user's actual age, moving away from generic safety measures. Developers receive age range signals to adjust content and features accordingly, while adult users can voluntarily share their age range. Parents can centralize control through the Google Family Link app, sharing their child's age range once for automatic communication to participating apps. Age data is not shared by default, and parents can modify permissions at any time. The API enhances existing safety tools on Google Play, including mandatory standards for family-friendly apps and features in Google Family Link.
Winsage
July 29, 2026
Microsoft is requiring the use of TPM 2.0 security modules for Key Management Service (KMS) activation servers to combat unlicensed software and corporate piracy. KMS, used by organizations for mass activation of devices, has been targeted by hackers who create counterfeit servers. The new protocol mandates that KMS hosts validate their hardware credentials through the TPM 2.0 chip before activating client devices. This initiative will mainly affect illegal infrastructures in the corporate sector, while legitimate PC users will not be impacted. Starting in August 2026, Windows Server 2025 will introduce hardware readiness alerts to help system administrators prepare for these changes. TPM 2.0 has been required for Windows 11 since 2021, and its application is being expanded to address vulnerabilities in volume licensing.
Winsage
July 12, 2026
Raymond Chen, a Microsoft engineer, revealed that Windows 95 identified installation programs by analyzing executable filenames against a list of keywords, including "setup," "install," and "inst." The system would then initiate a routine to repair any compromised system files. The list included six terms: setup, install, inst, imposta, ayarla, and felrak. Chen noted redundancy in the list, suggesting "install" was unnecessary since it included "inst." For executables not matching the terms, Windows 95 scanned the executable's path for "Setup." The system maintained backup copies of frequently overwritten files in a hidden directory at C:WindowsSYSBCKUP and would restore correct versions after installers completed. File verification was often postponed until the next system boot, especially for installers that reverted to MS-DOS for file replacements. This file repair mechanism continues to influence modern operating systems, including Windows 11.
Search