ZoomInfo 首席执行官屏蔽研究人员,原因是其记录了未经同意的生物识别追踪行为。
ZoomInfo CEO blocks researcher after documenting pre-consent biometric tracking

原始链接: https://github.com/clark-prog/blackout-public

## ZoomInfo GTM Studio 追踪问题 - 摘要 安全研究发现,ZoomInfo 的 GTM Studio 登陆页面存在广泛的预先同意追踪,尽管该平台被宣传为识别网站访客。在任何同意横幅出现*之前*,检测到超过 50 个追踪请求,包括与 Sardine.ai 合作的行为生物识别和 PerimeterX 的指纹识别。 当研究人员在 LinkedIn 上分享这些发现时,ZoomInfo 的 CEO 立即屏蔽了他们,没有提供任何回应或澄清。这份“证据包”详细介绍了技术分析,包括解码的配置,显示默认追踪鼠标移动和打字模式。 该报告强调了使用此类供应商可能存在的法律风险,并引用了潜在的 GDPR、CCPA 和 CIPA 违规行为。它警告说,依赖于可能非法获取的“意向数据”可能导致法律责任、客户诉讼和声誉损害。 核心信息:透明度至关重要。营销人员应审计其技术栈,了解供应商的做法,并优先考虑合规性,因为仅仅声称不知情可能不是有效的辩护。证据已公开提供,供验证和审查。

## ZoomInfo 首席执行官阻止曝光生物识别追踪的研究人员 一位研究人员(SignalDr)记录了ZoomInfo的GTM Studio着陆页上的监控行为,并在通过Chrome DevTools揭示发现后被该公司的首席执行官阻止。该研究人员发现了广泛的预先同意追踪,包括通过Sardine.ai进行的行为生物识别和通过PerimeterX进行设备指纹识别,以及118个追踪域名。证据,包括HAR文件和代码分析,已在GitHub上公开 ([https://github.com/clark-prog/blackout-public](https://github.com/clark-prog/blackout-public))。 该事件在Hacker News上引发了关于帖子内潜在广告以及更广泛的隐私侵犯问题的讨论。一些评论员指出ZoomInfo的讽刺之处——在自身使用多种指纹识别供应商的同时,出售访客识别信息。人们对GDPR执行不力以及将商业利益置于客户隐私之上的趋势表示担忧。 还有人强调了现代网络上追踪的普遍性以及用户对脚本执行更大的控制的需求。
相关文章

原文

Blackout's Public FAFO Repo

"You can block the researcher. You can't block the evidence."


On November 25, 2025, ZoomInfo CEO Henry Schuck posted a product demo of GTM Studio on LinkedIn — their AI-powered platform that "identifies person-level website visits."

A security researcher analyzed the GTM Studio landing page and documented extensive pre-consent tracking infrastructure. The findings were posted as a comment on the CEO's LinkedIn post.

Within minutes, the researcher was blocked.

No correction. No clarification. Just silence.

This evidence pack ensures the findings cannot be suppressed.


Finding Evidence
50+ tracking requests before consent Network capture shows tracking fires before consent banner loads
Sardine.ai biometrics enabled enableBiometrics: true in decoded config
PerimeterX fingerprinting Collector fires at request #79 (pre-consent)
DNS fingerprinting active enableDNS: true in Sardine config
118 unique tracking domains Contacted on single page load
Session fingerprinting Fraud detection API creates session pre-consent

Decoded Sardine.ai Configuration

{
  "enableBiometrics": true,
  "enableDNS": true,
  "partnerId": "zoominfo",
  "dBaseDomain": "d.sardine.ai",
  "environment": "production"
}

This configuration was decoded from a base64-encoded payload in the collector iframe URL.

Translation:

  • Mouse movements tracked by default
  • Typing patterns recorded
  • DNS fingerprinting enabled
  • ZoomInfo has a formal partnership with Sardine.ai
  • This is production, not testing

ZoomInfo markets GTM Studio as a tool to "identify person-level website visits."

Yet on their own landing page for this product, they deploy:

  • 3 external identity/fingerprinting vendors (Sardine.ai, PerimeterX, IdentityMatrix.ai)
  • Behavioral biometrics before consent
  • 118 different tracking domains

Even the visitor identification vendor doesn't trust their own product for visitor identification.


For Marketers: Why This Matters To You

You're not a privacy lawyer. You're trying to hit pipeline targets. So why should you care?

1. Your Budget May Be Buying Legal Exposure

Every dollar spent on vendors with documented pre-consent tracking is a dollar potentially spent on future legal liability. When class actions emerge in this space, "we didn't know" often isn't accepted as a defense — it can be characterized as negligence.

The question to consider: could this data become actionable in litigation?

2. Your "Intent Data" May Carry Legal Risk

Data collected without proper consent may not be legally processable. That could mean:

  • Your lead scores may be built on problematic data
  • Your ABM campaigns may target profiles collected without consent
  • Your attribution models may include tainted signals

This is worth evaluating with your legal team.

3. Your Customers Could Become Plaintiffs

The people being tracked without consent? They're the same people you're trying to convert. When they find out (and the prevalence of these practices is increasingly public), you may not just lose a deal — you may create an adversary with legal standing.

Every visitor is a potential plaintiff. Every page view is potential evidence.

4. Your Vendor's Compliance Affects YOUR Compliance

GDPR Article 26. CCPA 1798.100. Your contracts may say "vendor warrants compliance." Courts have found joint liability regardless. When a vendor's practices become public record, your legal team will ask: "Who approved this vendor?"

That answer is discoverable.

5. Your Competitors May Use This Against You

Imagine losing an enterprise deal because the prospect's security team researched your martech stack. Imagine the RFP question: "Do you use vendors with documented pre-consent tracking?"

Your vendor choices are discoverable. Choose accordingly.


Marketing has operated in a "move fast, ask forgiveness" mode for 15 years. That era is ending.

The tracking infrastructure that powered the "growth at all costs" playbook is now:

  • Documented (you're reading the evidence)
  • Discoverable (public GitHub repo)
  • Potentially actionable (GDPR, CCPA, CIPA may apply)

You can either:

  1. Audit your stack now and evaluate liability before it crystallizes
  2. Wait for external scrutiny and explain why you didn't act on public evidence

The vendors won't protect you. Your contracts may not protect you. Only your choices will.


zoominfo-gtm-studio/
├── FINDINGS.md              # Full technical analysis
├── TIMELINE.md              # CEO post → comment → block sequence
├── code/
│   ├── sardine-config.json  # Decoded biometrics configuration
│   ├── perimeterx.md        # PerimeterX infrastructure details
│   └── tracking-sequence.md # Complete request timeline
├── methodology/
│   └── how-we-tested.md     # Reproduction instructions
└── legal/
    ├── gdpr-analysis.md     # EU regulation analysis
    ├── ccpa-analysis.md     # California privacy law analysis
    └── cipa-exposure.md     # California wiretapping exposure analysis

How To Verify (5 Minutes)

  1. Open Chrome in Incognito mode
  2. Open DevTools (F12) → Network tab
  3. Enable "Preserve log"
  4. Navigate to: https://www.zoominfo.com/products/gtm-studio
  5. DO NOT interact with consent banner
  6. Count requests that fire before you see the banner
  • collector-pxosx7m0dx.px-cloud.net — PerimeterX fingerprinting
  • *.d.sardine.ai/bg.png — Sardine behavioral biometrics
  • gw-app.zoominfo.com/gw/ziapi/fraud-detection — Session fingerprinting

  • Article 5(3): Cookie consent required before tracking
  • Article 6: Lawful basis required for processing
  • Article 9: Behavioral biometrics may constitute special category data
  • Right to Know: Sardine.ai partnership not disclosed in privacy policy
  • Right to Opt-Out: No opt-out presented before tracking begins
  • Data Sharing: Data transmitted to 40+ third parties pre-consent
  • Wiretapping provisions: Biometric collection without consent may implicate wiretapping statutes
  • Two-party consent: California requires all-party consent for certain recordings

![Henry_Schuck_Post](./Screenshot 2025-11-25 100147.png)

When presented with documented evidence of:

  • Pre-consent tracking
  • Behavioral biometrics collection
  • 118 tracking domains on a single page

The CEO of a publicly traded company chose to:

  • Block the researcher
  • NOT dispute the findings
  • NOT provide clarification

ZoomInfo has not responded to requests for comment on these findings.


THIS IS NOT LEGAL ADVICE.

The information contained in this evidence pack is provided for informational and educational purposes only. Nothing herein constitutes legal advice, and no attorney-client relationship is created by accessing, reading, or using this information.

You should consult with a qualified attorney licensed in your jurisdiction before taking any action based on the information presented here. Privacy law is complex, varies by jurisdiction, and is subject to change. What may constitute a violation in one jurisdiction may not apply in another.

Blackout is not a law firm. We are security researchers documenting technical findings. We make no representations or warranties about:

  • The legal accuracy or completeness of any analysis
  • The applicability of cited regulations to your specific situation
  • The current state of any company's tracking practices (which may change)
  • The outcome of any legal action based on this information

All findings are based on publicly observable behavior at the time of testing. Network captures, decoded configurations, and request timelines represent a point-in-time snapshot. Vendors may modify their practices after publication.

If you believe you have been affected by pre-consent tracking or surveillance practices, consult a privacy attorney or contact your local data protection authority. Do not rely solely on this document to assess your legal rights or remedies.

By accessing this evidence pack, you acknowledge that you have read and understood this disclaimer.


This evidence pack is released in the public interest.

Vendor tracking infrastructure should be transparent and verifiable, not suppressed when documented.

Released by: Blackout Research
Date: November 25, 2025


Blackout Friday — November 29, 2025

Free forensic scans. 100 domains. 24 hours.

Find out what YOUR vendors are doing.

deployblackout.com


"You can block the researcher.
You can't block the evidence."

联系我们 contact @ memedata.com