Background

Google Accidentally Exposes 3-Years-Old Chromium Browser Bug That Could Turn Browsers Into Silent Botnet Proxies

Chromium bug

A serious security issue in Chromium-based browsers has drawn widespread attention after Google inadvertently exposed details of a long-standing and still-unfixed vulnerability.

What began as an internal bug report turned into a public concern when information about the flaw, including proof-of-concept exploit code, briefly appeared on the Chromium issue tracker before being pulled. Although the company quickly restricted access again, the details had already spread, leaving millions of users potentially at risk while a proper patch remains unavailable.

The vulnerability centers on the Background Fetch API, a legitimate feature designed to let browsers continue downloading large files or videos even after a user closes a tab or the entire browser window.

Security researcher Lyra Rebane first reported the issue privately in late 2022, highlighting how malicious websites could abuse this mechanism.

By using clever JavaScript and service workers, attackers can keep code running in the background indefinitely, creating persistent connections that survive browser restarts and sometimes even device reboots.

In some browsers like Microsoft Edge, the process can occur almost silently without obvious pop-ups or warnings, making it especially stealthy.

This flaw does not grant full control over a device or access to personal files, emails, or the operating system. Instead, it turns a user's browser into a lightweight participant in a potential botnet.

Compromised devices could relay traffic anonymously, contribute to distributed denial-of-service attacks, or serve as proxies for other malicious activities.

While building a massive network would require significant effort, even smaller-scale exploitation is relatively straightforward once the code is public, and the invisible nature of the background activity means most people would never notice anything unusual happening on their phones or computers.

What makes the situation more troubling is the length of time the vulnerability went unaddressed.

Reported over three years ago, it was internally rated as high priority by Google engineers yet lingered without a fix. The bug tracker entry had even been marked as resolved at one point, which led to the accidental public exposure when access restrictions were lifted.

As of now, the vulnerability affects virtually all Chromium-based browsers, including Google Chrome, Microsoft Edge, Brave, Opera, Vivaldi, and others, putting billions of users worldwide in the crosshairs. Firefox and Safari remain unaffected since they do not rely on the same engine.

Google has acknowledged the leak and stated that work on a fix is underway, but no timeline has been provided and no emergency update has rolled out yet.

In the meantime, users are advised to exercise caution when visiting unfamiliar websites, avoid clicking suspicious links, and keep their browsers updated in hopes that a patch arrives soon.

This incident serves as a stark reminder of how even well-intentioned browser features can be twisted for harm when left unresolved, and it underscores the importance of prompt attention to security reports in an ecosystem that powers so much of our daily online activity. Until the patch lands, staying vigilant remains the best defense against this lingering threat.

Published: 
22/05/2026