Artificial Intelligence Policy Tracker

AI incident ·

Purportedly AI-Generated Facebook Pages Allegedly Targeted Australian Rules Football Club Geelong Cats With Fabricated Harmful Claims

1 news report Snapshot 7 Sep 2026
On this page 6 sections

In brief

An AI system built by Synthetic Media Generation Technology Developers, Synthetic Image Generation Technology Developers and 1 other and deployed by Synthetic Media Creators, Information Manipulation Actors In Australia and 1 other allegedly harmed Social Media Users, Residents Of Geelong Victoria and 8 others.

Risk domain
Not classified
Occurred
Coverage
1 reportJul 2026

What happened

Purportedly AI-generated Facebook pages reportedly published false stories about the Geelong Football Club, including fabricated criminal allegations, illnesses, deaths, and a nonexistent bushfire evacuation warning. The club reported the pages to Meta, which later removed at least one page after complaints, while other misleading content reportedly remained online.

Laws on record for this risk area

No instrument on record yet covers this risk area where it happened. See the open queue.

Matched from the record's risk category and country to the instruments in effect recorded here: a law listed covers the area, which is not a finding that it applies to this incident. A reviewer can correct the match in the repository (data/external/incident_overrides.yaml).

News reports (1)

Titles link to the original publisher; report text is not reproduced here.

  1. AI-slop pages targeting the Geelong Cats, Meta asked to step in
    geelongadvertiser.com.au · Alexander Blain

Who was involved

Alleged harmed party
Social Media Users, Residents Of Geelong Victoria, General Public Of Australia, General Public, Geelong Football Club, Geelong Cats Players, Geelong Cats Fans, Geelong Cats, Facebook Users, Epistemic Integrity

Classification (MIT AI Risk Repository taxonomy)

Risk domain
—
Risk subdomain
—
Causal entity
—
Intent
—
Timing
—
Harm level
—
Sectors
—
Countries
—

Source record: incident #1594 on the AI Incident Database · all 1 report