Res-block: Extension Resources Block Attack on Chrome’s Incognito Mode

Piyush Raj ~ Rex
4 min readSep 16, 2020


Res-block Attack

This attack can be used to detect if victim is using incognito mode in latest version of Chrome (77.0.3865.90) by the time of discovery by me exactly a year ago in Sept 2019 by abusing web_accessible_resources. The research can be find over 0x48piraj/PwnHouse.

Anatomy of res-block attack

Sometimes developers share package resources of their Chrome extension, for example, images, HTML, CSS, or JavaScript and make them available to web pages. They do this via utilizing web_accessible_resources.

As per Chrome’s documentation,

An array of strings specifying the paths of packaged resources that are expected to be usable in the context of a web page. These paths are relative to the package root, and may contain wildcards. For example, an extension that injects a content script with the intention of building up some custom interface for would allow any resources that interface requires (images, icons, style-sheets, scripts, etc.) as follows:

"web_accessible_resources": [

More info can be found over Chrome’s Manifest — Web Accessible Resources documentation.

These resources then become available in a webpage via the URL chrome-extension://[PACKAGE-ID]/[PATH], which can be generated with the extension.getURL method. Allow-listed resources are served with appropriate CORS headers, so they're available via mechanisms like XHR.

The documentation goes on and states that some work has already been done previously focusing on different domain utilizing web accessible resources as the blob states:

Prior to manifest version 2 all resources within an extension could be accessed from any page on the web. This allowed a malicious website to fingerprint the extensions that a user has installed or exploit vulnerabilities (for example XSS bugs) within installed extensions. Limiting availability to only resources which are explicitly intended to be web accessible serves to both minimize the available attack surface and protect the privacy of users.

The Vulnerability

During my research, what I found interesting was that, these paths chrome-extension://[PACKAGE-ID]/[PATH] were not available to incognito mode, maybe it is because Chrome by default blocks extensions in incognito mode because it can't guarantee that the extensions aren't tracking one's data.

This actually opened a loophole. What if one scans for popular extensions which had web_accessible_resources parameter in their Manifest and then tries to access those one by one?

Testing the waters

Let’s test this with Wappalyzer chrome-extension as I know it has web_accessible_resources in it’s Manifest by looking at it’s source. I chose to go with this chrome extension because I’ve dealt it’s code-base in past during one of my other research which ended with me giving a talk at BSides Delhi 2019.

"web_accessible_resources": [

The path seems to be js/inject.js, now to find the [PACKAGE-ID], we can just visit chrome://extensions, switch to Developer mode, see extensive details about extensions.

NOTE: As the [PACKAGE-ID] is constant through-out, it is a reliable attack vector.

Final Payload


As expected, now, let’s test this over incognito mode,

Aha! It shows an error with code ERR_BLOCKED_BY_CLIENT or say, Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.

To make a proof-of-concept exploit, we can just use <script> with src tag to load target resource and,

  • if it loads successfully, we’re not into incognito mode.
  • if the page can’t load, we definitely are.

POC (proof-of-concept) for Wappalyzer chrome-extension installed,

<script src="chrome-extension://gppongmhjkpfnbhagpmjfkannfbllamg/js/inject.js"></script>

We can see the error again, programmatically,

So now, we just need to detect this error to tell if an user is using Incognito mode or not. We can use any of the two events here to detect the Incognito mode:

  • onload – successful load.
  • onerror – an error occurred.

Chaining for the win

This bug got far more interesting when I found web_accessible_resources in chrome-extensions which come pre-installed in every Chrome web-browser.

This discovery makes this bug very exploitable.

The dump of pre-installed Chrome extensions on latest version 77.0.3865.90 can be found over here.

The chrome-extensions which have web accessible resources:

You can find the final proof-of-concept exploit over 0x48piraj/PwnHouse/../resblock/res-block-poc.html.





Piyush Raj ~ Rex

Google Code-In C. Winner. GsOCer ‘19. Independent Security Researcher. Have hacked Medium, Mozilla, Opera & many more. Personal Website: