Last week, while debugging ad scripts, I nearly turned my own browser into a test sample
Last Tuesday at 10 p.m., I was in a shared workspace in Hangzhou, using uBlock Origin to inspect a client landing page. As my cursor moved across the page and the element picker opened, the browser tab suddenly went blank. My first thought was that I had installed the extension incorrectly. After restarting, I realized this was not an ordinary page error but a risk publicly disclosed by a security researcher: a malicious page could trigger a generic script attack through the element-picking flow. It may not steal your online-banking password, but “it is just an ad blocker” is not a good enough excuse either. This was also my first encounter with such a deeply hidden issue, and I rarely even check extension permissions.
The problem was hiding behind the act of clicking a page element
uBlock Origin’s element picker lets you select a button or pop-up on a page like you would marquee-select an image, then generate a blocking rule. It sounds convenient, and people do use it. Security researcher Alex Brubaker publicly demonstrated the issue on his website, iter.ca; in December 2025, people in the Hacker News community also discussed its impact across several browsers. The key point is not that “the extension is completely unusable.” Rather, a malicious page may have a chance to insert a script while you are selecting an element, turning a flow that should only view the page into something else. A typical solo founder’s routine looks like this: open an unfamiliar client dashboard, click an ad, generate a cleanup rule—and inadvertently create the opportunity.
Today’s replication: 0 yuan, about 20 minutes, no coding required
Replicating the verification costs 0 yuan and takes about 20 minutes. The technical barrier is simply knowing how to find the browser extension list and operate its buttons. First, open the browser you normally use, click the puzzle-piece extension button in the upper-right corner, find uBlock Origin in the list, open “Details,” and pause or uninstall it. See whether the tab returns to normal. While you are there, delete site data associated with uBlock, then confirm the version on the extension’s official update page; do not reinstall it from an unfamiliar download site in search results. For us, this is not an exam requiring immediate deep research into vulnerabilities. It is one extra layer of protection around a routine task. You could also use a second browser without important logged-in accounts as a control, but I made a mistake before: I tested directly in my main browser, where client data was stored, then spent an extra half hour clearing login sessions.
Match the response to your business stage, rather than jumping to a complex fix
If you are just starting out and your browser mainly holds web forms and free tools, pause the element picker, keep using ordinary ad blocking, and observe for a few days. There is no need to deal with it immediately, but avoid using it on unfamiliar pages. If you already have one or two clients, I would keep uBlock in a separate browser profile, away from accounts, online banking, and client dashboards, and check its version and permissions once a week. If you are scaling, sharing devices, or giving a team access to ad backends, I would create a version and permissions inventory for the extension and prepare a backup browser without extensions. Not everyone needs this tool, and nobody should panic and switch tools because of one security story. What we really need to do is know what happened, keep the blast radius small, and know when to stop clicking.