رونوشت 🔗
WEBVTT
Kind: captions
Language: en
00:00:00.080 --> 00:00:02.869
BITES, BORDERS, AND BREACHES.
00:00:02.879 --> 00:00:05.229
>> WHERE the digital hits the physical,
00:00:05.239 --> 00:00:06.710
[music] we take the red pill, we break
00:00:06.720 --> 00:00:09.589
the seal. Infallible security, making it
00:00:09.599 --> 00:00:11.910
real. To party on the mic [music]
00:00:11.920 --> 00:00:15.430
tonight,
00:00:15.440 --> 00:00:16.870
turning the darkness [music and singing]
00:00:16.880 --> 00:00:20.390
into
00:00:20.400 --> 00:00:22.630
>> the history of warfare, there is a
00:00:22.640 --> 00:00:25.269
concept that predates the tank, the
00:00:25.279 --> 00:00:28.710
missile, and even the swad. It is the
00:00:28.720 --> 00:00:31.910
concept of the siege. The logic of a
00:00:31.920 --> 00:00:36.790
siege is ruthless but simple. You do not
00:00:36.800 --> 00:00:39.670
fight the enemy's army on the open field
00:00:39.680 --> 00:00:42.709
where they are strong. Instead, you
00:00:42.719 --> 00:00:45.830
surround their casle. You cut off their
00:00:45.840 --> 00:00:50.549
water. You burn their food stores. You
00:00:50.559 --> 00:00:53.350
wait for the systems that sustain their
00:00:53.360 --> 00:00:56.709
life to fail. For the last 20 years, we
00:00:56.719 --> 00:00:59.750
have treated cyber war as a game of
00:00:59.760 --> 00:01:03.189
spies. We imagined it as a digital
00:01:03.199 --> 00:01:05.670
version of James Bond, stealing
00:01:05.680 --> 00:01:08.789
blueprints, reading emails, intercepting
00:01:08.799 --> 00:01:12.310
calls. We treated it as an intelligence
00:01:12.320 --> 00:01:15.270
problem. But the signal we are receiving
00:01:15.280 --> 00:01:18.789
this week, specifically from the Taiwan
00:01:18.799 --> 00:01:21.910
Strait, suggests that the error of
00:01:21.920 --> 00:01:24.630
espionage is over.
00:01:24.640 --> 00:01:28.630
And the era of the siege has begun.
00:01:28.640 --> 00:01:32.230
The data we are about to discuss is not
00:01:32.240 --> 00:01:36.149
just a statistic. It is a declaration of
00:01:36.159 --> 00:01:39.190
intent. The Taiwan National Security
00:01:39.200 --> 00:01:43.670
Bureau has just released numbers that
00:01:43.680 --> 00:01:47.190
should be statistically impossible.
00:01:47.200 --> 00:01:50.710
They are reporting a 1,000%
00:01:50.720 --> 00:01:53.910
increase in cyber attacks targeting the
00:01:53.920 --> 00:01:57.030
island's energy infrastructure.
00:01:57.040 --> 00:01:59.590
1,000%.
00:01:59.600 --> 00:02:02.389
That is not a spike. That is not a
00:02:02.399 --> 00:02:04.630
seasonal trend.
00:02:04.640 --> 00:02:07.030
Is a mobilization.
00:02:07.040 --> 00:02:10.229
We are talking about 2.6 million
00:02:10.239 --> 00:02:14.790
attempts every single day. This is not
00:02:14.800 --> 00:02:17.990
hacking. This is battlefield
00:02:18.000 --> 00:02:20.949
preparation. This is an adversary
00:02:20.959 --> 00:02:23.830
prepositioning digital explosives in the
00:02:23.840 --> 00:02:26.869
power grid in the water treatment plants
00:02:26.879 --> 00:02:30.470
and in the communication nodes. They are
00:02:30.480 --> 00:02:33.430
not trying to steal data. They are
00:02:33.440 --> 00:02:35.910
trying to ensure that when the kinetic
00:02:35.920 --> 00:02:37.830
war begins,
00:02:37.840 --> 00:02:41.509
when the ships launch and the planes
00:02:41.519 --> 00:02:44.229
take off, they don't have to fight for
00:02:44.239 --> 00:02:48.150
the island. They just have to reach out
00:02:48.160 --> 00:02:52.070
and switch it off. But the threat isn't
00:02:52.080 --> 00:02:54.229
just geopolitical.
00:02:54.239 --> 00:02:57.110
It isn't just happening on an island in
00:02:57.120 --> 00:02:58.710
the Pacific.
00:02:58.720 --> 00:03:02.869
It is structural and it is happening on
00:03:02.879 --> 00:03:07.270
your laptop right [music] now and it is
00:03:07.280 --> 00:03:10.550
hiding in the tools we trust to build
00:03:10.560 --> 00:03:13.270
the modern world. Every developer
00:03:13.280 --> 00:03:16.550
watching this show and every executive
00:03:16.560 --> 00:03:20.869
who employs them knows the command npm
00:03:20.879 --> 00:03:24.229
install. It is the heartbeat of modern
00:03:24.239 --> 00:03:26.309
software development.
00:03:26.319 --> 00:03:29.270
We run it dozens of times a day to pull
00:03:29.280 --> 00:03:32.390
in the libraries we need to build our
00:03:32.400 --> 00:03:36.149
apps. And because we know the internet
00:03:36.159 --> 00:03:40.789
is dangerous, we rely on safety flags.
00:03:40.799 --> 00:03:43.589
We use settings that are supposed to
00:03:43.599 --> 00:03:46.390
protect us from malicious code. [music]
00:03:46.400 --> 00:03:48.869
Well, this week, security researchers
00:03:48.879 --> 00:03:51.190
proved that those safety flags are a
00:03:51.200 --> 00:03:55.110
placebo. We have been driving at 100 m
00:03:55.120 --> 00:03:58.229
an hour trusting a seat belt that was
00:03:58.239 --> 00:04:00.789
never actually bolted to the frame.
00:04:00.799 --> 00:04:03.350
Package gate has shattered the trust
00:04:03.360 --> 00:04:05.990
model of the global software supply
00:04:06.000 --> 00:04:09.509
chain. And [music] finally we are going
00:04:09.519 --> 00:04:13.509
to count the cost. We often talk about
00:04:13.519 --> 00:04:16.550
cyber risk in the abstract.
00:04:16.560 --> 00:04:20.550
We talk about reputational harm, but
00:04:20.560 --> 00:04:24.469
United Natural Foods, the company, but
00:04:24.479 --> 00:04:27.590
United Natural Foods, the company that
00:04:27.600 --> 00:04:29.909
puts the food on the shelves of Whole
00:04:29.919 --> 00:04:34.310
Foods, just reported a $400 million
00:04:34.320 --> 00:04:35.830
loss.
00:04:35.840 --> 00:04:38.550
Not because of a recession, not because
00:04:38.560 --> 00:04:42.310
of inflation, but because a cyber attack
00:04:42.320 --> 00:04:45.510
broke the link between the warehouse and
00:04:45.520 --> 00:04:48.710
the truck. We are seeing what
Load full transcript
happens
00:04:48.720 --> 00:04:52.150
when just in time logistics meets just
00:04:52.160 --> 00:04:56.070
in time ransomware.
00:04:56.080 --> 00:04:59.350
I am Barat Mataparti.
00:04:59.360 --> 00:05:02.950
Welcome to Bites, Borders, and Breaches.
00:05:02.960 --> 00:05:05.990
Tonight we are moving past the headlines
00:05:06.000 --> 00:05:09.029
to understand the structural failures
00:05:09.039 --> 00:05:10.710
underneath.
00:05:10.720 --> 00:05:14.150
The system is blinking red. Let's find
00:05:14.160 --> 00:05:18.550
out why. Welcome back. Let's open our
00:05:18.560 --> 00:05:22.790
first file. Securing the borders.
00:05:22.800 --> 00:05:24.710
I want to start with a cultural
00:05:24.720 --> 00:05:27.270
touchstone that perfectly illustrates
00:05:27.280 --> 00:05:30.070
the reality we are facing in the
00:05:30.080 --> 00:05:31.670
Pacific.
00:05:31.680 --> 00:05:35.909
Think about Mr. Robot, specifically the
00:05:35.919 --> 00:05:39.510
59 hack. If you remember the show, the
00:05:39.520 --> 00:05:42.150
goal of the hackers wasn't to steal
00:05:42.160 --> 00:05:44.150
money for themselves.
00:05:44.160 --> 00:05:48.310
It wasn't to leak embarrassing emails.
00:05:48.320 --> 00:05:50.629
The goal was to destabilize the
00:05:50.639 --> 00:05:54.230
infrastructure of society itself,
00:05:54.240 --> 00:05:58.230
to erase deprecott, to freeze the
00:05:58.240 --> 00:06:02.070
banking system, to cause physical chaos
00:06:02.080 --> 00:06:04.469
through digital means.
00:06:04.479 --> 00:06:07.510
What we are seeing in Taiwan right now
00:06:07.520 --> 00:06:10.629
is a state sponsored rehearsal for a
00:06:10.639 --> 00:06:13.189
physical 59.
00:06:13.199 --> 00:06:15.909
The data coming out of Taipei this week
00:06:15.919 --> 00:06:19.110
is staggering, even for those of us who
00:06:19.120 --> 00:06:23.029
track this daily. The Taiwan National
00:06:23.039 --> 00:06:27.510
Security Bureau reports a 1,000%
00:06:27.520 --> 00:06:30.710
increase in attacks targeting critical
00:06:30.720 --> 00:06:32.390
infrastructure,
00:06:32.400 --> 00:06:35.670
specifically energy and water, [music]
00:06:35.680 --> 00:06:39.749
throughout late 2025 and into January
00:06:39.759 --> 00:06:41.830
2026.
00:06:41.840 --> 00:06:45.670
Let's contextualize that number because
00:06:45.680 --> 00:06:49.670
in cyber security we get numb to big
00:06:49.680 --> 00:06:54.870
numbers. A 20% increase is a trend. A
00:06:54.880 --> 00:06:59.749
50% increase is a surge. A 1,000%
00:06:59.759 --> 00:07:02.870
increase is a campaign.
00:07:02.880 --> 00:07:07.670
We are talking about an average of 2.63
00:07:07.680 --> 00:07:12.710
million attempts per day. Now, a skeptic
00:07:12.720 --> 00:07:15.430
might ask, if they are attacking 2
00:07:15.440 --> 00:07:17.990
million times a day, why hasn't the
00:07:18.000 --> 00:07:21.350
power gone out yet? Why are the lights
00:07:21.360 --> 00:07:24.309
still on in Taipei? And that is the red
00:07:24.319 --> 00:07:27.110
pill in sight for this segment.
00:07:27.120 --> 00:07:30.550
The fact that the power is still on is
00:07:30.560 --> 00:07:33.749
part of the plan. China is not trying to
00:07:33.759 --> 00:07:36.790
turn the lights off today. If they turn
00:07:36.800 --> 00:07:39.589
the lights off today, it is an act of
00:07:39.599 --> 00:07:44.390
war. It provokes a response. It alerts
00:07:44.400 --> 00:07:48.469
the international community. No, they
00:07:48.479 --> 00:07:51.350
are trying to ensure they can turn them
00:07:51.360 --> 00:07:53.670
off tomorrow.
00:07:53.680 --> 00:07:58.070
That is battlefield preparation.
00:07:58.080 --> 00:08:01.029
Let's look at this from a military
00:08:01.039 --> 00:08:02.790
perspective.
00:08:02.800 --> 00:08:05.270
If you are planning an invasion of
00:08:05.280 --> 00:08:09.749
Taiwan, a D-Day style amphibious landing
00:08:09.759 --> 00:08:12.550
is a nightmare scenario.
00:08:12.560 --> 00:08:16.950
The Taiwan Strait is rough. The beaches
00:08:16.960 --> 00:08:18.950
are fortified.
00:08:18.960 --> 00:08:22.309
The urban density makes urban compact
00:08:22.319 --> 00:08:27.029
incredibly costly. It is messy. It is
00:08:27.039 --> 00:08:30.469
expensive. It carries a high risk of
00:08:30.479 --> 00:08:31.990
failure.
00:08:32.000 --> 00:08:36.070
But imagine a different opening move.
00:08:36.080 --> 00:08:38.949
Imagine if you can compromise the SCADA
00:08:38.959 --> 00:08:42.230
systems that control the voltage
00:08:42.240 --> 00:08:45.110
regulation of the grid.
00:08:45.120 --> 00:08:48.310
Imagine if you can plant logic bombs in
00:08:48.320 --> 00:08:49.990
the PLC's,
00:08:50.000 --> 00:08:53.590
the programmable logic controllers that
00:08:53.600 --> 00:08:56.870
manage the water pressure.
00:08:56.880 --> 00:09:00.389
You don't need to storm the beaches. You
00:09:00.399 --> 00:09:05.110
simply initiate a switch off sequence.
00:09:05.120 --> 00:09:08.310
You degrade the radar so they can't see
00:09:08.320 --> 00:09:10.150
you coming.
00:09:10.160 --> 00:09:14.230
You degrade the civilian communication
00:09:14.240 --> 00:09:17.030
so that the government can't issue
00:09:17.040 --> 00:09:19.750
orders. You cut the power to the
00:09:19.760 --> 00:09:22.310
hospitals and the traffic lights to
00:09:22.320 --> 00:09:25.509
incite panic in the streets.
00:09:25.519 --> 00:09:28.870
You break the will of the population
00:09:28.880 --> 00:09:31.750
before the first soldier steps onto the
00:09:31.760 --> 00:09:35.750
sand. This is a fundamental shift in
00:09:35.760 --> 00:09:37.269
doctrine.
00:09:37.279 --> 00:09:41.670
We are moving from cyber espionage which
00:09:41.680 --> 00:09:45.030
is about information dominance to cyber
00:09:45.040 --> 00:09:49.350
siege which is about physical dominance.
00:09:49.360 --> 00:09:53.350
The attackers are mapping the terrain.
00:09:53.360 --> 00:09:56.310
They are testing the response times of
00:09:56.320 --> 00:09:59.350
the Taiwanese
defenders.
00:09:59.360 --> 00:10:02.150
Every failed attack that we see in the
00:10:02.160 --> 00:10:05.590
logs is actually a successful
00:10:05.600 --> 00:10:07.269
reconnaissance mission for the
00:10:07.279 --> 00:10:09.030
adversary.
00:10:09.040 --> 00:10:12.150
They are probing the firewall to see how
00:10:12.160 --> 00:10:15.030
fast the security operation center
00:10:15.040 --> 00:10:16.790
responds.
00:10:16.800 --> 00:10:19.350
They are learning where the walls are
00:10:19.360 --> 00:10:24.550
strong and where the motor is crumbling.
00:10:24.560 --> 00:10:29.110
Now let's pivot to the Middle East where
00:10:29.120 --> 00:10:32.470
we are seeing the inverse of this
00:10:32.480 --> 00:10:34.069
strategy.
00:10:34.079 --> 00:10:37.030
In Taiwan, the infrastructure is being
00:10:37.040 --> 00:10:40.389
attacked from the outside to disable the
00:10:40.399 --> 00:10:44.150
state. In Iran, the infrastructure is
00:10:44.160 --> 00:10:47.829
being weaponized from the inside by the
00:10:47.839 --> 00:10:49.430
state.
00:10:49.440 --> 00:10:51.990
Reports confirmed this week that the
00:10:52.000 --> 00:10:56.150
Iranian regime has implemented a near
00:10:56.160 --> 00:10:59.509
total internet blackout.
00:10:59.519 --> 00:11:03.350
Connectivity has dropped to 1%. Let's be
00:11:03.360 --> 00:11:08.630
clear about what 1% means. It means the
00:11:08.640 --> 00:11:12.470
global internet is gone. No WhatsApp, no
00:11:12.480 --> 00:11:15.750
Instagram, no encrypted signal out to
00:11:15.760 --> 00:11:19.110
the world. They have cut off their own
00:11:19.120 --> 00:11:22.790
domestic halal internet. The national
00:11:22.800 --> 00:11:25.990
information network they spent billions
00:11:26.000 --> 00:11:29.509
building. They are even actively jamming
00:11:29.519 --> 00:11:32.389
starling signals to prevent satellite
00:11:32.399 --> 00:11:33.910
bypass.
00:11:33.920 --> 00:11:37.670
Why? To suppress the latest wave of
00:11:37.680 --> 00:11:39.269
protests.
00:11:39.279 --> 00:11:42.310
This is the kill switch as a weapon of
00:11:42.320 --> 00:11:45.350
state survival. We often talk about
00:11:45.360 --> 00:11:48.870
digital sovereignity in this industry.
00:11:48.880 --> 00:11:52.310
We frame it as a positive thing. Nations
00:11:52.320 --> 00:11:55.670
owning their own data, protecting their
00:11:55.680 --> 00:11:59.430
own borders from foreign interference.
00:11:59.440 --> 00:12:02.069
But Iran is proving that digital
00:12:02.079 --> 00:12:04.790
sovereignity can quickly become a
00:12:04.800 --> 00:12:08.710
digital prison. When the state owns the
00:12:08.720 --> 00:12:10.230
cables,
00:12:10.240 --> 00:12:14.069
when the state owns the ISPs,
00:12:14.079 --> 00:12:18.150
when the state controls the DNS route,
00:12:18.160 --> 00:12:21.750
they control the reality.
00:12:21.760 --> 00:12:24.550
Think of the Hunger Games.
00:12:24.560 --> 00:12:27.030
When the uprising begins in the
00:12:27.040 --> 00:12:29.670
districts,
what is the first thing
00:12:29.680 --> 00:12:32.949
President Snow does? He cuts the video
00:12:32.959 --> 00:12:37.350
feed. He stops the transmission because
00:12:37.360 --> 00:12:39.430
if the other districts can't see the
00:12:39.440 --> 00:12:42.150
rebellion, then the rebellion isn't
00:12:42.160 --> 00:12:45.190
real. The Iranian regime is applying the
00:12:45.200 --> 00:12:48.790
exact logic to digital age. They are
00:12:48.800 --> 00:12:51.829
using the kill switch to hide the body
00:12:51.839 --> 00:12:55.910
count. If no video can get out, the
00:12:55.920 --> 00:12:56.790
crackdown [music]
00:12:56.800 --> 00:13:00.389
did not happen. The blackout creates a
00:13:00.399 --> 00:13:04.389
void where atrocities can occur without
00:13:04.399 --> 00:13:06.230
witness.
00:13:06.240 --> 00:13:09.829
It is the ultimate censorship.
00:13:09.839 --> 00:13:13.509
The censorship of physics. So what is
00:13:13.519 --> 00:13:16.230
the lesson for us sitting here in the
00:13:16.240 --> 00:13:20.310
west? It is that infrastructure is never
00:13:20.320 --> 00:13:22.949
neutral. We like to think of the
00:13:22.959 --> 00:13:27.910
internet as a utility like air or water.
00:13:27.920 --> 00:13:31.590
something that just exists. But these
00:13:31.600 --> 00:13:34.949
two stories prove that the internet is a
00:13:34.959 --> 00:13:37.990
terrain. In Taiwan, the grid is a target
00:13:38.000 --> 00:13:41.350
for an external conqueror. In Iran, the
00:13:41.360 --> 00:13:44.470
grid is a cage built by an internal
00:13:44.480 --> 00:13:47.030
oppressor. Whether it is being attacked
00:13:47.040 --> 00:13:49.829
or weaponized, the physical layer of the
00:13:49.839 --> 00:13:52.629
internet, the cables, the routers and
00:13:52.639 --> 00:13:55.430
the satellites has become the primary
00:13:55.440 --> 00:13:58.150
theater of conflict.
00:13:58.160 --> 00:14:01.110
We used to say the internet interprets
00:14:01.120 --> 00:14:03.990
censorship as damage and routes around
00:14:04.000 --> 00:14:08.150
it. That was true in 1990.
00:14:08.160 --> 00:14:12.069
In 2026, the internet does what the
00:14:12.079 --> 00:14:14.870
person with the biggest switch tells it
00:14:14.880 --> 00:14:16.790
to do.
00:14:16.800 --> 00:14:20.550
Let us move to the code. Open the file
00:14:20.560 --> 00:14:23.430
decoding the bites.
00:14:23.440 --> 00:14:27.110
I want to talk about trust. If you work
00:14:27.120 --> 00:14:30.949
in software development or if you manage
00:14:30.959 --> 00:14:34.230
a team that does, you know that our
00:14:34.240 --> 00:14:38.550
entire industry runs on trust.
00:14:38.560 --> 00:14:42.310
We trust the compiler not to insert back
00:14:42.320 --> 00:14:45.829
doors. We trust the browser to render
00:14:45.839 --> 00:14:48.230
the page correctly.
00:14:48.240 --> 00:14:51.189
And most of all, we trust the package
00:14:51.199 --> 00:14:55.670
manager. When a developer types npm
00:14:55.680 --> 00:14:59.509
install to download a
library, they are
00:14:59.519 --> 00:15:03.269
engaging in a massive act of faith.
00:15:03.279 --> 00:15:05.990
They are trusting that the code they are
00:15:06.000 --> 00:15:09.030
pulling from the internet code written
00:15:09.040 --> 00:15:12.069
by a stranger hosted on a public
00:15:12.079 --> 00:15:15.189
repository is safe.
00:15:15.199 --> 00:15:19.590
We are not naive. We know the risks. We
00:15:19.600 --> 00:15:22.470
know that the open-source ecosystem is
00:15:22.480 --> 00:15:27.590
the wild west. So we use safety flags.
00:15:27.600 --> 00:15:31.670
We use commands like ignore scripts for
00:15:31.680 --> 00:15:34.230
the nontechnical audience.
00:15:34.240 --> 00:15:37.990
Let me explain what that does.
00:15:38.000 --> 00:15:41.590
Many software packages come with install
00:15:41.600 --> 00:15:43.269
scripts.
00:15:43.279 --> 00:15:46.550
These are little programs that run
00:15:46.560 --> 00:15:49.670
automatically as soon as you download
00:15:49.680 --> 00:15:51.670
the package.
00:15:51.680 --> 00:15:54.470
They are meant to do the helpful things
00:15:54.480 --> 00:15:58.069
like compiling code or setting up
00:15:58.079 --> 00:15:59.910
configurations,
00:15:59.920 --> 00:16:03.030
but they are also the perfect place to
00:16:03.040 --> 00:16:05.749
hide malware.
00:16:05.759 --> 00:16:09.590
So, smart developers use the ignore
00:16:09.600 --> 00:16:13.430
scripts flag. It tells the system,
00:16:13.440 --> 00:16:16.389
download the code, but do not let it run
00:16:16.399 --> 00:16:18.389
any scripts.
00:16:18.399 --> 00:16:22.150
Just give me the files. It is the
00:16:22.160 --> 00:16:25.749
digital equivalent of a safety catch on
00:16:25.759 --> 00:16:27.590
a firearm.
00:16:27.600 --> 00:16:31.590
This flag is our shield. It is the
00:16:31.600 --> 00:16:34.710
primary defense against supply chain
00:16:34.720 --> 00:16:36.230
attacks.
00:16:36.240 --> 00:16:39.990
But on January 27th,
00:16:40.000 --> 00:16:43.749
security researchers at Koi revealed
00:16:43.759 --> 00:16:46.310
something terrifying.
00:16:46.320 --> 00:16:49.749
They dubbed it package [music] gate.
00:16:49.759 --> 00:16:52.150
It is a cluster of zeroday
00:16:52.160 --> 00:16:55.110
vulnerabilities across every major
00:16:55.120 --> 00:17:00.550
JavaScript package manager npm, PNPM,
00:17:00.560 --> 00:17:06.470
VT and B. The vulnerability is simple
00:17:06.480 --> 00:17:08.470
and devastating. [music]
00:17:08.480 --> 00:17:11.750
The safety catch doesn't work.
00:17:11.760 --> 00:17:14.949
attackers found a way to bypass the
00:17:14.959 --> 00:17:18.630
ignore scripts flag entirely.
00:17:18.640 --> 00:17:21.189
They discovered that if they manipulated
00:17:21.199 --> 00:17:22.949
the package.json
00:17:22.959 --> 00:17:26.710
file in a specific way using a technique
00:17:26.720 --> 00:17:29.669
called manifest confusion, they could
00:17:29.679 --> 00:17:32.390
trick the package manager into executing
00:17:32.400 --> 00:17:36.390
the code anyway. This means simply
00:17:36.400 --> 00:17:39.110
downloading a malicious package even
00:17:39.120 --> 00:17:41.830
with your shields up, even with your
00:17:41.840 --> 00:17:44.789
safety settings enabled, can execute
00:17:44.799 --> 00:17:48.470
code on your developer laptop.
00:17:48.480 --> 00:17:52.870
It can steal your SSH keys. It can read
00:17:52.880 --> 00:17:55.669
your AWS credentials.
00:17:55.679 --> 00:17:58.549
It can inject a backdoor into the
00:17:58.559 --> 00:18:01.669
software you are building for your
00:18:01.679 --> 00:18:04.789
customers. I call this the placebo
00:18:04.799 --> 00:18:07.029
safety switch.
00:18:07.039 --> 00:18:09.830
And to understand why this is so
00:18:09.840 --> 00:18:11.430
dangerous,
00:18:11.440 --> 00:18:14.710
I want you to think about Jurassic Park.
00:18:14.720 --> 00:18:17.510
It is the perfect analogy for this
00:18:17.520 --> 00:18:21.029
situation. Remember the tour vehicles,
00:18:21.039 --> 00:18:23.909
the Ford Explorers?
00:18:23.919 --> 00:18:27.029
The tourists are sitting in the car. The
00:18:27.039 --> 00:18:30.470
T-Rex is approaching and they look at
00:18:30.480 --> 00:18:33.750
the dashboard. The [music] screen says
00:18:33.760 --> 00:18:36.870
locking mechanism engaged.
00:18:36.880 --> 00:18:40.070
They see the green light. They hear the
00:18:40.080 --> 00:18:43.990
click. They feel safe.
00:18:44.000 --> 00:18:47.590
But the power was out. The locks were
00:18:47.600 --> 00:18:50.950
electronic. Without power, the locking
00:18:50.960 --> 00:18:55.669
mechanism was physically useless.
00:18:55.679 --> 00:18:57.510
The T-Rex
00:18:57.520 --> 00:18:59.430
did not care about the light on the
00:18:59.440 --> 00:19:01.190
dashboard.
00:19:01.200 --> 00:19:03.430
It did not care about the user
00:19:03.440 --> 00:19:07.669
interface. It opened the door anyway.
00:19:07.679 --> 00:19:11.350
For years, developers have been using
00:19:11.360 --> 00:19:14.710
ignore scripts thinking the door was
00:19:14.720 --> 00:19:16.230
locked.
00:19:16.240 --> 00:19:18.549
We have been telling our compliance
00:19:18.559 --> 00:19:22.150
teams, "It's okay. We use the safety
00:19:22.160 --> 00:19:24.630
flags." Package gate proves that the
00:19:24.640 --> 00:19:27.510
T-Rex could walk right in the whole
00:19:27.520 --> 00:19:28.789
time.
00:19:28.799 --> 00:19:31.510
This shatters the trust model of the
00:19:31.520 --> 00:19:35.270
software supply chain. The tools we use
00:19:35.280 --> 00:19:38.070
to build the software are now the
00:19:38.080 --> 00:19:41.110
primary attack vector. We are not
00:19:41.120 --> 00:19:43.510
fighting malware that infects the final
00:19:43.520 --> 00:19:46.630
product. We are fighting malware that
00:19:46.640 --> 00:19:50.630
infects the assembly line itself.
00:19:50.640 --> 00:19:53.510
And [music] if the new tools are broken,
00:19:53.520 --> 00:19:56.390
the old ones are rotting.
00:19:56.400 --> 00:19:59.750
While we were
worrying about JavaScript
00:19:59.760 --> 00:20:03.510
and modern web frameworks, the ghost of
00:20:03.520 --> 00:20:07.990
the past came back to haunt us. On
00:20:08.000 --> 00:20:10.070
January 26th,
00:20:10.080 --> 00:20:12.950
CISA, the Cyber Security and
00:20:12.960 --> 00:20:16.470
Infrastructure Security Agency, added a
00:20:16.480 --> 00:20:20.310
new vulnerability to its known exploited
00:20:20.320 --> 00:20:22.070
catalog
00:20:22.080 --> 00:20:23.590
CVE
00:20:23.600 --> 00:20:25.350
2026
00:20:25.360 --> 00:20:27.350
2461.
00:20:27.360 --> 00:20:30.549
This is a critical authentication bypass
00:20:30.559 --> 00:20:35.190
in GNU in utils tnetd.
00:20:35.200 --> 00:20:38.630
Now I can hear some of you laughing.
00:20:38.640 --> 00:20:42.549
Telnet? Who uses TNET in 2026?
00:20:42.559 --> 00:20:45.110
For the uninitiated, Telnet is an
00:20:45.120 --> 00:20:47.909
ancient protocol. It was used to log
00:20:47.919 --> 00:20:50.950
into computers remotely before we had
00:20:50.960 --> 00:20:52.470
encryption.
00:20:52.480 --> 00:20:55.909
It sends your password in plain text. It
00:20:55.919 --> 00:20:59.270
is insecure by design. It should have
00:20:59.280 --> 00:21:03.270
been dead 20 years ago. But here is the
00:21:03.280 --> 00:21:05.270
incredible part.
00:21:05.280 --> 00:21:08.789
This vulnerability allows anyone to log
00:21:08.799 --> 00:21:12.149
in as root highest level of
00:21:12.159 --> 00:21:13.750
administrator
00:21:13.760 --> 00:21:18.070
without a password at all. And this bug
00:21:18.080 --> 00:21:21.350
was introduced in 2015.
00:21:21.360 --> 00:21:24.789
It has been sitting there dormant in the
00:21:24.799 --> 00:21:29.590
code for 11 years. 11 years of digital
00:21:29.600 --> 00:21:32.549
asbesistos. We are living in digital
00:21:32.559 --> 00:21:35.190
buildings constructed with toxic
00:21:35.200 --> 00:21:38.950
materials we forgot about.
00:21:38.960 --> 00:21:43.830
You might ask, okay, but really who uses
00:21:43.840 --> 00:21:45.350
Telnet?
00:21:45.360 --> 00:21:48.789
The answer is machines that don't get
00:21:48.799 --> 00:21:50.470
updated.
00:21:50.480 --> 00:21:54.950
Countless IoT devices, smart cameras,
00:21:54.960 --> 00:21:57.990
industrial controllers in factories,
00:21:58.000 --> 00:22:00.950
legacy Linux systems running in the
00:22:00.960 --> 00:22:03.669
basement of major banks.
00:22:03.679 --> 00:22:05.990
These systems were [music] built 10
00:22:06.000 --> 00:22:08.549
years ago, flashed with a version of
00:22:08.559 --> 00:22:11.669
Linux that contained this bug and then
00:22:11.679 --> 00:22:15.110
bolted to a wall and forgotten. This is
00:22:15.120 --> 00:22:17.590
the ghost of 2015.
00:22:17.600 --> 00:22:21.029
It reminds me of the movie Halloween.
00:22:21.039 --> 00:22:23.830
The killer is not a new monster. [music]
00:22:23.840 --> 00:22:26.630
It is not some high-tech AI threat that
00:22:26.640 --> 00:22:29.430
we have never seen before. It is Michael
00:22:29.440 --> 00:22:32.470
Myers. It's the same threat from 40
00:22:32.480 --> 00:22:35.830
years ago walking back into your life
00:22:35.840 --> 00:22:39.029
because you didn't finish the job. You
00:22:39.039 --> 00:22:42.230
thought you killed Telnet in the '90s,
00:22:42.240 --> 00:22:45.270
but it was just waiting in the basement,
00:22:45.280 --> 00:22:48.630
in your smart fridge, in your HWAC
00:22:48.640 --> 00:22:51.270
controller, waiting for someone to
00:22:51.280 --> 00:22:52.789
knock.
00:22:52.799 --> 00:22:56.230
This highlights the absolute danger of
00:22:56.240 --> 00:22:59.909
code depth. In our industry, new
00:22:59.919 --> 00:23:03.190
features get the budget, new features
00:23:03.200 --> 00:23:06.630
get the glory, maintenance gets the
00:23:06.640 --> 00:23:09.260
leftovers, and eventually the neglect
00:23:09.270 --> 00:23:09.830
[music]
00:23:09.840 --> 00:23:13.510
comes back to haunt you. We are building
00:23:13.520 --> 00:23:16.630
skyscrapers on top of the foundations
00:23:16.640 --> 00:23:20.070
that are slowly turning to dust.
00:23:20.080 --> 00:23:22.950
Let's talk about the impact.
00:23:22.960 --> 00:23:26.310
Open the file dissecting the breach. We
00:23:26.320 --> 00:23:29.510
often talk about cyber attacks in terms
00:23:29.520 --> 00:23:31.750
of data.
00:23:31.760 --> 00:23:36.230
500 GB stolen, 10 million records
00:23:36.240 --> 00:23:37.909
exposed.
00:23:37.919 --> 00:23:41.270
These are abstract numbers. They are
00:23:41.280 --> 00:23:43.750
hard to visualize.
00:23:43.760 --> 00:23:47.510
But businesses don't run on data. They
00:23:47.520 --> 00:23:49.830
run on solveny.
00:23:49.840 --> 00:23:53.909
They run on cash flow. They run on the
00:23:53.919 --> 00:23:56.870
ability to move a physical object from
00:23:56.880 --> 00:24:01.190
point A to point B. And this week we got
00:24:01.200 --> 00:24:04.390
a very brutal lesson in what happens
00:24:04.400 --> 00:24:06.789
when the digital world breaks the
00:24:06.799 --> 00:24:11.990
physical. United Natural Foods, UNFI.
00:24:12.000 --> 00:24:14.630
You might not know the name, but you
00:24:14.640 --> 00:24:16.789
know their work.
00:24:16.799 --> 00:24:19.750
They are the primary distributor for
00:24:19.760 --> 00:24:23.110
Whole Foods and thousands of other
00:24:23.120 --> 00:24:25.990
independent grocerers across North
00:24:26.000 --> 00:24:27.830
America.
00:24:27.840 --> 00:24:30.549
They are the reason the shelves have
00:24:30.559 --> 00:24:35.029
yogurt and kale when you walk in. UNFI
00:24:35.039 --> 00:24:38.950
just revealed a $400 million loss in
00:24:38.960 --> 00:24:42.070
sales for the last quarter.
00:24:42.080 --> 00:24:46.149
$400 million. Let's break down what that
00:24:46.159 --> 00:24:48.789
number actually represents.
00:24:48.799 --> 00:24:51.269
That is not a regulatory fine. [music]
00:24:51.279 --> 00:24:53.750
That is not a consulting fee for
00:24:53.760 --> 00:24:57.190
incident response. That is revenue
that
00:24:57.200 --> 00:25:01.750
simply vanished. Why? Because a cyber
00:25:01.760 --> 00:25:04.789
attack disrupted their ability to move
00:25:04.799 --> 00:25:06.310
trucks.
00:25:06.320 --> 00:25:10.070
It corrupted the distribution software.
00:25:10.080 --> 00:25:13.510
Drivers couldn't get manifests. They did
00:25:13.520 --> 00:25:17.669
not know what to load. Warehouses could
00:25:17.679 --> 00:25:21.750
not pick orders. The robots did not know
00:25:21.760 --> 00:25:24.470
where the pellets were. The food was
00:25:24.480 --> 00:25:28.630
there. The trucks were there. The demand
00:25:28.640 --> 00:25:31.510
was there. But the code that connects
00:25:31.520 --> 00:25:36.149
them was broken. This is solveny risk.
00:25:36.159 --> 00:25:39.029
We have optimized our economy for
00:25:39.039 --> 00:25:41.590
maximum efficiency.
00:25:41.600 --> 00:25:45.669
We call it just in time logistics.
00:25:45.679 --> 00:25:48.070
We don't keep inventory in the back room
00:25:48.080 --> 00:25:49.669
anymore.
00:25:49.679 --> 00:25:53.510
That costs money. We rely on the trucks
00:25:53.520 --> 00:25:57.430
arriving exactly at 400 p.m. to restock
00:25:57.440 --> 00:26:00.710
the shelf for the 5 p.m. rush.
00:26:00.720 --> 00:26:05.190
But in time logistics means we have zero
00:26:05.200 --> 00:26:07.750
buffer. We have stripped away the
00:26:07.760 --> 00:26:10.310
redundancy to save pennies. And in doing
00:26:10.320 --> 00:26:13.830
so, we created a system that shatters at
00:26:13.840 --> 00:26:17.190
the first sight of stress. A digital
00:26:17.200 --> 00:26:20.549
hiccup at the distributor level leads to
00:26:20.559 --> 00:26:23.029
physical hunger at the neighborhood
00:26:23.039 --> 00:26:25.430
level. It is the scenario from
00:26:25.440 --> 00:26:27.190
Interstellar.
00:26:27.200 --> 00:26:31.350
In that film, the blight destroys the
00:26:31.360 --> 00:26:35.029
food supply. It is an ecological
00:26:35.039 --> 00:26:38.630
collapse. In our reality, it is a
00:26:38.640 --> 00:26:40.310
ransomware.
00:26:40.320 --> 00:26:43.510
The blight is not biological. It is
00:26:43.520 --> 00:26:47.750
digital. But the result is the same.
00:26:47.760 --> 00:26:52.070
Empty shelves, spoiled fresh goods.
00:26:52.080 --> 00:26:56.230
If you are a CFO watching this, look at
00:26:56.240 --> 00:26:58.070
UNFI.
00:26:58.080 --> 00:27:01.269
Your CISO is not asking for budget to
00:27:01.279 --> 00:27:03.750
buy a firewall. They are asking for
00:27:03.760 --> 00:27:06.070
budget to protect your ability to
00:27:06.080 --> 00:27:08.470
recognize revenue.
00:27:08.480 --> 00:27:11.350
A cyber attack is no longer an IT
00:27:11.360 --> 00:27:15.190
ticket. It is a half billion hole in
00:27:15.200 --> 00:27:18.149
your balance sheet.
00:27:18.159 --> 00:27:22.310
And finally, let's look upwards.
00:27:22.320 --> 00:27:26.870
The European Space Agency, ESA, suffered
00:27:26.880 --> 00:27:28.950
a significant breach this week.
00:27:28.960 --> 00:27:34.710
attackers exposed 500 gigabytes of data.
00:27:34.720 --> 00:27:37.110
But they did not just steal employee
00:27:37.120 --> 00:27:38.630
emails.
00:27:38.640 --> 00:27:42.230
They did not steal HR records.
00:27:42.240 --> 00:27:45.350
They stole technical schematics for
00:27:45.360 --> 00:27:49.990
partners like SpaceX and Airbus.
00:27:50.000 --> 00:27:52.950
This is a classic case of island
00:27:52.960 --> 00:27:54.549
hopping.
00:27:54.559 --> 00:27:56.389
Think about it from the attacker's
00:27:56.399 --> 00:27:58.230
perspective.
00:27:58.240 --> 00:28:01.590
SpaceX is a hard target. They have
00:28:01.600 --> 00:28:03.990
worldclass security.
00:28:04.000 --> 00:28:06.710
They are paranoid.
00:28:06.720 --> 00:28:08.950
They are essentially a defense
00:28:08.960 --> 00:28:10.870
contractor.
00:28:10.880 --> 00:28:13.909
But the European Space Agency,
00:28:13.919 --> 00:28:16.710
they are a research institution.
00:28:16.720 --> 00:28:20.710
They are collaborative by nature. Their
00:28:20.720 --> 00:28:24.870
culture is built on sharing data.
00:28:24.880 --> 00:28:27.430
They are the island.
00:28:27.440 --> 00:28:30.870
The attackers hacked the island to get
00:28:30.880 --> 00:28:32.870
to the mainland.
00:28:32.880 --> 00:28:36.310
They hacked the research partner to get
00:28:36.320 --> 00:28:38.149
the blueprints for the defense
00:28:38.159 --> 00:28:41.269
contractor. Orbit is the new high
00:28:41.279 --> 00:28:44.470
ground. [music] And just like in
00:28:44.480 --> 00:28:47.350
Moonrakaker, where the villain steals
00:28:47.360 --> 00:28:49.909
the space shuttle blueprints to build
00:28:49.919 --> 00:28:53.590
his own empire, our adversaries are
00:28:53.600 --> 00:28:55.510
doing the same.
00:28:55.520 --> 00:29:00.070
China, Russia, North Korea. They know
00:29:00.080 --> 00:29:03.430
that the future of warfare and economy
00:29:03.440 --> 00:29:06.470
is in low Earth orbit.
00:29:06.480 --> 00:29:09.590
But R&D is expensive.
00:29:09.600 --> 00:29:12.389
Developing a new rocket engine takes 10
00:29:12.399 --> 00:29:16.710
years and billions of dollars. Stealing
00:29:16.720 --> 00:29:18.389
is cheap.
00:29:18.399 --> 00:29:21.669
Why spend 10 years developing a rocket
00:29:21.679 --> 00:29:25.350
engine when you can just download the
00:29:25.360 --> 00:29:28.789
schematics from a partner's insecure
00:29:28.799 --> 00:29:32.389
server. This breach reminds us that your
00:29:32.399 --> 00:29:36.549
security is only as strong as your
00:29:36.559 --> 00:29:38.950
weakest partner.
00:29:38.960 --> 00:29:41.750
You can build a fortress.
00:29:41.760 --> 00:29:44.470
You can have the best firewalls in the
00:29:44.480 --> 00:29:48.710
world, but if you give the keys to a
00:29:48.720 --> 00:29:52.710
friend who lives in a glass house, you
00:29:52.720 --> 00:29:56.230
are exposed. So, what is the signal this
00:29:56.240 --> 00:29:57.830
week?
00:29:57.840 --> 00:30:02.149
If we connect the dots between Taiwan,
00:30:02.159 --> 00:30:05.190
the package gate vulnerability and the
00:30:05.200 --> 00:30:09.750
UNFI loss, the theme is fragility.
00:30:09.760 --> 00:30:12.950
We have built a world that is fast,
00:30:12.960 --> 00:30:16.310
efficient, and interconnected.
00:30:16.320 --> 00:30:18.710
But we stripped away the buffers. We
00:30:18.720 --> 00:30:21.350
built a power grid that can be switched
00:30:21.360 --> 00:30:25.350
off remotely because we wanted smart
00:30:25.360 --> 00:30:28.950
meters. We built a software supply chain
00:30:28.960 --> 00:30:31.909
where the safety switches are placeos
00:30:31.919 --> 00:30:35.029
because we wanted faster deployment
00:30:35.039 --> 00:30:36.470
times.
00:30:36.480 --> 00:30:39.110
We built a food distribution network
00:30:39.120 --> 00:30:43.430
that loses $400 million because the
00:30:43.440 --> 00:30:46.789
computers went down for a week because
00:30:46.799 --> 00:30:50.389
we wanted just in time inventory.
00:30:50.399 --> 00:30:53.350
The 10-fold siege on Taiwan is a
00:30:53.360 --> 00:30:56.389
warning. The enemy is preparing the
00:30:56.399 --> 00:30:58.070
battlefields.
00:30:58.080 --> 00:31:01.029
They are testing the locks. They are
00:31:01.039 --> 00:31:04.230
finding the cracks. And as we saw with
00:31:04.240 --> 00:31:07.750
the TNET bug, some of those cracks have
00:31:07.760 --> 00:31:11.110
been open for a decade.
00:31:11.120 --> 00:31:13.669
The question is not when will they
00:31:13.679 --> 00:31:16.950
attack. The data shows they are
00:31:16.960 --> 00:31:21.669
attacking right now, 2.6 million times a
00:31:21.679 --> 00:31:24.230
day. The question is when they turn the
00:31:24.240 --> 00:31:29.029
key, will our defenses hold or will we
00:31:29.039 --> 00:31:32.710
realize our safety switch was a placebo
00:31:32.720 --> 00:31:35.750
all along? I am Barat Mataparti.
00:31:35.760 --> 00:31:40.549
This is bites, borders, and breaches.
00:31:40.559 --> 00:31:42.389
Stay vigilant,
00:31:42.399 --> 00:31:45.990
stay paranoid, and for God's sake, PATCH
00:31:46.000 --> 00:31:47.190
YOUR
00:31:47.200 --> 00:31:49.992
>> BORDERS AND BREACHES.
00:31:50.002 --> 00:31:52.230
[music] The lesson it teaches infallible
00:31:52.240 --> 00:31:54.549
security. Stand in the guard. The truth
00:31:54.559 --> 00:31:57.200
is heavy.