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

> 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.

- **Published:** 2026-06-14T00:00:00Z
- **Last reviewed:** 2026-06-14T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-0792
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-maine-breach-portal-abuse-tl-2026-0792.webp?v=7796e9cc (Threadlinqs threat intel: Maine AG Portal Fake VRChat Notices: Detection & IOCs (TL-2026-0792) — Medium severity, 18 IOCs, 9 detection rules.)
- **ID:** TL-2026-0792
- **Severity:** MEDIUM
- **Category:** THREAT_INTEL
- **Status:** MONITORING
- **Detections:** 9 (1 shown free below) · **IOCs:** 18 (1 shown free below)

## Description

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

- T1591 Gather Victim Org Information
- T1589 Gather Victim Identity Information
- T1593 Search Open Websites/Domains
- T1585 Establish Accounts
- T1583 Acquire Infrastructure
- T1190 Exploit Public-Facing Application
- T1036 Masquerading
- T1684.001 Impersonation
- T1565 Data Manipulation
- T1491 Defacement

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**Auto-Published Hoax Filing — Inflated Count, Missing Legal Rep, Fictitious Filer / External Defacement** (`TL-2026-0792-SPL-003`)

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

```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

```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

```yaml
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

- Sentinel: Impersonating Submission From Newly-Created Free-Webmail Identity — Exploitation (locked: unlock with TL Creds)
- Sentinel: Auto-Publish Without Verification Step — Data Manipulation / Missing Authorization (locked: unlock with TL Creds)
- Sentinel: Single Source Filing Breach Notices Against Multiple Impersonated Brands — Campaign / Lateral Spread (locked: unlock with TL Creds)
- Sigma: Fictitious Filer Identity Not Matching Impersonated Organization — Exploitation (locked: unlock with TL Creds)
- Sigma: Placeholder Contact Phone and Vague Boilerplate Affected-Data Field — Post-Exploitation (locked: unlock with TL Creds)
- Sigma: Insider-Wrongdoing Claim With No Notice Or Counsel On Unverified High-Count Filing — C2/Impact (locked: unlock with TL Creds)
- Breach-Portal Submission Impersonating a Vendor via Free-Webmail / Non-Corporate Reporter — Exploitation (locked: unlock with TL Creds)
- Breach Filing With Anachronistic Dates and Implausible Breach/Discovery Gap — Post-Exploitation (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sample indicators (1 of 18)

Defanged, TLP:CLEAR.

- Domain: `gmail[.]com`

Full set of 18 indicators unlocks with TL Creds: https://threadlinqs.com/tl-creds

## Sources

- [Maine breach portal abused to publish fake data breach disclosures](https://www.bleepingcomputer.com/news/security/maine-breach-portal-abused-to-publish-fake-data-breach-disclosures/)
- [Maine disables data breach notification portal after fake disclosures](https://www.bleepingcomputer.com/news/security/maine-disables-data-breach-notification-portal-after-fake-disclosures/)
- [Maine Takes Data Breach Reporting Portal Offline After Fake VRChat and Discord Filings](https://cybersecuritynews.com/maine-data-breach-portal-offline/)
- [Maine Govt Portal Lists 10M Discord Data Breach Notice, But Filing Shows Red Flags](https://hackread.com/maine-govt-portal-discord-data-breach-notice/)
- [UPDATED: Someone Filed A Fake VRChat Data Breach Notice To Maine's Attorney General](https://www.uploadvr.com/vrchat-maine-attorney-general-fake-data-breach-notice/)
- [VRChat says Data Breach notification filed with Maine Attorney General was Fake](https://www.cybersecurity-insiders.com/vrchat-says-data-breach-notification-filed-with-maine-attorney-general-was-fake/)
- [Maine Data Breach Notification Portal Disabled After Fake Discord and VRChat Reports - Service Disruption Analysis](https://www.rescana.com/post/maine-data-breach-notification-portal-disabled-after-fake-discord-and-vrchat-reports-service-disruption-analysis)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-0792
