Accidental Inclusion: National Security Adviser Michael Waltz accidentally added journalist Jeffrey Goldberg to a Signal group chat titled "Houthi PC small group."
Sensitive Data Shared: The chat included messages from Secretary of Defense Pete Hegseth detailing exact launch times for F-18s and drones, strike windows, and real-time operational updates just hours before attacks commenced. Example: `1215et: F-18s LAUNCH (1st strike package)`.
Real-Time Intelligence: Waltz shared live updates, such as confirming a target ("their top missile guy") was in a building that subsequently collapsed.
Official Downplaying: Despite the specificity, officials including Hegseth, DNI Tulsi Gabbard, CIA Director John Ratcliffe, and President Trump asserted that no classified information or "war plans" were shared.
Security Risks: Experts consulted by *The Atlantic* confirmed that discussing such details on non-secure channels poses significant national security risks, potentially endangering US personnel if intercepted.
Why this matters: This breach highlights critical vulnerabilities in government communication practices. Sharing precise operational timings, even if retroactively claimed unclassified, could allow adversaries to anticipate actions, putting military operations and personnel at risk. It underscores the tension between secure communication protocols and the apparent practices of some high-level officials.
The controversy began when *The Atlantic* reported being accidentally included in a Signal chat where senior Trump officials discussed upcoming military action against Houthi targets in Yemen on March 15, 2025. Despite subsequent denials from the administration that classified "war plans" were shared, *The Atlantic*, citing public interest and the officials' downplaying of the incident, published the specific messages.
Messages from Secretary of Defense Pete Hegseth provided a minute-by-minute timeline, including:
`11:44 AM ET`: Confirmation of favorable weather and mission go-ahead from CENTCOM.
`12:15 PM ET`: F-18s launch (1st strike package).
`1:45 PM ET`: Start of F-18 strike window and drone launch (MQ-9s).
`2:15 PM ET`: Estimated time for first bombs dropping via drones.
`3:36 PM ET`: Start of F-18 2nd strike and Tomahawk launches.
Hegseth sent this information over Signal approximately 31 minutes before the first launch and two hours before a key strike window, concluding with "We are currently clean on OPSEC" and "Godspeed to our Warriors."
Further messages included National Security Adviser Michael Waltz updating the group on a successful strike: "VP. Building collapsed. Had multiple positive ID... The first target – their top missile guy – we had positive ID of him walking into his girlfriend’s building and it’s now collapsed." Vice President J.D. Vance responded "Excellent," and CIA Director John Ratcliffe added, "A good start."
The administration objected to the full release, citing the sensitive nature of internal deliberations, but maintained the information wasn't classified. The incident exposes a potentially dangerous gap in operational security and raises questions about how sensitive military information is handled and communicated at the highest levels.
Q: Was the information shared actually classified?
A: Top administration officials, including the President, DNI, and CIA Director, stated the information was not classified. However, security experts and the nature of the details (exact timings, real-time target status) suggest it was highly sensitive operational information that would typically warrant protection. *The Atlantic* published the messages partly because officials downplayed their significance.
Q: What are the risks of using apps like Signal for sensitive government communication?
A: While Signal offers end-to-end encryption, using commercial apps for potentially classified or highly sensitive operational details carries risks. These include accidental inclusion of unauthorized individuals (as happened here), potential vulnerabilities in the app or device security, and the lack of oversight and logging typical of official government communication systems.
Understand the critical importance of operational security (OPSEC) in military actions.
Recognize that breaches can occur through seemingly secure channels if proper protocols aren't followed.
Be aware of potential discrepancies between official statements and the details revealed through investigative reporting.
This incident serves as a case study on the challenges of maintaining security in an age of rapid digital communication.
The use of commercial messaging apps for sensitive government communications continues to be debated. What measures do you think should be in place to prevent such security lapses? Let us know your thoughts!
*Share this article with others who need to stay ahead of this trend!*
[Link to Twitter/X Share] [Link to LinkedIn Share] [Link to Reddit Share]
The Atlantic: Here Are the Attack Plans That Trump’s Advisers Shared on Signal{:}
The Atlantic: The Trump Administration Accidentally Texted Me Its War Plans{:}
This Friday marks a critical deadline for the reauthorization of Section 702 of the Foreign Intelligence Surveillance Act (FISA), a vital co...
Donald Trump's recent appointment of businessman Bill Pulte as interim Director of National Intelligence (ODNI) has ignited a political fire...
The U.S. government's ability to collect crucial foreign intelligence is facing an imminent threat as Section 702 of the Foreign Intelligenc...
Emails obtained by the Associated Press reveal that former FBI Director Kash Patel participated in a 'VIP snorkel' at the USS Arizona Memori...
⚠ Disclaimer: Yanuki provides article summaries and links for reference only. Yanuki does not endorse, verify, or guarantee the accuracy of third-party sources. Please review original sources and verify information independently. Managed by the Yanuki Data Engine. Full Disclaimer