How This Briefing Works
This report opens with key findings, then maps the gaps between what Influ2 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
Pre-Consent Activity
Influ2 was observed loading and executing before user consent was obtained on 83% of sites where it was detected.
Claims vs. Observed Behavior
pending
“Unknown”
Requires claims extraction via CDT
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Influ2
- →Immediately audit Influ2 deployment for consent bypass and identity resolution without user notification
- →Demand contractual prohibition on viewer identification data sharing across customer base
- →Request legal review of person-based advertising compliance with GDPR transparency requirements
- →If continuing use, implement explicit consent mechanism before identity resolution activates
If You're Evaluating Influ2
- →Consider whether person-based advertising benefits justify severe regulatory exposure and competitive intelligence leakage
- →Evaluate alternative ABM platforms using account-level targeting without individual identification
- →Request third-party audit of identity resolution methodology and data sharing practices
- →Assess whether platform's core functionality can be made GDPR-compliant or if architecture is fundamentally non-compliant
Negotiation Leverage
- →Influ2 VRS 80 = Broker (100) + Counselor (95) threat. Person-level ad targeting exposes campaign strategy to competitors. This is existential risk.
- →Identity resolution (BTI-C14) of ad viewers without consent = systematic GDPR violation. The platform's core value proposition violates privacy law.
- →Consent bypass (BTI-C09) demonstrates willful non-compliance. No technical remediation exists; platform architecture requires viewer identification without consent.
- →Cross-domain sync (BTI-C08) links ad impressions to website behavior, creating comprehensive surveillance. Individuals are tracked without notification.
- →Competitive intelligence exposure: If competitors use Influ2, they may observe which individuals see your ads, revealing target account lists.
- →Ask: What is the legal basis for ad viewer identification? How are individuals notified? What is the opt-out mechanism? Expect no satisfactory answers.
- →Recommendation: Legal review required before deployment. Platform's core functionality likely violates GDPR Articles 13-14. Consider contract termination.
Runtime Detections
BLACKOUT observed this vendor's JavaScript executing in a live browser and classified each hostile behavior using our BTI-C (Behavioral Threat Intelligence — Capability) taxonomy. These are not theoretical risks — each code below was triggered by something we watched this vendor's code actually do.
Keystroke/mouse tracking
Impact: Mouse tracking and engagement patterns captured from ad impressions feed behavioral profiles used to identify individual viewers.
Identity stitching
Impact: Cookie syncing across publishers and your website enables viewer tracking from initial ad impression through site conversion.
Ignoring CMP signals
Impact: Ad viewer identification continues without explicit user consent, violating foundational privacy rights and creating GDPR violation liability.
PII deanonymization
Impact: Linking anonymous ad impressions to named individuals enables persistent surveillance that users cannot detect or control, violating privacy expectations.
Container/loader (neutral)
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
144 detection signatures across scripts, domains, cookies, and network endpoints