Skip to navigation

Threat reportThreat IntelligenceTL-2026-0792

Maine AG Data Breach Notification Portal Abused to Publish Fraudulent Breach Disclosures Impersonating VRChat and Discord

mediumMONITORING

An unknown actor abused the Office of the Maine Attorney General's public data breach notification portal — which auto-published submissions without verification — to file fraudulent breach notices impersonating VRChat (claimed 2.4M users) and Discord (claimed 10M users). No data was actually compromised; the campaign weaponized a trusted government disclosure channel to spread disinformation and inflict reputational harm.

Key facts

IdentifiersTL-2026-0792
Also known asMaine AG Breach Portal Hoax, Fake VRChat/Discord Breach Filings
SeverityMEDIUM
Affected productsState of Maine Office of the Attorney General Data Breach Notification Portal; VRChat Inc. VRChat (brand impersonated; no system compromise); Discord Inc. Discord (brand impersonated; no system compromise)
Weaknesses (CWE)CWE-345, CWE-862, CWE-602
MITRE ATT&CK techniquesT1036 Masquerading, T1190 Exploit Public-Facing Application, T1491 Defacement, T1565 Data Manipulation, T1583 Acquire Infrastructure, T1585 Establish Accounts, T1589 Gather Victim Identity Information, T1591 Gather Victim Org Information, T1593 Search Open Websites/Domains, T1684.001 Impersonation
MotivationUNKNOWN
Target sectorsgovernment, technology, gaming, social media
Target regionsNorth America, United States
Detection rules9 (1 shown free)
Sources7 cited sources

Detection coverage

As of 2026-06-14, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-0792 across Splunk SPL, Microsoft KQL and Sigma, covering 18 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Auto-Published Hoax Filing — Inflated Count, Missing Legal Rep, Fictitious Filer / External Defacement

Detects the impact stage (T1491.002 external defacement of a trusted public database; T1656 impersonation): a notice auto-published WITHOUT verification that combines an inflated round-number victim count (>=1M, multiple of 100k), missing legal representation, no attached consumer notice, and a filer whose name/email cannot be matched to the impersonated organization. This is the composite signature of the published VRChat (2.4M) and Discord (10M) hoaxes. Designed to alert on records that reached the public site so a takedown/correction workflow can trigger.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1491.002, T1656, T1036
  • Data sources: webapp, breach_portal:submission, BreachPortalSubmissions_CL
  • Severity: critical
  • Confidence: high

Splunk SPL

index=webapp sourcetype="breach_portal:submission" event_type="breach_notification_published" verified=false
| eval inflated=if(affected_count>=1000000 AND (affected_count%100000)==0,1,0)
| eval no_legal=if(isnull(legal_representation) OR legal_representation="" OR legal_representation="null",1,0)
| eval no_notice=if(consumer_notice_attached="false" OR consumer_notice_attached==0,1,0)
| eval no_idtheft=if(identity_theft_protection_offered="false" OR identity_theft_protection_offered==0,1,0)
| eval fictitious_filer=if(isnotnull(filer_verified) AND filer_verified="false",1,0)
| eval risk=inflated+no_legal+no_notice+no_idtheft+fictitious_filer
| where risk>=3
| table _time submitting_entity affected_count filer_name filer_email inflated no_legal no_notice no_idtheft fictitious_filer risk
| sort - risk - _time

Microsoft KQL

// Sentinel custom log table; primary flavor is SPL
BreachPortalSubmissions_CL
| where TimeGenerated > ago(90d)
| where EventType_s == "breach_notification_published" and Verified_b == false
| extend Inflated = AffectedCount_d >= 1000000 and (toint(AffectedCount_d) % 100000) == 0
| extend NoLegal = isempty(LegalRepresentation_s) or LegalRepresentation_s == "null"
| extend NoNotice = ConsumerNoticeAttached_b == false
| extend NoIdTheft = IdentityTheftProtectionOffered_b == false
| extend FictitiousFiler = FilerVerified_b == false
| extend Risk = toint(Inflated) + toint(NoLegal) + toint(NoNotice) + toint(NoIdTheft) + toint(FictitiousFiler)
| where Risk >= 3
| project TimeGenerated, SubmittingEntity_s, AffectedCount_d, FilerName_s, FilerEmail_s, Risk
| sort by Risk desc, TimeGenerated desc

Sigma

title: Auto-Published Hoax Breach Filing With Inflated Count And Missing Legal Notice
id: 6b3f1a52-0792-4a11-9c01-1a2b3c4d5e03
status: experimental
description: Detects an unverified, auto-published breach notice combining an inflated round-number victim count with missing legal representation and no attached consumer notice — the composite impact signature of the VRChat/Discord breach-portal hoax defacing a trusted public database (TL-2026-0792).
references:
    - https://www.bleepingcomputer.com/news/security/maine-disables-data-breach-notification-portal-after-fake-disclosures/
    - https://attack.mitre.org/techniques/T1491/002/
    - https://attack.mitre.org/techniques/T1656/
author: Threadlinqs Team
date: 2026/06/14
tags:
    - attack.impact
    - attack.t1491.002
    - attack.defense_evasion
    - attack.t1656
    - attack.t1036
logsource:
    product: webapp
    category: application
detection:
    selection:
        event_type: 'breach_notification_published'
        verified: false
        legal_representation: null
        consumer_notice_attached: false
        affected_count|gte: 1000000
    condition: selection
fields:
    - submitting_entity
    - affected_count
    - filer_name
    - filer_email
falsepositives:
    - Large genuine breaches self-reported by a small in-house team before counsel is engaged (verify with the entity)
level: high

Known false positives:

  • A large genuine breach self-reported by a small in-house team before outside counsel is engaged
  • Legitimate filings that happen to report an exactly round affected count

Tuning notes: Lower the risk threshold to >=2 for fully unauthenticated portals and raise to >=4 where submitter identity is already verified. Feed confirmed hits directly into the takedown/public-correction workflow; correlate the same filer_email/src_ip across multiple impersonated entities to surface a single actor running several hoaxes.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Sentinel: Impersonating Submission From Newly-Created Free-Webmail Identity — Exploitation · unlock with TL Creds
  • Sentinel: Auto-Publish Without Verification Step — Data Manipulation / Missing Authorization · unlock with TL Creds
  • Sentinel: Single Source Filing Breach Notices Against Multiple Impersonated Brands — Campaign / Lateral Spread · unlock with TL Creds
  • Sigma: Fictitious Filer Identity Not Matching Impersonated Organization — Exploitation · unlock with TL Creds
  • Sigma: Placeholder Contact Phone and Vague Boilerplate Affected-Data Field — Post-Exploitation · unlock with TL Creds
  • Sigma: Insider-Wrongdoing Claim With No Notice Or Counsel On Unverified High-Count Filing — C2/Impact · unlock with TL Creds
  • Breach-Portal Submission Impersonating a Vendor via Free-Webmail / Non-Corporate Reporter — Exploitation · unlock with TL Creds
  • Breach Filing With Anachronistic Dates and Implausible Breach/Discovery Gap — Post-Exploitation · unlock with TL Creds

Indicators of compromise

As of 2026-06-14, Threadlinqs Intelligence tracks 18 indicators of compromise for TL-2026-0792.

Sample indicators (1 of 18)

  • Domain: gmail[.]com

Defanged, TLP:CLEAR. Full set of 18 indicators: unlock with TL Creds.

18 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

On June 11, 2026, BleepingComputer reported that the Office of the Maine Attorney General's public-facing data breach notification database had been abused to publish fabricated breach disclosures falsely attributed to VRChat and Discord. Maine, like many U.S. states, operates a statutory breach-notification system where entities self-report incidents; the portal's design automatically published submitted notices to the public database without any independent verification or human review. The Maine AG's office confirmed: "We don't have any independent knowledge of the breaches, the submitting entity fills out the information and it goes directly onto the site." This trust-by-default workflow is the root cause that the actor exploited.

The fake VRChat filing claimed a breach affecting more than 2.4 million users, alleging that attackers accessed VRChat's cloud environment between approximately May 10-12 and exposed usernames, emails, VRChat+ subscription status, login history, device/hardware IDs, and linked Steam/Meta user IDs. VRChat's Head of Community, Charles Tupper, confirmed the filing was fraudulent: "VRChat did not submit this Notice of Data Incident, and the employee/email cited does not exist." The notice had been submitted under the name of a fictitious employee.

A second fraudulent notice impersonated Discord, claiming "more than 10 million people" were affected via "Insider wrongdoing." This filing was submitted on June 8, 2026 by "Xavier Morrison," listed as a "Data Subject / Reporter" rather than an official Discord representative, using a personal Gmail account and a placeholder/inactive phone number. The submission carried multiple red flags: an alleged breach date of July 9, 2024 with discovery not until August 2, 2025 (over a year gap), an anachronistic consumer-notification date of January 1, 2000, vague affected-data elements ("Name or other personal identifier in combination with"), no identity-theft protection offered, no copy of any consumer notice, and an absence of the professional legal representation (e.g., BakerHostetler) that handled prior legitimate Discord filings. These fabricated claims are distinct from Discord's genuine 2025 incidents (a September/October 2025 Zendesk third-party vendor compromise and a separate incident affecting roughly 70,000 users via stolen ID photos).

The abuse forced both companies to publicly deny the false claims before any verification occurred. On June 12, 2026, the Maine Attorney General's Office disabled public access to the breach notification database, stating: "After conversations with VRChat, one of two affected companies, it has become clear that the reported data breaches were hoaxes submitted by an unknown entity unrelated to either company." The office said it would review its reporting procedures to reduce similar abuse; entities can still submit notifications, but public access now requires contacting the AG's office directly. The office stated it was previously "not aware of another example" of intentional misrepresentation through the system. This event is best understood as an abuse-of-functionality / disinformation operation against a trusted public-sector data channel rather than a software vulnerability — there is no CVE, no malware, and no technical compromise of VRChat, Discord, or the State of Maine.

MITRE ATT&CK techniques by tactic:

Defense Evasion

T1036 Masquerading

Initial Access

T1190 Exploit Public-Facing Application

Impact

T1491 Defacement; T1565 Data Manipulation

Resource Development

T1583 Acquire Infrastructure; T1585 Establish Accounts

Reconnaissance

T1589 Gather Victim Identity Information; T1591 Gather Victim Org Information; T1593 Search Open Websites/Domains

stealth

T1684.001 Impersonation

Remediation

Immediate actions

  • State breach-portal operators: disable automatic public publication of self-reported breach notices pending verification (Maine took the public database offline on 2026-06-12)
  • Impersonated organizations: publicly and promptly deny fraudulent filings via official channels and request takedown from the hosting authority
  • Monitor state AG breach-notification databases for filings naming your organization, especially those using non-corporate contact details

Workarounds

  • Gate public access to breach databases behind a request-to-the-AG process while verification controls are built (Maine's interim measure)

Longer-term hardening

  • Introduce submitter identity verification (verified corporate email domains, callback verification, or notarized/authenticated filing) before public publication
  • Add a human review / moderation queue between submission and public posting
  • Implement anomaly checks on filings (anachronistic dates, free webmail contacts, missing legal representation, implausible record counts)
  • Establish a rapid takedown and public-correction workflow for confirmed hoax filings

Affected and fixed versions

  • State of Maine — Office of the Attorney General Data Breach Notification Portal
    Vulnerable versions: public auto-publish workflow (pre-2026-06-12)
    Fixed in: public access disabled / under review (2026-06-12)
  • VRChat Inc. — VRChat (brand impersonated; no system compromise)
  • Discord Inc. — Discord (brand impersonated; no system compromise)

Timeline

  • Fraudulent Discord filing lists this as the alleged breach date (fabricated; no such breach occurred).
  • Fraudulent Discord filing lists this as the alleged discovery date — over a year after the claimed breach, a key red flag.
  • Fraudulent VRChat filing alleges attackers accessed VRChat's cloud environment between ~May 10-12, 2026, exposing usernames, emails, VRChat+ status, login history, device/hardware IDs and linked Steam/Meta IDs (all fabricated; VRChat confirmed no breach).
  • Fake Discord breach notice submitted to the Maine AG portal under the name 'Xavier Morrison' (Data Subject / Reporter) using a personal Gmail and placeholder phone, claiming 10M affected via 'Insider wrongdoing'.
  • VRChat Head of Community Charles Tupper publicly denies the filing: 'VRChat did not submit this Notice of Data Incident, and the employee/email cited does not exist.'
  • BleepingComputer (Bill Toulas) reports the fake VRChat (2.4M) and Discord (10M) breach disclosures published on Maine's official portal; VRChat confirms its filing is fraudulent and cites a non-existent employee/email.
  • Maine states entities can still submit notifications but public access now requires contacting the AG's office directly while verification controls are reviewed.
  • Maine Attorney General's Office disables public access to the breach notification database, calling the filings 'hoaxes submitted by an unknown entity,' and announces a review of reporting procedures.

Sources cited

Previous and next in threat intel

Drafted by the Threadlinqs research pipeline from 7 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats