How This Briefing Works
This report opens with key findings, then maps the gaps between what Semrush discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection data and evidence underneath.
Key Findings
Analysis pending. Findings will appear here once intelligence collection is complete.
Claims vs. Observed Behavior
pending
“Awaiting scanner verification”
Runtime behavior of Semrush tracking scripts on customer websites has not yet been observed via BLACKOUT scanner
pending
“Extension encryption status”
Browser extension data transmission patterns require direct forensic analysis to confirm current encryption status and data payloads
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Semrush
- →- Audit and remove Semrush browser extensions (Semrush Rank, PI Rank) from all corporate-managed browsers and endpoint policies. - Evaluate whether your organization's ISP agreements permit clickstream data resale to third parties, and negotiate opt-out provisions where possible. - Implement browser extension allowlisting policies to prevent employees from installing unvetted extensions that may feed clickstream panels. - Monitor what competitive intelligence about your organization is visible through Semrush's Traffic Analytics tool to understand your current exposure level. - Consider the competitive intelligence asymmetry: if you subscribe to Semrush, your competitors likely do too, and your traffic data flows in both directions.
Negotiation Leverage
- →Leverage: Semrush's reliance on clickstream data from browser extensions and ISP partnerships creates regulatory exposure under GDPR, CCPA, and emerging privacy legislation. The February 2026 finding that affiliated extensions transmitted data over unencrypted HTTP is a material security concern. If your organization uses Semrush products, request contractual guarantees that your employees' browsing data collected via extensions is excluded from the traffic analytics dataset sold to other subscribers.
- →Key questions for Semrush: (1) Can you guarantee our employees' browsing data from your extensions is not included in traffic estimates visible to other subscribers? (2) What encryption standards are currently applied to all extension-collected data in transit? (3) Which ISP and clickstream panel partners contribute data to your Traffic Analytics product? (4) What is the data retention period for raw clickstream data?
- →Protections: Include data exclusion clauses in enterprise agreements. Require notification if Semrush's data collection practices change. Establish the right to audit what data about your organization's web properties is available through their platform.
IOC Manifest
Indicators of compromise across 4 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
135 detection signatures across scripts, domains, cookies, and network endpoints