Gone quiet · last update Dec 3, 2025 / Pete Hegseth

The Signal chat leak of US strike plans on Yemen

Overview · reviewed October 26, 2026

In March 2025, the editor in chief of The Atlantic, Jeffrey Goldberg, was added to a Signal group chat in which President Donald Trump's national security team discussed imminent strikes on Yemen's Houthis, and Defense Secretary Pete Hegseth posted details including the timing of warplane launches.[1][2] National Security Adviser Mike Waltz, who had added Goldberg, took responsibility and was removed from the post in May.[3][4] In December 2025 the Pentagon's found that Hegseth's use of Signal risked endangering US troops and their mission; the Pentagon called the report a "total exoneration."[5][6]

Read the timeline

Follow this story to see new developments when you return.

National Security Adviser Mike Waltz, who had added Goldberg, took responsibility and was removed from the post in May.[3][4] In December 2025 the Pentagon's found that Hegseth's use of Signal risked endangering US troops and their mission; the Pentagon called the report a "total exoneration."[5][6]

Coverage over time

Share of tracked outlets · weekly (UTC)

Week of 2025-03-24 (UTC): 38%, 73 of 194 tracked outlets (22 left, 37 center, 14 right)Week of 2025-03-31 (UTC): 14%, 29 of 205 tracked outlets (8 left, 17 center, 4 right)Week of 2025-04-07 (UTC): no coverage from tracked outletsWeek of 2025-04-14 (UTC): no coverage from tracked outletsWeek of 2025-04-21 (UTC): 23%, 47 of 206 tracked outlets (14 left, 24 center, 9 right)Week of 2025-04-28 (UTC): 38%, 78 of 204 tracked outlets (18 left, 32 center, 28 right)Week of 2025-05-05 (UTC): no coverage from tracked outletsWeek of 2025-05-12 (UTC): no coverage from tracked outletsWeek of 2025-05-19 (UTC): no coverage from tracked outletsWeek of 2025-05-26 (UTC): no coverage from tracked outletsWeek of 2025-06-02 (UTC): 5%, 9 of 189 tracked outlets (2 left, 5 center, 2 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): 5%, 10 of 184 tracked outlets (2 left, 2 center, 6 right)Week 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): 22%, 39 of 177 tracked outlets (14 left, 18 center, 7 right)Week 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

LeftCenterRightLighter bar: this week so far

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. 9 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 (7 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
Dec 1, 20251418739 of 17722%
Jul 14, 202522610 of 1845%
Jun 2, 20252529 of 1895%
Apr 28, 202518322878 of 20438%
Apr 21, 20251424947 of 20623%
Mar 31, 2025817429 of 20514%
Mar 24, 202522371473 of 19438%

Latest coverage

The newest reporting in this story's record.

  1. Dec 2, 2025 · first reported · Headline from NBC 5 Dallas-Fort Worth

    Pentagon's Signalgate review finds Pete Hegseth violated military regulations

Background

The chat came to light on March 24, 2025, when Jeffrey Goldberg reported that he had been included in a Signal thread with Vice President JD Vance, Defense Secretary Pete Hegseth, National Security Adviser Mike Waltz and other officials.[7][1] Goldberg wrote that he had at first doubted it was authentic.[7] Hegseth said "nobody was texting war plans."[8] The Atlantic then published the entire chat, showing that Hegseth had given the exact timing of warplane launches and bomb drops before the strikes,[2] and sources told CNN the details were highly classified when he wrote them.[2] Trump stood by Waltz, calling the episode a "glitch,"[9] and later said he would not "fire people" over it.[10] The Associated Press noted that officials playing down the leak had once condemned Hillary Clinton's use of a private email server.[11]

Read the full background (3 more paragraphs)

Investigations followed. Judge James Boasberg ordered agencies to preserve Signal messages sent from March 11 to 15,[12] and the top Republican and Democrat on the Senate Armed Services Committee asked for an investigation.[13] On April 3 the Pentagon's acting inspector general, its internal watchdog, opened a review of Hegseth's use of Signal.[14] Later that month CNN reported that Hegseth had shared detailed plans for the operation in a second Signal chat, on his personal phone, that included his wife, his brother and his lawyer.[15] The AP reported that he had an internet line that bypassed Pentagon security protocols set up in his office to use Signal on a personal computer.[16] In June the watchdog was examining whether aides had been asked to delete his Signal messages, the AP reported.[17]

Waltz paid the price first. On May 1, 2025, Trump announced that he would nominate Waltz as ambassador to the United Nations, after reports that he was leaving the national security adviser's job.[4][18] The day before, Waltz had been photographed at a Cabinet meeting using a Signal-like app that can archive messages.[19] At his confirmation hearing in July he faced questions about the chat and insisted that he had not technically been fired.[20]

The inspector general reported in December 2025, after a more than eight-month investigation. The watchdog concluded that the information Hegseth shared was classified and that his use of Signal violated department policy and risked compromising sensitive information, which could have endangered troops and their mission.[6][5] The Pentagon pointed to the conclusion that Hegseth had the authority to declassify the strike information and called the report a "total exoneration."[5] The strikes themselves are followed in the arc on the Houthis' attacks and the US strikes on Yemen.

Supporting stories (20)
  1. Trump Officials Texted War Plans to a Group Chat in a Secure App That Included a Journalist
  2. The Atlantic releases the entire Signal chat showing Hegseth's detailed attack plans against Houthis
  3. Mike Waltz, under the spotlight, takes ‘full responsibility’ for Signal group-chat breach
  4. Trump nominates Mike Waltz for UN ambassador in major shake-up of national security team
  5. Pentagon watchdog finds Hegseth’s use of Signal posed risk to U.S. personnel, AP sources say
  6. Pentagon's Signalgate review finds Pete Hegseth violated military regulations
  7. Trump national security team messaged plans for Yemen strikes to Atlantic editor in chief
  8. Pete Hegseth claims ‘nobody was texting war plans’ in first comments since Yemen strike group text scandal
  9. Trump defends national security adviser Mike Waltz amid fallout from Signal texts on Houthi attack
  10. Trump stands by security team, says he won’t ‘fire people’ over Signal leak
  11. In their own words: Trump officials shrugging off Signal leak once decried Clinton’s server
  12. Judge will order government to preserve Signal messages about Houthi military strike - Boston News, Weather, Sports
  13. Was classified information shared? Senators overseeing military request probe into Signal leak
  14. Pentagon watchdog to review Hegseth’s use of Signal app to convey plans for Houthi strike
  15. Hegseth had a second Signal chat where he shared details of Yemen strike, New York Times reports
  16. Hegseth had an unsecured internet line set up in his office to connect to Signal, AP sources say
  17. Pentagon watchdog investigates if staffers were asked to delete Hegseth’s Signal messages
  18. Michael Waltz expected to depart as Trump's national security adviser, sources say
  19. Photo appears to show Mike Waltz using Signal-like app that can archive messages
  20. Trump’s UN nominee faces scrutiny over Signal chat but emerges largely unscathed

The full record

Each date is when an update was first reported.

All 22 recorded updates

June 2025

  1. Pentagon watchdog investigates if staffers were asked to delete Hegseth’s Signal messagesHeadline from Minneapolis Star Tribune · 9 outlets

March 2025

  1. Mikey Madison texts with government officials in ‘SNL’ cold open spoof of Signal group chat leakHeadline from KTVZ Bend · 7 outlets
  2. Trump stands by security team, says he won’t ‘fire people’ over Signal leakHeadline from FOX 6 Milwaukee · 9 outlets
  3. Was classified information shared? Senators overseeing military request probe into Signal leakHeadline from WFMZ Allentown · 10 outlets
  4. Judge will order government to preserve Signal messages about Houthi military strike - Boston News, Weather, SportsHeadline from WHDH Boston · 19 outlets
  5. Mike Waltz, under the spotlight, takes ‘full responsibility’ for Signal group-chat breachHeadline from The Boston Globe · 4 outlets
  6. The Atlantic releases the entire Signal chat showing Hegseth's detailed attack plans against HouthisHeadline from KING 5 Seattle · 38 outlets
  7. In their own words: Trump officials shrugging off Signal leak once decried Clinton’s serverHeadline from The Boston Globe · 20 outlets
  8. Trump defends national security adviser Mike Waltz amid fallout from Signal texts on Houthi attackHeadline from CBS News · 10 outlets
  9. Trump national security team messaged plans for Yemen strikes to Atlantic editor in chiefHeadline from New York Post · 12 outlets
  10. Trump Officials Texted War Plans to a Group Chat in a Secure App That Included a JournalistHeadline from Military.com · 32 outlets
  11. Pete Hegseth claims ‘nobody was texting war plans’ in first comments since Yemen strike group text scandalHeadline from New York Post · 6 outlets

Coverage & sources

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

Coverage & sources →