Gone quiet · last update Jun 2, 2025 / Colorado

The firebomb attack on a pro-Israel gathering in Boulder, Colorado

Overview · reviewed October 28, 2026

On June 1, 2025, a man using a makeshift flamethrower and incendiary devices attacked a weekly gathering in Boulder, Colorado, calling for the release of Israeli hostages in Gaza, in what the FBI called a "targeted terror attack."[1][2][3] Authorities said the suspect, who was heard yelling "Free Palestine," wounded 12 people and had planned to kill them all.[4][3]

Read the timeline

Follow this story to see new developments when you return.

Authorities said the suspect, who was heard yelling "Free Palestine," wounded 12 people and had planned to kill them all.[4][3]

Coverage over time

Share of tracked outlets · weekly (UTC)

Week of 2025-05-26 (UTC): 8%, 15 of 191 tracked outlets (2 left, 7 center, 6 right)Week of 2025-06-02 (UTC): 30%, 56 of 189 tracked outlets (16 left, 27 center, 13 right)Week of 2025-06-09 (UTC): no coverage from tracked outletsWeek of 2025-06-16 (UTC): no coverage from tracked outletsWeek of 2025-06-23 (UTC): no coverage from tracked outletsWeek of 2025-06-30 (UTC): no coverage from tracked outletsWeek of 2025-07-07 (UTC): no coverage from tracked outletsWeek of 2025-07-14 (UTC): no coverage from tracked outletsWeek of 2025-07-21 (UTC): no coverage from tracked outletsWeek of 2025-07-28 (UTC): no coverage from tracked outletsWeek of 2025-08-04 (UTC): no coverage from tracked outletsWeek of 2025-08-11 (UTC): no coverage from tracked outletsWeek of 2025-08-18 (UTC): no coverage from tracked outletsWeek of 2025-08-25 (UTC): no coverage from tracked outletsWeek of 2025-09-01 (UTC): no coverage from tracked outletsWeek of 2025-09-08 (UTC): no coverage from tracked outletsWeek of 2025-09-15 (UTC): no coverage from tracked outletsWeek of 2025-09-22 (UTC): no coverage from tracked outletsWeek of 2025-09-29 (UTC): no coverage from tracked outletsWeek of 2025-10-06 (UTC): no coverage from tracked outletsWeek of 2025-10-13 (UTC): no coverage from tracked outletsWeek of 2025-10-20 (UTC): no coverage from tracked outletsWeek of 2025-10-27 (UTC): no coverage from tracked outletsWeek of 2025-11-03 (UTC): no coverage from tracked outletsWeek of 2025-11-10 (UTC): no coverage from tracked outletsWeek of 2025-11-17 (UTC): no coverage from tracked outletsWeek of 2025-11-24 (UTC): no coverage from tracked outletsWeek of 2025-12-01 (UTC): no coverage from tracked outletsWeek of 2025-12-08 (UTC): no coverage from tracked outletsWeek of 2025-12-15 (UTC): no coverage from tracked outletsWeek of 2025-12-22 (UTC): no coverage from tracked outletsWeek of 2025-12-29 (UTC): no coverage from tracked outletsWeek of 2026-01-05 (UTC): no coverage from tracked outletsWeek of 2026-01-12 (UTC): no coverage from tracked outletsWeek of 2026-01-19 (UTC): no coverage from tracked outletsWeek of 2026-01-26 (UTC): no coverage from tracked outletsWeek of 2026-02-02 (UTC): no coverage from tracked outletsWeek of 2026-02-09 (UTC): no coverage from tracked outletsWeek of 2026-02-16 (UTC): no coverage from tracked outletsWeek of 2026-02-23 (UTC): no coverage from tracked outletsWeek of 2026-03-02 (UTC): no coverage from tracked outletsWeek of 2026-03-09 (UTC): no coverage from tracked outletsWeek of 2026-03-16 (UTC): no coverage from tracked outletsWeek of 2026-03-23 (UTC): no coverage from tracked outletsWeek of 2026-03-30 (UTC): no coverage from tracked outletsWeek of 2026-04-06 (UTC): no coverage from tracked outletsWeek of 2026-04-13 (UTC): no coverage from tracked outletsWeek of 2026-04-20 (UTC): no coverage from tracked outletsWeek of 2026-04-27 (UTC): no coverage from tracked outletsWeek of 2026-05-04 (UTC): no coverage from tracked outletsWeek of 2026-05-11 (UTC): no coverage from tracked outletsWeek of 2026-05-18 (UTC): no coverage from tracked outletsWeek of 2026-05-25 (UTC): no coverage from tracked outletsWeek of 2026-06-01 (UTC): no coverage from tracked outletsWeek of 2026-06-08 (UTC): no coverage from tracked outletsWeek of 2026-06-15 (UTC): no coverage from tracked outletsWeek of 2026-06-22 (UTC): no coverage from tracked outletsWeek of 2026-06-29 (UTC): no coverage from tracked outletsWeek of 2026-07-06 (UTC): no coverage from tracked outletsWeek of 2026-07-13 (UTC): no coverage from tracked outletsWeek of 2026-07-20 (UTC): no coverage from tracked outletsWeek of 2026-07-27 (UTC): no coverage from tracked outletsWeek of 2026-08-03 (UTC): no coverage from tracked outletsWeek of 2026-08-10 (UTC): no coverage from tracked outletsWeek of 2026-08-17 (UTC): no coverage from tracked outletsWeek of 2026-08-24 (UTC): no coverage from tracked outletsWeek of 2026-08-31 (UTC): no coverage from tracked outletsWeek of 2026-09-07 (UTC): no coverage from tracked outletsWeek of 2026-09-14 (UTC): no coverage from tracked outletsWeek of 2026-09-21 (UTC): no coverage from tracked outletsWeek of 2026-09-28 (UTC): no coverage from tracked outletsWeek of 2026-10-05 (UTC): no coverage from tracked outletsWeek of 2026-10-12 (UTC): no coverage from tracked outletsWeek of 2026-10-19 (UTC): no coverage from tracked outletsWeek of 2026-10-26 (UTC): no coverage from tracked outletsWeek of 2026-11-02 (UTC): no coverage from tracked outletsWeek of 2026-11-09 (UTC): no coverage from tracked outlets, so far

LeftCenterRight

Each bar is the share of the outlets on our Left / Center / Right rating scale that we tracked publishing that week which carried reporting on this story, split by the outlets' ratings.We track more outlets now than in the archive, so a share keeps earlier and later weeks comparable. An outlet counts once a week however much it published, and outlets in one ownership or syndication group count as one on each side they appear on. A rating describes the outlet, not the report. A gap means no such reports were collected that week, not that nothing was reported anywhere. Weeks run Monday to Sunday in UTC, so a report published on a Sunday evening in US Eastern time counts in the next week. 5 more outlets off the scale (not rated, or outside the left-right graphs) also reported; they are not in this chart. See them.

Weekly counts, outlets and reports (2 weeks with coverage)
Outlets on the rating scale that carried this story each week, of the outlets tracked that week, newest first
Week of (UTC)LeftCenterRightOf trackedShareReceipts
Jun 2, 202516271356 of 18930%
May 26, 202527615 of 1918%

Latest coverage

The newest reporting in this story's record.

  1. Jun 1, 2025 · first reported · Headline from WHDH Boston

    Boulder suspect planned to kill group he called ‘Zionist,’ but appeared to have second thoughts - Boston News, Weather, Sports

Background

The attack took place at an outdoor mall where the group had gathered to raise attention to the hostages.[1] FBI Director Kash Patel described it as a terror attack,[5] and police took a male suspect into custody.[6] Officials said the man had appeared to have second thoughts about killing everyone.[3]

Supporting stories (6)
  1. 6 injured, possibly with burns, in a Colorado attack the FBI is investigating as terrorism
  2. What we know about the suspect and victims in the Boulder, Colorado, attack
  3. Boulder suspect backed off his initial plan to kill all in a group he called 'Zionist,' police say
  4. FBI says 8 injured in Colorado attack by man with makeshift flamethrower who yelled ‘Free Palestine’
  5. FBI: Boulder terror attack targeted Israeli supporters, 6 injured
  6. Man attacks Colorado crowd with firebombs, 8 people injured

The full record

Each date is when an update was first reported.

All 7 recorded updates

June 2025

  1. Boulder suspect backed off his initial plan to kill all in a group he called 'Zionist,' police sayHeadline from WFMZ Allentown · 9 outlets
  2. Man attacks Colorado crowd with firebombs, 8 people injuredHeadline from The Jamestown Sun · 14 outlets

Coverage & sources

Read the reports, see how much was collected over time, or compare outlets by political leaning.

Coverage & sources →