Back to feed
Dev.to
Dev.to
7/13/2026
ModHeader removed from Edge store after malware flag — a guide to auditing header-editing extensions

ModHeader removed from Edge store after malware flag — a guide to auditing header-editing extensions

Original: ModHeader was flagged as malware and pulled from Edge — here's how to audit any header-editing extension before you trust it

Short summary

Microsoft removed ModHeader from the Edge Add-ons store after Google flagged build 7.0.18 as malware containing a hidden data-collection module disguised as a date-formatting library. The article provides a practical audit checklist for header-editing extensions: check permissions, inspect service worker network requests, look for suspicious bundled dependencies, and prefer declarativeNetRequest over raw webRequest. The author maintains Header Relay, a competing extension, and discloses this bias.

  • ModHeader build 7.0.18 contained a hidden data-collection module flagged as malware
  • Audit checklist: check permissions, inspect background network requests, scrutinize bundled dependencies
  • Prefer declarativeNetRequest API and extensions with transparent captured-value visibility

Generated with AI, which can make mistakes.

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more