Home › Intelligence › Brief
BREACH BRIEF🟠 High Breach

FNTECH Events Platform Breach Exposes 10,386 Registrant Emails, Names, and IP Addresses

In July 2024 FNTECH, an events‑management SaaS, suffered a breach that released email addresses, names, and IP addresses for 10,386 registrants, including attendees of the Roblox Developer Conference. The leak highlights the need for continuous third‑party risk monitoring and auditable evidence of vendor security controls.

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 haveibeenpwned.com
🟠
Severity
High
BR
Type
Breach
🎯
Confidence
High
🏢
Affected
3 sector(s)
✅
Actions
4 recommended
📰
Source
haveibeenpwned.com

FNTECH Events Platform Breach Exposes 10,386 Registrant Emails, Names, and IP Addresses

What Happened — In July 2024 the events‑management SaaS FNTECH disclosed a breach affecting 10,386 registered accounts. The exposed data set includes email addresses, full names, and IP addresses of registrants, notably participants of the Roblox Developer Conference.

Why It Matters for Trust & Control Assurance

  • The incident illustrates a gap in third‑party oversight: a vendor handling attendee data failed to protect basic identifiers, a scenario continuous control‑assurance programs are built to detect and remediate.
  • Demonstrable evidence of vendor risk assessments, contractual security clauses, and ongoing monitoring can provide a defensible audit trail when regulators or partners inquire about data‑handling practices.
  • Continuous monitoring of vendor controls (e.g., encryption, access reviews) helps organizations prove due‑diligence and maintain trust with customers and auditors.

Who Is Affected – SaaS event‑management providers, their corporate customers, and any organization that shares attendee data with FNTECH (technology, gaming, education, and marketing sectors).

Recommended Actions

  • Initiate a third‑party risk review of FNTECH: request recent SOC 2/ISO 27001 reports, evidence of encryption at rest, and access‑control policies.
  • Verify that any shared credentials have been rotated and that multi‑factor authentication is enforced for vendor portals.
  • Update contractual clauses to require breach‑notification timelines and continuous security monitoring.
  • Conduct a focused data‑subject impact assessment for exposed email, name, and IP fields; notify affected individuals as required.

Source: Have I Been Pwned – FNTECH breach

Technical Notes – The breach was reported via the public “Have I Been Pwned” database; no specific attack vector (phishing, exploit, misconfiguration) was disclosed. Exposed data types are limited to personally identifiable information (email, name) and network identifiers (IP).

Source: same as above

📰 Original Source
https://haveibeenpwned.com/api/v3/breach/RobloxDeveloperConference2024 ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Vendor Risk Hub

This is the scenario continuous vendor monitoring is built to catch.

When a vendor is compromised, your third-party risk controls are what produce the audit trail showing you knew, assessed, and acted. The Verisq AI Trust Operations platform tracks that continuously.

Explore the Verisq AI Trust Operations platform →