Fake PDF and search tools hijacked searches for 13.4 million Chrome users
Socket tied 319 mostly unlisted Chrome Web Store extensions, promoted by ads, to query proxying toward Yahoo or Bing.
Socket tied 319 mostly unlisted Chrome Web Store extensions, promoted by ads, to query proxying toward Yahoo or Bing.
Anthropic says the model made five exploits, including Android data theft and Linux root code execution; vendors have patched.
Socket says operators swapped the default search engine and proxied queries for Bing and Yahoo referral payments; most listings are now gone.
Debugging protocols, in-browser agents and WebMCP can act inside signed-in sessions that logs may attribute to the user.
The decade-long set is linked to about 13.4 million reported users, a cumulative figure rather than current infections.
Extensions redirect user searches via proxies to Yahoo or Bing for referral revenue, exposing queries without invasive scripts.
October 27–28 session titles name Skia, Telegram stickers and Muse Spark, but list no CVEs, versions or confirmed attacks.
The US rollout covers desktop, Android, and iOS when Personal Intelligence is on, and users can disable it.
Optional US suggestions may include confirmation numbers, membership IDs, addresses, phone numbers, and card numbers.
Canadian advisory AV26-1095, dated October 28, tells users to install the Stable Channel updates.
Stable builds move to 156.0.8078.73/.74 on Windows and Mac and 156.0.8078.73 on Linux, with no exploitation stated.
CVE-2026-118306 can run arbitrary code outside Chrome's sandbox from a crafted HTML page; no in-the-wild exploitation is mentioned.
Vendors were notified first; Chrome 156 fixed 62 CVEs, and the Linux root flaw is CVE-2026-98432.
Anthropic says the lab-only chains were reported first and fixed, including Chrome 156, with no real-world incidents.
Google shipped 52 fixes, four rated Critical, and Mozilla fixed 167 bugs; both credited AI-assisted bug finding.
Lab proofs, not live attacks, covered Chrome 156, iOS 26.5.2, Windows CVE-2026-33096, and Linux CVE-2026-98432.
Google assigned 62 critical or high Chrome CVEs, patched as of Chrome 156; Apple and Google say the Safari and Android issues are fixed.
In six months BigSleep reported 45 V8 vulnerabilities to Fuzzilli's 37, and experiments put theoretical overlap near 60%.
Eight intermediate keys were trivial values; browsers blocked them, and the firm says nothing was breached.
Eight intermediate keys were integers below 256, one of them 4; major browsers blocked the certificates within days.
Nearly 95% of desktop users see no HTTP warning in a week; intranet and local IPs are exempt.
Enhanced Protection now scores pages with a server-side Gemini model and warns before copied ClickFix commands run.
Server-side Gemini scam checks and ClickFix clipboard warnings are Enhanced Protection features; HTTP prompts are now default for everyone.
Scam scoring moved to a server-side model for every Enhanced Protection user, with separate suspicious-site warnings and ClickFix command checks.
Eight intermediates from an April 2025 ceremony used keys under 256; browsers blocked them, and about 30,000 customer certificates need replacement.
Fixed builds are 156.0.8078.47 on Linux and 156.0.8078.47 or .48 on Windows and Mac; Google does not report active attacks.
Eight April 2025 intermediates, also cross-signed by Sectigo, used P-384 private keys of one byte.
Enhanced Protection adds scam scoring, separate suspicious warnings, and clipboard checks for ClickFix commands.
Canadian Cyber Centre advisory AV26-1069 covers Windows, Mac, and Linux Stable Channel releases as of October 20.
Copied commands are scrubbed and checked by Safe Browsing, and Chrome is also expanding scam and financial-ad checks.
Six critical issues are included; Google does not say any are exploited, and stable builds are 156.0.8078.47/.48.
Linux builds are 156.0.8078.47 and Windows and macOS builds are 156.0.8078.47 or .48; exploitation is not addressed.
Eight April 2025 intermediates used near all-zero keys; browsers blocked them between October 17 and October 20.
All eight P-384 private keys were integers below 256 and could be recovered from public certificate data.
The linked Neowin page returned only a Cloudflare bot check, so the clipboard claim is unverified here.
Eight April 2025 intermediates used private keys smaller than 256; no abuse is evidenced, but many trust stores needed updates.
Six keys issued website TLS certificates and two were for code signing; fraudulent issuance is unconfirmed.
Eight intermediates chaining to major browser roots were blocked; attacks on users are not confirmed.
Whether Edge, Internet Explorer, cURL, and other private root stores still trust eMudhra is unconfirmed.
Chrome and Firefox blocked the TLS intermediates within hours of an October 17 report, and no website certificate chaining to them was in Certificate Transparency beforehand.
Entities are extracted by the model from each article. First seen , last mentioned . Watching keeps it in this browser only (no account); the watchlist page and dashboard alerts use it.
Today 2.1K readers · 11K views · 8.7K reads · all time 157K views