How This Briefing Works
This report opens with key findings, then maps the gaps between what Saleshandy 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
Saleshandy was observed loading and executing before user consent was obtained on 100% of sites where it was detected.
Claims vs. Observed Behavior
email_web_surveillance
“Pending claims extraction”
Runtime shows email-linked web tracking active before consent
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Saleshandy
- →Audit email-to-web tracking linkage and consent timing
- →Map persistence mechanisms linking email recipients to web visitors
- →Document session recording scope for email-originated sessions
- →Verify DPA covers email-web surveillance combination
If You're Evaluating Saleshandy
- →Require consent-first web tracking with email attribution disabled pre-consent
- →Demand disclosure of email-web linking methodology and persistence techniques
- →Negotiate liability provisions covering surveillance across communication channels
- →Evaluate email-only alternatives without web tracking extension
Negotiation Leverage
- →Four active BTI codes: Demand DPA addressing each threat category
- →C09+C07 email-web combination: Require consent before ANY web tracking regardless of email engagement
- →Persistence threat: Demand 24hr data deletion post-consent-revocation across email AND web
- →Request written confirmation that email engagement does not bypass web consent requirements
- →Alternative: Email tracking without web extension eliminates consent bypass surface
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
Ignoring CMP signals
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
255 detection signatures across scripts, domains, cookies, and network endpoints