No bundled code phones home
Header lifecycle logic lives in one reviewable module. It uses Chrome's declarativeNetRequest API and local storage, and does not initiate analytics or unrelated network requests.
Chrome extension security incident — July 2026
On July 3, 2026, Microsoft removed ModHeader — Modify HTTP Headers (roughly 1.6M combined Chrome/Edge installs) from the Edge Add-ons store after Google flagged it as malware. Independent researchers who examined build 7.0.18 found a hidden module, disguised as a date-formatting library, capable of collecting the domains you visit and preparing a daily encrypted upload to an external endpoint. Researchers noted the collector was dormant in the build they tested and found no confirmed evidence of data leaving a test profile — see the sources below for the full technical analysis.
Built for the same job — attaching headers to matching requests — with a narrower, inspectable data path.
Header lifecycle logic lives in one reviewable module. It uses Chrome's declarativeNetRequest API and local storage, and does not initiate analytics or unrelated network requests.
Captured header values are masked by default in the management screen and can be revealed or copied with an explicit action when you need to verify what will be attached.
Profiles, session state, and audit logs are not transmitted to the developer or unrelated services. Configured header values go only to matching target origins. See the privacy policy for details.
Capture and attachment only run for target origins enabled by enabled profiles; everything else is ignored.
Header Relay doesn't import another extension's settings — recreating a setup is quick.
Add the target origin(s) you were using before.
Anything you always sent — API keys, client IDs — becomes a Fixed Header.
Manually copying a session token or trace ID between requests? Add it as a Captured Header and Header Relay reattaches it automatically.
No. Browser extension supply-chain compromises have hit multiple tools, not just one. Treat any extension with broad host permissions and an opaque update process as a risk, and prefer ones whose data handling you can verify yourself.
It does not send data to the developer, analytics providers, or unrelated servers. Configured header values are attached only to matching target origins; profiles, session state, and audit logs remain local.
Yes — inspect network requests in Chrome DevTools while Header Relay is enabled, or read the published privacy policy and permission justifications.
Header Relay is not affiliated with ModHeader or its developer. The information above reflects third-party security research published in July 2026 — consult the linked sources for the full technical analysis.