Skip to navigation

Threat reportMalwareTL-2026-1207

StegoAd Campaign: 119 Malicious Microsoft Edge Extensions Deliver Steganographic Malware to 2.6M Users

highACTIVE

Microsoft's Edge Extensions Security Team disrupted "StegoAd," a multi-year (active since at least 2021) supply-chain campaign of 119 malicious Edge browser extensions across 90+ developer accounts, downloaded up to 2.6 million times.

Key facts

IdentifiersTL-2026-1207
Also known asStegoAd
SeverityHIGH
Affected productsMicrosoft Microsoft Edge Add-ons Store (browser extensions); Various (impersonated third-party developers) Chromium-based / Chrome and Firefox variants of the same extension codebase
Weaknesses (CWE)CWE-506, CWE-912, CWE-522
AttributionDarkSpectre (low confidence)
MalwareStegoAd
MITRE ATT&CK techniquesT1005 Data from Local System, T1008 Fallback Channels, T1027 Obfuscated Files or Information, T1036 Masquerading, T1041 Exfiltration Over C2 Channel, T1056 Input Capture, T1059 Command and Scripting Interpreter, T1070 Indicator Removal, T1071 Application Layer Protocol, T1090 Proxy, T1102 Web Service, T1105 Ingress Tool Transfer and 15 more in the attack flow
MotivationFINANCIAL
Target sectorsall sectors consumer enterprise browser users, ecommerce, content management wordpress site operators
Target regionsGlobal
Detection rules9 (1 shown free)
Sources13 cited sources

Detection coverage

As of 2026-07-11, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1207 across Splunk SPL, Microsoft KQL and Sigma, covering 24 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: StegoAd — Malicious Edge Extension Install / Masquerading as Trusted Utility

Detects installation of an Edge/Chromium browser extension matching known StegoAd extension IDs/names (ad blockers, VPNs, translators, video downloaders) or newly-installed extensions requesting broad host permissions shortly before a dormancy window, consistent with StegoAd's masquerading and supply-chain compromise pattern.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1585, T1195.001, T1036.005
  • Data sources: edge_extension_telemetry, windows_security, sysmon
  • Severity: high
  • Confidence: high

Splunk SPL

index=endpoint sourcetype="XmlWinEventLog:Microsoft-Windows-AppLocker/MSI and Script" OR sourcetype="edge:extension:install"
| eval ext_name=coalesce(extension_name, ProcessName)
| where match(ext_name, "(?i)ads?\s?block|adblock|trusted vpn|veepn|hiddence|turbo download|tiktok app for edge|ai search gpt|image downloader pro|google translate in right click")
| stats earliest(_time) as first_seen count by host, user, ext_name, extension_id
| table first_seen, host, user, ext_name, extension_id

Microsoft KQL

DeviceEvents
| where Timestamp > ago(24h)
| where ActionType == "BrowserExtensionInstalled"
| where AdditionalFields has_any ("Ads Block Ultimate", "Adblock for Youtube", "Adblocker FX", "Trusted VPN for Edge", "Hiddence VPN", "Turbo Download Manager", "TikTok APP for Edge", "AI Search GPT for Edge", "Image Downloader Pro", "Google Translate in Right Click")
| project Timestamp, DeviceName, AccountName, ActionType, AdditionalFields

Sigma

title: StegoAd-Style Malicious Edge Extension Install
id: 6f1a2b3c-0001-4a1e-9c11-3a1207001001
status: experimental
description: Detects install of an Edge extension matching a known StegoAd malicious extension name/ID
references:
  - https://microsoftedge.github.io/edgevr/posts/Inside-StegoAd-How-We-Disrupted-a-Massive-Malicious-Extension-Campaign/
author: Threadlinqs Team
date: 2026-07-11
tags:
  - attack.resource-development
  - attack.t1585
  - attack.initial-access
  - attack.t1195.001
  - attack.defense-evasion
  - attack.t1036.005
logsource:
  product: windows
  category: browser_extension_install
detection:
  selection:
    ExtensionName|contains:
      - 'Ads Block Ultimate'
      - 'Adblock for Youtube'
      - 'Adblocker FX'
      - 'Trusted VPN for Edge'
      - 'Hiddence VPN'
      - 'Turbo Download Manager'
      - 'TikTok APP for Edge'
      - 'AI Search GPT for Edge'
      - 'Image Downloader Pro'
      - 'Google Translate in Right Click'
  condition: selection
falsepositives:
  - Legitimate extensions with similar generic names published by verified developers
level: high

Known false positives:

  • Legitimate extensions sharing generic category names published by verified/vetted developers

Tuning notes: Maintain an updated allowlist of vetted publisher IDs and cross-reference against Microsoft's published StegoAd extension-ID list; tune name matching to avoid overlapping with legitimately named ad-blocker/VPN extensions from verified vendors.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • StegoAd — Steganographic PNG/WebP/WOFF2 Payload Fetch from Extension Context · unlock with TL Creds
  • StegoAd — Google/WordPress Credential and 2FA Interception via Extension Content Script · unlock with TL Creds
  • StegoAd — Bulk Cookie Collection / Session Hijack via Extension cookies API · unlock with TL Creds
  • StegoAd — Remote JS Backdoor Execution via Extension Fetched Script · unlock with TL Creds
  • StegoAd — Multi-Layer Obfuscated String Decode (Base64/XOR) in Extension Script Host · unlock with TL Creds
  • StegoAd — C2 Fallback-Domain Walk & Cloudflare Workers / GitHub Pages Fronted Beacon · unlock with TL Creds
  • StegoAd — Dormancy-Gated First Network Call 3-5 Days Post-Install · unlock with TL Creds
  • StegoAd — DevTools-Detection Anti-Analysis Behavior in Extension Context · unlock with TL Creds

Indicators of compromise

As of 2026-07-11, Threadlinqs Intelligence tracks 24 indicators of compromise for TL-2026-1207.

Sample indicators (1 of 24)

  • Domain: mitarchive[.]info

Defanged, TLP:CLEAR. Full set of 24 indicators: unlock with TL Creds.

24 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

Extensions posed as ad blockers, VPNs, translators, video downloaders, and other utilities; hid payloads inside PNG/WebP images and WOFF2 font glyph data (steganography); remained dormant 3-5 days after install with DevTools-detection and server-side validation gates; and activated in roughly 10% of installations to run ad fraud, execute arbitrary remote JavaScript, steal Google credentials and 2FA codes, harvest WordPress admin logins, hijack affiliate commissions, and exfiltrate cookies for session hijacking.

StegoAd is a long-running (since at least 2021) malicious browser-extension operation targeting the Microsoft Edge Add-ons store, disclosed and disrupted by Microsoft's Edge Extensions Security Team in June 2026 after enterprise customers reported unusual browser behavior (unexpected pop-ups, unauthorized redirects, sluggish performance) starting in early May 2026. The operation ran 119 extensions across 90+ distinct developer accounts, impersonating trusted extension categories -- ad blockers ("Ads Block Ultimate", "Adblock for Youtube", "Adblocker FX", "Adblock" as a uBlock clone), VPNs ("Trusted VPN for Edge (VeePN)", "Hiddence VPN"), translators ("Google Translate in Right Click"), video downloaders ("Free Online Video Downloader", "Turbo Download Manager", "TikTok APP for Edge"), AI tools ("AI Search GPT for Edge"), image tools ("Image Downloader Pro"), and other utility categories (color pickers, PDF editors, weather apps, bandwidth optimizers, Pomodoro timers, screenshot tools, social-media integrators, coupon tools, calculators).

The extensions delivered genuine baseline functionality to build trust and pass store review, then deployed malicious payloads three to five days post-install (a dormancy/sleeper design), with additional evasion via DevTools-detection logic (extending dormancy indefinitely if developer tools were open) and server-side request validation/fingerprint and User-Agent gating on the C2 side, so direct researcher probes returned empty responses. Execution was probabilistic -- only roughly 10% of installations ever fired the payload, limiting exposure to automated analysis and complicating detection.

The steganographic delivery chain evolved over time as Microsoft's detection improved: early variants appended JavaScript after the IEND marker of PNG icon files bundled with the extension; the operators then moved to fetching external PNGs from C2 servers, then to WebP image containers, and finally to WOFF2 web-font files with code hidden in glyph ranges disguised as Asian-language text or font metadata. Retrieved payload strings were further multi-layer obfuscated using character case-swaps, digit-swaps, Base64 encoding, and XOR. The operators successfully ported the extension codebase from Manifest V2 to Manifest V3 as Chromium deprecated the older extension platform, indicating sustained active maintenance.

Microsoft's analysis attributes at least 10 distinct malicious modules to the retrieved payloads: Google credential and second-factor (2FA) code interception at sign-in, WordPress administrator credential harvesting, bulk cookie collection/exfiltration for session hijacking, a remote-code-execution backdoor that executes arbitrary JavaScript pushed from C2, ad injection/ad fraud, affiliate-commission hijacking targeting Amazon, eBay, and AliExpress referral links, search-result redirection, and competitor-extension targeting/removal. Covert telemetry was routed through at least seven distinct Google Analytics tracking IDs, giving the operators real-time dashboards on infected populations. Command-and-control relied on 10+ domains organized by function with automatic failover, fronted in part through Cloudflare Workers, with additional beacon/telemetry traffic abused through GitHub Pages hosting. One credential-exfiltration domain identified in follow-on reporting is mitarchive[.]info, associated with a broader operation Microsoft describes as sharing infrastructure, hashing/debug-string patterns, AdSense publisher IDs, and Analytics properties across all 119 extensions despite the 90+ separate developer accounts -- consistent with a single actor rapidly recreating suspended accounts. A BeaconBeagle infrastructure-correlation check on mitarchive[.]info returned no additional C2 configuration matches at the time of this research (2026-07), indicating either fresh/rotated infrastructure or a domain not yet indexed by that source.

Security researchers (via The Hacker News and Rescana reporting) have flagged methodological overlap -- identical icon-based steganography, overlapping extension naming conventions (e.g. "Ads Block Ultimate"), and shared credential-exfiltration infrastructure -- with a cluster tracked as DarkSpectre, and noted similarity to prior campaigns dubbed ShadyPanda and GhostPoster. Microsoft has not officially confirmed attribution to any named actor or nation-state as of the June 2026 disclosure. No CVE applies; this is an abuse-of-platform / malicious-extension supply-chain campaign rather than a software vulnerability. Microsoft removed all 119 extensions from the Edge Add-ons store, suspended 90+ developer accounts, published extension-ID indicators for user self-check (edge://extensions), and deployed dynamic C2-response analysis plus steganographic content scanning for future store submissions. Reporting notes the malicious codebase also produced Chrome- and Firefox-targeted variants, so remediation guidance extends beyond Edge, and the operator is assessed to remain active post-disruption.

MITRE ATT&CK techniques by tactic:

Collection

T1005 Data from Local System; T1119 Automated Collection; T1185 Browser Session Hijacking

Command and Control

T1008 Fallback Channels; T1071 Application Layer Protocol; T1090 Proxy; T1102 Web Service; T1105 Ingress Tool Transfer

Defense Evasion

T1027 Obfuscated Files or Information; T1036 Masquerading; T1070 Indicator Removal; T1497 Virtualization/Sandbox Evasion

Exfiltration

T1041 Exfiltration Over C2 Channel

Credential Access

T1056 Input Capture; T1111 Multi-Factor Authentication Interception; T1539 Steal Web Session Cookie; T1555 Credentials from Password Stores

Execution

T1059 Command and Scripting Interpreter; T1204 User Execution

Persistence

T1176 Software Extensions

Initial Access

T1189 Drive-by Compromise; T1195 Supply Chain Compromise; T1566 Phishing

Discovery

T1518 Software Discovery

Resource Development

T1584 Compromise Infrastructure; T1585 Establish Accounts

Impact

T1657 Financial Theft

Remediation

Immediate actions

  • Check installed Edge extensions against Microsoft's published StegoAd extension-ID list via edge://extensions and remove any matches
  • Block network egress to known StegoAd C2/exfil domains, including mitarchive[.]info
  • Force password resets for Google and WordPress admin accounts on any endpoint that had a matching extension installed
  • Invalidate/rotate active browser session cookies for affected users to neutralize stolen-cookie session hijacking
  • Audit ad-network and affiliate-program accounts (Amazon, eBay, AliExpress) for unauthorized commission redirection

Workarounds

  • Disable/remove extensions matching the affected category+name patterns (ad blockers, VPNs, translators, video downloaders) sourced from unverified developer accounts until vetted

Longer-term hardening

  • Deploy enterprise browser-extension allowlisting/management policies restricting installs to vetted publishers
  • Enable hardware security keys / phishing-resistant MFA for Google and WordPress admin accounts
  • Monitor for extension code fetching external images/fonts at runtime and flag post-install network calls to newly-registered domains as anomalous
  • Extend monitoring to Chrome and Firefox, since reporting indicates the same codebase produced variants for those browsers

Affected and fixed versions

  • Microsoft — Microsoft Edge Add-ons Store (browser extensions)
    Vulnerable versions: Manifest V2 extensions; Manifest V3 extensions
    Fixed in: All 119 identified extensions removed from store as of 2026-06-16
  • Various (impersonated third-party developers) — Chromium-based / Chrome and Firefox variants of the same extension codebase
    Vulnerable versions: Not fully enumerated; reporting indicates cross-browser variants exist
    Fixed in: Not confirmed removed on Chrome/Firefox stores as of this research

Timeline

  • StegoAd operation assessed to begin (extensions active since at least 2021, initially built on Manifest V2 with JavaScript appended after the PNG IEND marker)
  • Over more than two years of sustained activity, the operator iteratively adjusts payload encryption, rotates C2 infrastructure, migrates the extension codebase from Manifest V2 to Manifest V3, and progressively shifts steganographic carriers from PNG to WebP images and finally to WOFF2 font-glyph data as Microsoft's detection capability improves (exact per-shift dates not disclosed by Microsoft)
  • Koi Security publicly links the locked-ioc-1 credential-theft domain to the DarkSpectre actor cluster, connecting it to the earlier ShadyPanda and GhostPoster malicious-extension campaigns
  • Microsoft's Edge Extensions Security Team begins investigating suspicious extensions after enterprise customer reports of unexpected pop-ups, unauthorized redirects, and sluggish browser performance
  • Microsoft confirms it has disabled and removed all 119 identified malicious extensions, suspended 90+ developer accounts, and publishes technical report 'Inside StegoAd'
  • Malwarebytes and The Hacker News publish coverage of the StegoAd disruption, summarizing scale, payload capabilities, and evasion techniques; The Hacker News reporting surfaces the December 2025 Koi Security/DarkSpectre attribution linkage
  • Follow-on reporting (Rescana, Risky Business, TechRadar, TechTimes) publishes MITRE ATT&CK mappings, the locked-ioc-1 credential-exfiltration domain, and notes possible overlap with the DarkSpectre actor cluster
  • Threadlinqs Intelligence research and IOC correlation performed for this record; BeaconBeagle check on locked-ioc-1 returned no additional infrastructure matches

Sources cited

Previous and next in malware

Drafted by the Threadlinqs research pipeline from 13 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats