Researchers Push Over 2 Million Updates to Remotely Disable Popcorn Time Updater That Could Fuel a Botnet

thehackernews.com Oct 25, 2026

Researchers Push Over 2 Million Updates to Remotely Disable Popcorn Time Updater That Could Fuel a Botnet

Curated by Shubham · TechCapsules · Oct 25, 2026

AI-summarised brief · reviewed before publication

Between November 2025 and March 2026, Dutch security firm Eye Security executed Operation IXIM, pushing more than two million updates to computers it did not own to disable the background updater of Time4Popcorn, an abandoned fork of the pirated‑streaming app Popcorn Time. The updater, Updater.exe, contacted unregistered domains, allowing any registrant to deliver arbitrary code with SYSTEM/root privileges. Eye’s threat hunt recorded over 3.8 million hardware IDs, estimating 2.5‑3 million Windows and 250‑350 thousand macOS machines were vulnerable, including home users and devices on government, military and corporate networks. After disclosing CVE‑2026‑30612 in June, Eye legally repurposed the updater to shut itself down, reducing traffic by 98 percent and handing the controlled domains to the Shadowserver Foundation for long‑term sinkholing.

💡 Why It Matters

· By forcibly neutralizing a dormant, high‑privilege updater, Eye prevented a ready‑made foothold that could have been weaponized into a massive, cross‑sector botnet.

Capsules Cybersecurity

Read full article on thehackernews.com

Gheist Uses Stolen GitHub Tokens to Steal Private Repository Secrets via Actions…

An automated campaign dubbed “Gheist” has been using stolen GitHub tokens to create malicious workflow files in private repositories and GitHub Enterprise environments. The tool opens a new branch named ci-sync‑, commits a workflow that prints every readable secret to the Actions log, downloads the log via the API, and then deletes the run. Wiz’s investigation, ongoing since September 15, identified over 13,500 such branches across more than 850 compromised accounts, ranging from personal projects to enterprise repos. GitHub’s safeguard that pauses suspicious runs only protects public repositories, leaving private and Enterprise Server instances exposed. The attack also leverages compromised AWS credentials to enumerate Secrets Manager, and a recent variant targets self‑hosted runners. As of October 24 the campaign remains active, with many compromised accounts already removed from GitHub.

💡 By exfiltrating secrets directly through GitHub’s own infrastructure, the attack bypasses traditional network defenses, giving attackers unfettered access to production credentials.

thehackernews.com · Oct 26

Microsoft 365 Token-Replay Attacks Compromise 97 Accounts at 79 Organizations

Researchers at Huntress uncovered a Microsoft 365 token‑replay campaign that hijacked sign‑in sessions and replayed stolen access tokens to infiltrate 97 accounts across 79 organizations between July 14 and September 22, 2026. The attackers used an adversary‑in‑the‑middle login page to capture credentials and MFA codes, then harvested the resulting tokens and “sprayed” them at scale, achieving 497 successful sign‑ins from over 200,000 attempts traced to the 193.26.115.0/24 subnet. After gaining access, they added rogue authenticator apps and registered 48 fake Entra devices to maintain persistence, sometimes removing existing MFA within three hours. Hidden email rules were also deployed to delete or forward messages, and compromised mailboxes were used to send spam before Microsoft Entra ID Protection flagged the accounts as high risk. The operation originated from a Romanian IP linked to the AsyncRAT‑infected hosting provider 1337 Services GmbH, which has connections to previously seized RDP rental services.

💡 By bypassing MFA through token replay, the attack demonstrates a scalable method to subvert modern authentication, forcing organizations to rethink token‑validation and device‑registration safeguards.

thehackernews.com · Oct 26

uCreator Android Spyware Can Steal Telegram 2FA Passwords and Clone WeChat Accounts

A rent‑a‑spyware kit named uCreator embeds malicious code in counterfeit copies of Telegram and WeChat, allowing attackers to hijack accounts, steal Telegram two‑factor authentication passwords, and clone WeChat sessions. The kit’s Telegram module matches the Baohuo backdoor previously reported by Doctor Web, sharing the same namespace (com.ucreator.tgjar), C2 server and command set. Infections spread via sideloaded APKs, fake app‑store sites targeting Portuguese‑speaking Brazil and Indonesian users, and a container app called “Onion Box” that runs other apps inside it. By running with the victim app’s identity, the malware can query message databases, exfiltrate phone numbers, names and passwords, and conceal attacker sessions. Samples dated July 2026 still use an older hooking engine, but the threat persists across Android 16–17 devices, with victims reported in China, the United States, India, Brazil and Indonesia.

💡 By capturing clear‑text 2FA passwords, the kit bypasses Telegram’s strongest user protection, giving attackers full control over high‑value messaging accounts and the ability to silently monitor or commandeer communications.

thehackernews.com · Oct 26

Two Critical Wasmtime Flaws Could Let Malicious WebAssembly Modules Escape Sandboxes

Two critical vulnerabilities were discovered in Wasmtime, a WebAssembly runtime used as an embeddable library, allowing malicious modules to break out of the sandbox that isolates them. Both bugs reside in Cranelift, Wasmtime’s default compiler, and received CVSS scores of 9.9. One flaw (CVE‑2026‑115889) stems from 24‑bit value fields that overflow on large functions, causing type confusion; the other (CVE‑2026‑115893) affects ARM64 br_table handling, letting an out‑of‑range index jump to unintended code. Fixed releases (36.0.19, 48.0.7, 49.0.4, and 50.0.0) were issued on October 19‑20, but only supported LTS lines receive patches; older lines, including 24.x, remain vulnerable. Because Wasmtime is compiled into services that accept third‑party modules—such as Fastly’s Compute platform—any host that does not rebuild with the patched library is exposed to arbitrary code execution.

💡 Unpatched Wasmtime instances can let attackers run native code on servers that execute user‑supplied WebAssembly, turning a sandboxed service into a full‑system compromise.

thehackernews.com · Oct 26

Unpatched Tailscale SSH Flaws Could Let a Hacked Device Reach Root on…

A security researcher disclosed a critical flaw in Tailscale SSH that allows a compromised device to obtain root access on any reachable server within the same mesh. The vulnerability, detailed in the “Tailworm” report published on October 25, requires Tailscale SSH to be configured for port forwarding and an attacker to already control a device permitted by the network’s access rules. Testing on Tailscale 1.104.2 and headscale 0.29.5 showed that an ordinary SSH session could hijack a root‑only socket, read the password file, replace sockets for command execution, and even capture enrollment keys to add malicious nodes—provided Tailnet Lock is disabled. Tailscale has acknowledged the issue, is working on a fix, and has not yet issued a CVE or advisory.

💡 The exploit turns a single foothold into rapid, password‑less root takeover across an entire private network, exposing organizations to immediate, uncontrolled lateral movement.

techcrunch.com · Oct 25

Will AI expose the rickety infrastructure of the internet?

A week‑long security alert forced millions of PHP‑based websites to patch or shut down after researchers uncovered long‑standing vulnerabilities. TechCrunch’s Equity podcast highlighted the incident as a “real reckoning moment,” noting that the flaws, discovered by human researchers aided by large language models, could be exploited by attackers worldwide. The discussion underscored the fragility of the internet’s core, built on decades‑old open‑source code, and raised concerns about future breaches as AI tools become more powerful.

💡 The episode exposes how hidden, decades‑old bugs can suddenly threaten the web’s backbone, forcing rapid, widespread remediation. It signals a shift toward proactive vulnerability hunting using AI, reshaping how developers and security teams prioritize patching in an increasingly automated threat landscape.