How This Briefing Works
This report opens with key findings, then maps the gaps between what Koala 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
Koala was observed loading and executing before user consent was obtained on 17% of sites where it was detected.
Claims vs. Observed Behavior
comprehensive_surveillance
“Unknown - requires claims extraction”
C06+C07+C09+C14+C15 detected - maximum surveillance deanonymization platform
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Koala
- →IMMEDIATE: Audit complete Koala surveillance scope - catalog behavioral, recording, and identity capabilities
- →Map identity resolution methodology - how does Koala link anonymous to known?
- →Verify tag manager injection scope - what capabilities can Koala deploy autonomously?
- →Enforce strict consent gate - deanonymization must not occur pre-consent
- →Document session recording extent - full replay vs aggregated metrics
If You're Evaluating Koala
- →Evaluate first-party identification alternatives eliminating third-party deanonymization
- →Consider form-based lead capture instead of stealth visitor identification
- →Investigate privacy-respecting analytics without identity resolution
- →Prepare Koala removal plan - comprehensive surveillance creates unacceptable liability
Negotiation Leverage
- →Koala deploys C06+C07+C09+C14+C15 - vendor must explain comprehensive surveillance infrastructure
- →Demand complete technical disclosure of behavioral, recording, identity, and injection capabilities
- →Require consent-first operation - no pre-consent deanonymization
- →Negotiate removal of session recording and behavioral biometrics if not contractually specified
- →Establish absolute liability for deanonymization violations - vendor accountability is non-negotiable
- →Consider contract termination - surveillance scope may exceed acceptable risk threshold
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
Full session replay
Identity stitching
Ignoring CMP signals
PII deanonymization
Container/loader (neutral)
IOC Manifest
Indicators of compromise across 5 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
138 detection signatures across scripts, domains, cookies, and network endpoints