Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7
Tag: browser (3 articles)Clear

148 npm packages posed as student proxies to turn browsers into a DDoS botnet

Researchers at JFrog found 148 npm packages that abused the registry not to attack developers but as free hosting for a booby-trapped web proxy aimed at students trying to bypass school filters. Anyone who opened one of the proxy sites had their browser quietly conscripted into a distributed denial-of-service botnet, flooding target servers with HTTP and WebSocket traffic, alongside injected ads and tracking. Crucially, the packages contained no install-time scripts and were never meant to be added to a project, so dependency scanners and install sandboxes, which watch what runs on install, would not catch them. The operators can re-arm the dormant attack code with a single commit.

Check
Consider that npm and similar registries can host malicious web content, not just installable code; watch for browsers reaching proxy or tutoring-themed sites backed by package registries, and block known campaign domains.
Affected
Anyone, especially students, who visits one of these registry-hosted proxy sites; their browser is silently used to launch denial-of-service attacks, while organizations may see the resulting traffic from their networks.
Fix
Block the campaign's known package and domain indicators, educate users that free web proxies can weaponize their browsers, and treat public package registries as potential malware-hosting infrastructure, not just a dependency source.

Opera GX flaw let malicious sites silently install mods to steal page data

Researchers found a flaw in Opera GX, the gaming-focused version of the Opera browser, that let a malicious website silently install a browser add-on, known as a mod, and use it to pull specific data from the pages the victim later visited. In a proof of concept, they reconstructed a signed-in user's full Gmail address from a single visit, with no clicks required. The issue stemmed from how the browser handled automatic mod installation, giving a hostile page more power than it should have. Opera has patched the flaw and says it found no evidence of exploitation before the fix, but users should update.

Check
Confirm that Opera GX is updated to the patched version anywhere it is used, and review which browser mods or add-ons are installed for anything unexpected.
Affected
Users of Opera GX before the patch; a malicious website could silently install a mod and use it to read data from other sites the victim visited, with no interaction.
Fix
Update Opera GX to the patched version, review and remove unfamiliar browser mods, and in managed environments control which browser extensions and mods can be installed through policy.

Google leaks unfixed Chromium flaw - Service Workers run JavaScript after browser closes, enabling silent botnet on Chrome, Edge, Brave

Google has accidentally published the technical details of an unfixed Chromium vulnerability that lets a malicious webpage run JavaScript on a visitor's device even after the browser is closed. The issue, originally reported by researcher Lyra Rebane in December 2022, abuses a Service Worker download task that never terminates. It was marked 'fixed' on February 12 and the bug tracker went public on May 20 after the 14-week visibility timer expired, but Rebane re-tested the latest Chrome Dev 150 and Edge 148 and confirmed the bug still works. Microsoft Edge no longer shows a download prompt, making the persistence completely silent. All Chromium-based browsers are affected.

Check
Inventory Chromium-based browsers (Chrome, Edge, Brave, Opera, Vivaldi, Arc) and check current Service Worker activity at chrome://serviceworker-internals/ for unexpected background fetches surviving browser close.
Affected
All Chromium-based browsers including Chrome Dev 150 and Edge 148 (and earlier). Confirmed bug in Service Worker handling. The Edge variant is silent (no download prompt).
Fix
No vendor patch yet. Until one ships: enforce a Chrome/Edge policy that blocks background-fetch or restricts service-worker scopes. Educate users to manually unregister Service Workers via chrome://serviceworker-internals/.