Yesterday, for more than four hours, U.S. air traffic was grounded, with no new domestic flights taking off. The proximate cause was a data overload within air traffic control systems. However, questions remain regarding what the underlying cause was, and whether a nefarious actor was involved. Today, still not knowing who or what was ultimately responsible, we briefly look at the broader cyber vulnerabilities that the United States faces and the political problems that have popped up as a result of this particular incident.
0:00 Yesterday's Ground Stop 2:32 The White House's Political Problems 4:50 Ongoing U.S. Cyber Vulnerabilities 6:53 Potential Cyber Suspects
The appearance of U.S. Department of Defense (DoD), EU, and NATO visual information does not imply or constitute an endorsement.
AI Generated·May contain errors
The Trump administration said that there
was no evidence of a cyber attack.
And yet, what they were describing
was exactly consistent with a cyber attack.
Let's rewind a moment.
Pity anyone trying to fly inside of the United States yesterday.
Or today.
Or tomorrow.
Or for a while until all of the dominoes get sorted out.
Yesterday afternoon, U.S. Air Traffic Control issued
a ground stop for flights traveling over
the United States. Their systems have become unstable,
leaving hundreds of thousands of
people stranded, and only giving some relief
to international travelers on the coastlines
who are immediately leaving the U.S. region of control.
It was only the second such ground stop
since September 11, 2001,
which immediately created a sense of unease in the country.
It did not help that there was very little explanation
from officials during that period.
A press conference at the White House began
a little after 8 p.m. Eastern to finally burst the bubble.
Secretary of Homeland Security Mark Wayne Mullin
and Secretary of Transportation Sean Duffy gave the official word.
They cited that the cause
was the system suffering from a data overload.
While also downplaying the possibility of a cyber attack,
AI infiltration, or anything of that sort,
they said that nothing is completely certain
and that we cannot rule out those possibilities.
And indeed, the very first question
from the press pool immediately sent us back to speculating.
Isn't an overload of data consistent with a cyber attack?
And the answer was awkward ambiguity.
Basically, White House officials
were describing the symptom of the disease,
not identifying the disease itself.
Accidental overloads are commonplace, of course,
but that still leaves the question of what
the underlying cause of the shutdown was.
Now, I want to be very careful
as we describe what is happening further.
I have no special insider knowledge of what is actually happening.
I know that this will come as a surprise,
but even though I make these lifelike videos
of Iran's supreme leader,
they still do not invite me to their secret planning sessions.
And I would also wager that both
this and the Microsoft outage the day before were both
ordinary failures.
Nonetheless, it is still worth discussing
the political situation here, and how there
are cyber vulnerabilities that adversaries could exploit,
even if that was not actually
the case here.
And we need to go back to the press conference
as the starting point of our discussion.
Part of why there is ample speculation about what happened
is the lack of a sense of control from
officials, both before and during the press conference.
It speaks to an underlying problem
that the White House has.
There has not been a press secretary since Caroline Leavitt stepped
down. Unless you count this debacle,
which is not really the counterpoint that the technical
technical facts would make it seem like.
The lack of coordination in the White House
was playing out on the national stage,
and you could see that even in the lack of guidance for Mullin
and Duffy as they conducted
the press conference.
In fact, their preferred underlying explanation for who was responsible
for the situation was counterproductive.
The press conference often devolved into
a discussion of the effectiveness
of leadership of the Trump administration,
which did not play well after four hours of public confusion.
The finger pointing instead went to Congress,
which has authorized some funding for upgrading
Federal Aviation Administration systems,
but not what Duffy believes is necessary.
National security officials would agree on this point.
It was also a priority under the previous Secretary
of Transportation, Pete Buttigieg.
The problem with blaming Congress, though,
as anyone with an ounce of political knowledge
would realize, is that Republicans have controlled both chambers
of Congress since January 2025.
Duffy was effectively blaming his own co-partisans.
Awkwardly, that includes, to some extent, Mullin,
who was a senator until March of this year.
I think that this is worth underscoring
as we transition to a post-blue tsunami Congress,
and we wonder both how the remaining Republicans will interact
with the lame duck White House,
and whether the White House will take one
for the team for the long-term health of the party.
If last night was any indication,
there will be a lot of infighting for the next two years.
But back to the cyber vulnerabilities. Ironically,
one of the main arguments against this being
a cyber attack is that the systems are old.
Actually, one of the arguments in favor
of maintaining old analog systems is precisely
how they are obscure and air-gapped,
making them a bit harder for adversaries to reach.
Of course, air gaps are not impossible to breach.
It just takes an infected USB drive to cause them to tumble down.
We have seen notable cases of this with the Stuxnet virus,
ostensibly created to take down Iran's nuclear program.
There was also the Agent.BTZ incident in 2008,
when an infected USB drive spread malware
to Pentagon computers and took more than a year of cleanup to fix.
And actually, the FAA system is in a period of greater vulnerability.
It is transitioning from the old analog system to a modern one,
and there is a yet newer
system that now includes AI tools,
though that is not yet supposed to be plugged into
flight tracking systems.
The point is, attackers can strike any part of a mixed system
and still crash the entire thing,
meaning that the possible entry points have
increased during the transition period.
That said, the switch provides a mundane explanation
for what could have happened here.
As the new portions of the system try
to communicate with the old portions,
the old portions are not configured
to handle everything coming through,
and the system breaks.
That points to an administrator error.
Someone should have figured out
that they would not mesh together in advance,
and accordingly adjust
the interconnectivity setup to avoid the problem.
Then again, the issue with sorting out all
of this is that the security experts behind the scenes
need to identify where the data overflow originated from.
That is a forensics process that could take weeks.
And, in the meantime,
there is no shortage of possible adversaries
that could be responsible for something nefarious.
Indeed, one ongoing news story that has escaped the public's attention
is what appears to be Iranian hackers finding
multiple vulnerabilities in water systems
inside of the United States.
If the ground stop was an Iranian cyber infiltration,
then this would represent a major jump in sophistication.
The water system suffered
from basic vulnerabilities that low-level hackers exploited.
Penetrating a federal
system that has substantially more
oversight requires better cyber expertise.
So even though Iran has the greatest motive here,
given how the Hormuz blockade has left the country with virtually
no new streams of oil revenues and a worthless currency, motive does
not imply capacity, never mind the choice to pull the trigger.
The capacity question might point to a more sophisticated actor.
China immediately comes to mind on the sophistication dimension,
but that would be a bizarre policy for Beijing to pursue.
So let's table that for now,
just bookmarking that the PRC remains on the list of future concerns
if things go off the rails on other diplomatic fronts.
Instead, the more reasonable and still
sophisticated state-level actor would be Russia.
Certainly Europe knows this all too well,
with weekly reports of something mysteriously going wrong somewhere,
and digital fingerprints tracing back to a possible Russian origin.
But it would be weird for the Kremlin to make such an aggressive play
while the Trump administration
is pressing the brakes on aid to Ukraine.
Then again, that has not stopped Moscow
from sharing intelligence with Tehran,
so there may still be a complicated game afoot.
The last plausible state-level actor remaining is North Korea,
given that Pyongyang often trolls for seemingly the sake of trolling.
North Korea has the tools to conduct such an operation,
even if the country is not as capable
as China or Russia.
And speaking of trolling, you always have to leave open the possibility
that some random person accidentally stumbled on a vulnerability
and just decided to have some fun
with it on a Friday night.
As a reminder, though, we have no direct indications of foul play. But
regardless of what the upcoming investigation uncovers,
the above discussion remains relevant.
National security officials have warned
of the vulnerabilities that the United States has
across its infrastructure.
If the ground stop was the result of a more mundane user or mechanical
error, that does nothing to ensure us
that the next one will not be nefarious. Meanwhile,
you can catch up on my non-nefarious schemes
to educate the public by watching yesterday's video
on how Democrats might try
to pass Ukraine aid legislation through Trump's veto.
And if you enjoyed today's video, then please like, share,
and subscribe, and I will see you next time. Take care.