How This Briefing Works
This report opens with key findings, then maps the gaps between what ChorusAI 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
Key Findings
1 detection across 1 site
Disclosure Gaps
Claims vs. Observed Behavior
1 gaps
Pending Analysis
UNKNOWN
They Claim
“Claims extraction pending”
Observed Behavior
CDT analysis needed for engagement tracking and data capture assessment
Customer Impact
What This Means For You
No measurable behavioral risk from current detection data. Revenue intelligence vendors may capture engagement signals and conversation data that are not visible in signature-only analysis.
Recommended Actions
What To Do About It
Role-specific actions based on observed behavior
If You Use ChorusAI
- →monitor for future scanner detections
If You're Evaluating ChorusAI
- →recon investigation for engagement tracking and data capture patterns
Negotiation Leverage
- →Baseline detection only — behavioral analysis pending
- →Revenue intelligence vendors may capture undisclosed engagement data
- →Review data capture scope and conversation recording policies
IOC Manifest
IOC Manifest
6 INDICATORS
Indicators of compromise across 4 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
TRACK
chorus.ai
Tracking script
Ecosystem
Ecosystem & Supply Chain
ChorusAI operates in the revenue intelligence market, providing sales analytics, conversation intelligence, and pipeline optimization.
Loads (1)
Evidence
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
HAR Capture
Complete network capture with all requests and responses
IOC Manifest
7 detection signatures across scripts, domains, cookies, and network endpoints