“Pentagon not forthcoming on how troops are injured in Iran war”, 29 September 2026 (Photo via Washington Examiner — the original report)
As it ran on the front
The Pentagon took months. Nobody has said exactly how many, only that it was more than the breach should have taken to notice, and more than it takes the department to send someone to Capitol Hill for a different kind of accounting.
That accounting is the one Secretary Pete Hegseth and General Dan Caine haven't given. Nearly five months have passed since the two men last stood at a podium and told reporters how the Iran war is going for the more than 440 U.S. service members hurt in it since March. Five months is long enough for a war to have a season, an anniversary, a policy review. It is not, apparently, long enough for a briefing.…
…(cont) Ten days before the breach story ran, on September 19, five Pentagon officials told The Washington Post, under condition of anonymity, that the true death toll in the Iran war runs higher than the department has said publicly — at least 22 service members dead, more than the number the Pentagon has confirmed. The administration that calls itself the "most transparent administration in history" did not dispute the figure. It simply hasn't given one of its own.
Go back further, to September 3, and the shape gets clearer. That's when The Wall Street Journal reported Hegseth had quietly extended American deployments in the Middle East into 2027 — 50,000 troops, fighter squadrons, warships, kept in place "in part to give the president options," in the Journal's phrase. Nobody voted on that extension. Nobody stood at the Pentagon podium to announce it. It surfaced the way the death toll surfaced and the way the breach surfaced: after the fact, through people who would not put their names on it.
Line them up and the pattern isn't incompetence, it's operation. An institution that takes months to find its own data breach, goes five months without accounting for its own wounded, and extends its own war a year and a half without saying so out loud, is not failing to find things. It has decided the finding is optional — for itself, if not for the three million people whose files it lost, or the families still waiting on a number.
🍺
“Notice the order: they find the money to keep 50,000 troops there through 2027 before they find the words to tell you 440 of them got hurt doing it. That's not a scheduling problem, that's a choice about who gets told what and when. When the same building loses track of three million people's data and can't produce a body count on the same week, the "can't find it" stops being an excuse and starts being the policy.”
“Look, operational security exists for a reason — you don't want the enemy reading a press release to count our wounded, that's just basic wartime discipline. The breach thing is unrelated, totally different systems, and frankly they caught it, which is more than you can say for — wait, they didn't catch it for months, did they. Okay, that one's not great. But the deployment extension, giving the president "options," that's just prudent planning, not a — why does that sound like I'm defending a blank check.”
A Pentagon data breach took months to discover and exposed sensitive information on nearly 3 million people, a defense official said. Charlie D'Agata reports.
The Pentagon has failed its audit eight years running - the only major federal agency never to pass one Military Times, 19 December 2025
Nearly five months have passed, and more than 440 U.S. service members have been injured in the Middle East since the last time War Secretary Pete Hegseth and Gen. Dan Caine, the chairman of the Joint Chiefs of Staff, briefed the media on the state of the Iran war.
This page is a back-issue: the story as it ran, receipts as they were. The current edition is at the front. The byline is a pen name for a column drafted by a machine and checked by the editor: how this is made.