Is Browser Security Plus safe?
Browser Security Plus is medium risk. When admin policy enables upload monitoring, Browser Security Plus injects a script into every page replacing attachShadow, intercepting shadow DOM creation, including closed roots. toString() returns the native string to evade detection.
Who publishes itmanageengine.com - 3 other listings from the same operator, none carrying a finding
manageengine.com - 3 other listings from the same operator, none carrying a finding
Same store account
3 other listings published from this account, 200k+ users between them, none of them carrying a finding.
Shared hosts - 1 hostname
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
Browser Security Plus findings
Shadow DOM API Patched to Intercept Closed Shadow Root File Selections
When admin policy enables upload monitoring, Browser Security Plus injects a script into every page replacing attachShadow, intercepting shadow DOM creation, including closed roots. toString() returns the native string to evade detection.
What actually happens
An administrator enables upload monitoring via the Browser Security Plus management policy.
Browser Security Plus injects a content script into the JavaScript main world of every page that replaces the browser's shadow DOM API with a patched version.
The replacement intercepts closed shadow roots, which are normally inaccessible to outside scripts, and attaches file-selection listeners inside them.
File metadata read from every closed shadow root file input
- File nameQ4-board-deck-DRAFT.pdf
The exact filename of the file you are selecting for upload.
- File size (bytes)3145728
The byte size of the file.
- MIME typeapplication/pdf
The format type of the file, identifying whether it is a PDF, spreadsheet, image, and so on.
- Last modified timestamp1750422912000
When the file was last changed on your device, in milliseconds since Unix epoch.
- Page URLhttps://app.example.com/documents/upload
The URL of the page where the file selection occurred.
The code that does this
The attachShadow replacement and its toString disguise (shadowhook.js, lines 24-50):
Annotated: what each section does
// (1) Save the real browser function before replacing it.var originalAttachShadow = Element.prototype.attachShadow;// (2) Replace the global function with a wrapper that runs in the page's// own JavaScript context (MAIN world). Every call from the page or// any framework goes through this wrapper.Element.prototype.attachShadow = function(init) { var shadow = originalAttachShadow.call(this, init); // call the real API allShadowRoots.set(this, shadow); // record it (open and closed) // (3) For closed roots: immediately attach change listeners so that // file inputs inside them are visible to the extension. // Normally a closed root returns null to all outside accessors; // the WeakMap retains the reference anyway. if (init.mode === 'closed') { processShadowRoot(shadow); } return shadow; // caller receives the real shadow root unmodified};// (4) Override toString on the wrapper via Object.defineProperty.// When JS frameworks (Lit, Polymer, etc.) call// Element.prototype.attachShadow.toString() to verify the function// has not been replaced, they receive the original native string// ('function attachShadow() { [native code] }') rather than the// wrapper source — concealing the replacement from those checks.try { var nativeStr = originalAttachShadow.toString(); // capture original string once Object.defineProperty(Element.prototype.attachShadow, 'toString', { value: function() { return nativeStr; }, // always returns native string configurable: true });} catch(e) {}Check if you're affected
Checks whether Browser Security Plus has replaced Element.prototype.attachShadow on the current page. Uses Function.prototype.toString.call() to bypass the extension's toString disguise and reveal the wrapper function source.
- Chrome with Browser Security Plus installed and upload monitoring policy active
// bsp-shadowhook-detector.js// Detects whether Browser Security Plus has replaced Element.prototype.attachShadow.//// The extension overrides attachShadow.toString() via Object.defineProperty so that// calling Element.prototype.attachShadow.toString() returns the native browser string// even though the function is a wrapper.//// Detection: Function.prototype.toString.call(fn) invokes the original// Function.prototype.toString — bypassing any per-property toString override —// and returns the true function source.(function() { var fn = Element.prototype.attachShadow; if (!fn) { console.log('[BSP-DETECTOR] Element.prototype.attachShadow is not present in this browser.'); return; } // Standard toString — may be overridden by the extension var visibleSource = fn.toString(); // Function.prototype.toString — bypasses per-property override var realSource = Function.prototype.toString.call(fn); var isNative = /\[native code\]/.test(realSource); var hookFlagSet = !!window.__bspShadowHookInstalled; console.log('[BSP-DETECTOR] window.__bspShadowHookInstalled:', hookFlagSet); console.log('[BSP-DETECTOR] attachShadow.toString() (may be spoofed):', visibleSource); console.log('[BSP-DETECTOR] Function.prototype.toString.call(attachShadow):', realSource); console.log('[BSP-DETECTOR] Is native?', isNative); if (!isNative) { console.warn('[BSP-DETECTOR] PATCHED: Element.prototype.attachShadow has been replaced.'); console.warn('[BSP-DETECTOR] The toString disguise is active: fn.toString() returns native string but Function.prototype.toString reveals the wrapper.'); } else if (hookFlagSet) { console.warn('[BSP-DETECTOR] Idempotency guard is set but attachShadow appears native — unexpected state.'); } else { console.log('[BSP-DETECTOR] NOT PATCHED: attachShadow is the native browser function.'); }})();- 1Open any page in Chrome with Browser Security Plus installed.
- 2Open DevTools (F12) and switch to the Console tab.
- 3Paste and run this script. It prints whether the native API has been patched and, if so, shows the wrapper source.
What Browser Security Plus can do
Permissions this extension asks for, as declared in version 3.2.15. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on every site you visit
<all_urls>
See, disable and uninstall your other extensions, including your security ones
management
Watch every request your browser makes
webRequest
Talk to a program installed on your computer, outside the browser's sandbox
nativeMessaging
Change your browser's privacy and security settings
privacy
Change per-site browser settings such as cookies, JavaScript and camera access
contentSettings
Start, monitor and manage your downloads
downloads
Run its own code inside the pages you visit
scripting
See the address and title of every tab you have open
tabs
See every page you navigate to, as you navigate to it
webNavigation
Browser Security Plus version history
2.30
Mar 4, 2026
+12 more
3.2.13
Oct 21, 2026
3.2.14
Nov 6, 2026
3.2.15
Nov 13, 2026
Chrome Web Store listing
- Versions
- 3.2.15 latest of 16 seen since March 4, 2026
- Store rating
- 1.5 from 24 ratings
- Last updated
- October 21, 2026
- Size
- 261 KiB
- Privacy policy
- www.manageengine.com
