Google Introduces Multi-Step Verification for Android APK Sideloading to Combat Fraud
Google has started deploying a new, more complex installation process for Android applications installed outside of Google Play. One user has already received the updated interface and documented the full sequence: confirming that installation of third-party APKs is not being forced, rebooting the device, and waiting 24 hours.
The system first asks whether anyone has pressured the user to allow unknown sources. Google warns that fraudsters frequently trick victims into enabling this option, while employees of government agencies or legitimate businesses never request it.
After confirmation, the device must be restarted. The 24-hour timer appears to start once this step is completed. The remaining time is shown in settings, and normal device use remains possible during the wait.
Once the period expires, users can enable sideloading for seven days or permanently. The new flow does not apply to installations performed via ADB, leaving technically proficient owners an alternative route.
Google explains the delay as a measure against fraud, giving users time to verify whether an unknown APK is genuinely needed. However, many users fear this is only the first step toward stricter controls. In a poll by Android Authority, 88 percent of respondents predicted that Google will continue tightening the rules.
Related articles
Russian Minister Proposes Blocking All SIM Cards of Scammers Banned in MAX Messenger
The head of Russia's Ministry of Digital Development has suggested expanding account bans in the MAX messenger to include full disconnection of all mobile numbers belonging to the same owner. Maksut Shadaev stated that simply restricting the messenger account is insufficient and that operators must continue countermeasures. The proposal also includes a cooling-off period preventing the individual from registering new numbers after a ban. Details on the duration of restrictions, data transfer procedures to operators, and appeal mechanisms remain undisclosed. Questions around accurate owner identification and cases of compromised or misused numbers are highlighted as critical for implementation. The measures target fraudsters specifically and would not apply automatically to every MAX rule violation.
Avito Develops Cyberdetective Browser Game to Train Employees on Real-World Attacks Using MITRE ATT&CK Techniques
Avito security awareness specialist Ilya Nikiforov created the browser-based Cyberdetective game over 74 days to move beyond traditional courses and train practical responses to attacks. The game places players in the fictional company Lumi where they control mascot Spok the honey badger, investigating six cases based on authentic attack chains documented in MITRE ATT&CK. Scenarios cover physical access via unlocked laptops, invoice domain spoofing, voice cloning of executives, MFA fatigue attacks, and evidence preservation during incident response. The project relied heavily on AI agents including Claude Code and Codex for coding and testing while Nikiforov handled scenario design, methodology, and acceptance. Additional AI tools generated art, animations, voiceovers, and music, resulting in 80 JavaScript modules, roughly 2,200 automated tests, and 18 distinct interactive mechanics. The game emphasizes safe mistake-making, chain-of-events thinking, and specific actions such as callback verification rather than blanket refusal of all requests.
Scammers Use *#62# USSD Command to Fabricate Surveillance Claims and Steal Victims' Funds
Fraudsters are exploiting the USSD command *#62# to convince targets that their phones are being tapped, then directing them to hand over cash to supposed couriers. The scheme begins with a familiar pretext such as a doorphone replacement or parcel delivery, after which the victim is tricked into revealing a verification code that the attackers themselves sent. A fake government official then claims the victim's account has been compromised and an extremist has been granted power of attorney. Victims are instructed to visit a counterfeit state website, enter *#62#, and interpret the displayed forwarding number as proof of interception. In reality the code only reveals call-forwarding settings for when the phone is unreachable, often showing a voicemail or missed-call service number. T-Bank warns that the displayed number has no connection to surveillance and urges anyone receiving such calls to hang up and contact the real organization through official channels.
Aroshka Cloud Faces Scrutiny Over Alleged False Claims of SOC 24/7 Operations and High-End Infrastructure
StackWorks has published the fourth installment in its investigative series on Aroshka Cloud, detailing how the cloud storage provider accused the studio of orchestrating a DDoS attack shortly after the third part appeared. The service published five posts claiming technical evidence linked StackWorks to the attack, including IP traces from Moscow, Ufa, and Stavropol, while asserting that its SOC 24/7 team mitigated a 3.5 Gbit/s assault within seconds. StackWorks responded with a pre-trial claim demanding removal of the posts and a public retraction, which Aroshka Cloud rejected within seven minutes. Analysis of the provider’s own Kwork job postings reveals requests for template-based support staff, a five-VDS server pool, and later up to eight NVIDIA H200 GPUs with InfiniBand, contradicting public statements about multi-country data centers and round-the-clock security engineers. Further inconsistencies include mismatched time zones in email headers, inflated user statistics, and reliance on the BeDrive script rather than custom development. The investigation continues with plans to involve law enforcement regarding suspicious visitor logs.