Trump officials mistakenly add journalist to private chat on Yemen attack

Jeffrey Goldberg was mistakenly added to a private chat where Trump officials discussed military strikes on Yemen.


Pop Culture & Art March 25, 2025
Courtesy: AFP

The Trump administration has confirmed that The Atlantic editor-in-chief Jeffrey Goldberg was mistakenly added to a private Signal chat discussing planned U.S. military strikes against the Houthis in Yemen.

The security breach, described as “a shocking leak,” raises concerns over how classified information is handled within the administration.

Goldberg detailed the incident in The Atlantic, revealing that he received a Signal message on March 11 from a user named “Michael Waltz,” later confirmed to be National Security Advisor Mike Waltz. Days later, he was unexpectedly included in a chat with high-level officials, including Secretary of State Marco Rubio, Vice President J.D. Vance, and Defense Secretary Pete Hegseth.

The chat, titled “Houthi PC small group,” contained sensitive discussions about U.S. military actions. Officials debated the timing of strikes, with Vance expressing concerns about European trade benefits and Hegseth warning that delays could make the U.S. appear weak.

Goldberg, realizing the chat was authentic, informed the White House and left the group. The National Security Council confirmed the incident, stating that the situation is under review.

At a press event, Trump distanced himself, stating, “I don’t know anything about it,” while dismissing The Atlantic as “a magazine going out of business.” Critics, including Senator Chris Coons, are calling for a congressional investigation into the use of non-secure communication for military discussions.

The breach highlights risks associated with encrypted messaging apps in government operations and raises legal concerns over record preservation and classified information leaks.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ