TRANSCRIÇÃO 🔗
WEBVTT
Kind: captions
Language: en
00:00:00.080 --> 00:00:02.869
BITES, BORDERS, AND BREACHES.
00:00:02.879 --> 00:00:05.510
>> Where the digital hits the physical, we
00:00:05.520 --> 00:00:07.590
take the red pill, we break the seal.
00:00:07.600 --> 00:00:10.230
Infallible security, making it real.
00:00:10.240 --> 00:00:15.430
Party on the mic tonight.
00:00:15.440 --> 00:00:21.910
Turning the darkness into
00:00:21.920 --> 00:00:26.390
>> time. We think of time as a constant, a
00:00:26.400 --> 00:00:29.830
universal measurement, a sequence of
00:00:29.840 --> 00:00:32.790
seconds ticking away on a clock
00:00:32.800 --> 00:00:35.910
indifferent to human suffering.
00:00:35.920 --> 00:00:39.270
We measure our quarters, our sprints,
00:00:39.280 --> 00:00:43.110
and our fiscal years by it. But in the
00:00:43.120 --> 00:00:46.709
domain of cyber warfare, time is not a
00:00:46.719 --> 00:00:50.150
measurement. It is a weapon. They know
00:00:50.160 --> 00:00:53.189
our calendar better than we do.
00:00:53.199 --> 00:00:56.069
They know when our security operation
00:00:56.079 --> 00:01:00.630
centers run on skeleton crews. They know
00:01:00.640 --> 00:01:05.189
when our executives are skiing in aspen.
00:01:05.199 --> 00:01:09.270
They know when we lower our shields to
00:01:09.280 --> 00:01:14.230
roast chestnuts and open presents.
00:01:14.240 --> 00:01:18.230
And most importantly, they know exactly
00:01:18.240 --> 00:01:21.429
when the temperature drops low enough.
00:01:21.439 --> 00:01:24.550
That turning off the power isn't just an
00:01:24.560 --> 00:01:28.950
inconvenience, it is a death sentence.
00:01:28.960 --> 00:01:34.069
In episode 3, we warned you about Crink.
00:01:34.079 --> 00:01:39.030
The alliance of China, Russia, Iran, and
00:01:39.040 --> 00:01:42.069
North Korea. We told you they were
00:01:42.079 --> 00:01:45.190
industrializing destruction. We told you
00:01:45.200 --> 00:01:48.230
the war was moving from the screen to
00:01:48.240 --> 00:01:52.550
the street. Well, this week they didn't
00:01:52.560 --> 00:01:55.190
just move to the street, they moved to
00:01:55.200 --> 00:01:58.709
the thermostat. And they moved to the
00:01:58.719 --> 00:02:01.190
sky. While we were celebrating the
00:02:01.200 --> 00:02:04.149
holidays, Eastern Europe was fighting
00:02:04.159 --> 00:02:06.950
off a winter siege.
00:02:06.960 --> 00:02:10.469
Romanian energy grids, Ukrainian heating
00:02:10.479 --> 00:02:14.150
plants hit with precision timing to
00:02:14.160 --> 00:02:18.070
maximize human suffering. This wasn't
00:02:18.080 --> 00:02:22.229
hacking for money. This was hacking for
00:02:22.239 --> 00:02:24.630
hypothermia.
00:02:24.640 --> 00:02:26.869
And while we were freezing on the
00:02:26.879 --> 00:02:30.390
ground, we looked up and realized the
00:02:30.400 --> 00:02:33.670
sky was full of spice.
00:02:33.680 --> 00:02:38.630
The FCC just banned foreign made drones.
00:02:38.640 --> 00:02:42.150
Finally admitting what we have known for
00:02:42.160 --> 00:02:45.270
years. We have covered our critical
00:02:45.280 --> 00:02:48.390
infrastructure with flying cameras that
00:02:48.400 --> 00:02:52.550
phone home to Beijing. But the rot goes
00:02:52.560 --> 00:02:56.470
deeper than the borders. It goes into
00:02:56.480 --> 00:02:58.630
code itself.
00:02:58.640 --> 00:03:01.750
Tonight we are going to talk about God
00:03:01.760 --> 00:03:02.949
mode.
00:03:02.959 --> 00:03:05.830
We found a vulnerability in the very
00:03:05.840 --> 00:03:09.990
foundation of the modern web, React,
00:03:10.000 --> 00:03:13.030
that lets attackers rewrite the laws of
00:03:13.040 --> 00:03:16.949
physics inside your application.
00:03:16.959 --> 00:03:19.830
And we found a hole in the management
00:03:19.840 --> 00:03:24.470
plane of your servers that lets them own
00:03:24.480 --> 00:03:28.630
the metal itself. And finally, we are
00:03:28.640 --> 00:03:31.589
going to look at the bill.
00:03:31.599 --> 00:03:35.110
Jaguar Land Rover just posted their
00:03:35.120 --> 00:03:36.710
financials.
00:03:36.720 --> 00:03:43.270
A 43% drop in cars built. Billions gone,
00:03:43.280 --> 00:03:45.910
not because of a recession, but because
00:03:45.920 --> 00:03:50.470
of a hack that happened months ago.
00:03:50.480 --> 00:03:54.470
And in South Korea, an e-commerce giant
00:03:54.480 --> 00:03:57.910
is trying to pay for a massive breach
00:03:57.920 --> 00:04:02.229
with its own funny money, proving that
00:04:02.239 --> 00:04:05.429
privacy is now just a commodity to be
00:04:05.439 --> 00:04:09.190
traded for coupons. The siege is
00:04:09.200 --> 00:04:13.190
invisible, folks, but the casualties are
00:04:13.200 --> 00:04:14.869
real.
00:04:14.879 --> 00:04:18.550
Welcome back to Bites, Borders, and
00:04:18.560 --> 00:04:22.230
Breaches. I am Barat Mataparti.
00:04:22.240 --> 00:04:25.749
I don't just read the headlines. I read
00:04:25.759 --> 00:04:29.030
the source code of the apocalypse so you
00:04:29.040 --> 00:04:32.230
don't have to. Tonight, we are
00:04:32.240 --> 00:04:35.270
conducting a forensic autopsy on the
00:04:35.280 --> 00:04:38.469
three signals that defined the start of
00:04:38.479 --> 00:04:40.390
2026.
00:04:40.400 --> 00:04:43.990
First, securing the borders. We are
00:04:44.000 --> 00:04:46.710
going to expose the calendar kill chain.
00:04:46.720 --> 00:04:49.270
We aren't just looking at the attacks on
00:04:49.280 --> 00:04:53.030
Romania and Ukraine. We are analyzing
00:04:53.040 --> 00:04:56.950
why the enemy chose December 26th,
00:04:56.960 --> 00:05:00.390
Boxing Day to strike. And we will look
00:05:00.400 --> 00:05:04.390
at the FCC's new ban on foreign drones.
00:05:04.400 --> 00:05:07.830
We will ask, is a ban enough or is it
00:05:07.840 --> 00:05:10.629
too late to remove the hardware Trojan
00:05:10.639 --> 00:05:13.749
from our skies? Second, decoding the
00:05:13.759 --> 00:05:15.270
bytes.
00:05:15.280 --> 00:05:19.110
We are
Load full transcript
entering god mode. We will break
00:05:19.120 --> 00:05:24.310
down react to shell as CVS's 10.0
00:05:24.320 --> 00:05:27.830
vulnerability that turns your fancy web
00:05:27.840 --> 00:05:31.590
apps into open doors for Chinese thread
00:05:31.600 --> 00:05:36.469
groups. And we will look at the HP1 view
00:05:36.479 --> 00:05:40.310
hack. This isn't just an OS
00:05:40.320 --> 00:05:41.909
vulnerability.
00:05:41.919 --> 00:05:45.029
It is a flaw in the management plane
00:05:45.039 --> 00:05:48.390
that controls the physical metal of the
00:05:48.400 --> 00:05:51.909
server. We will show you why your
00:05:51.919 --> 00:05:55.350
endpoint detection tools are blind to
00:05:55.360 --> 00:05:57.510
this attack.
00:05:57.520 --> 00:06:01.830
And finally, dissecting the breach, the
00:06:01.840 --> 00:06:05.029
high cost of silence. From the $3
00:06:05.039 --> 00:06:09.670
billion handover at Jaguar Land Rover to
00:06:09.680 --> 00:06:13.909
the voucher hush money scandal at Kong
00:06:13.919 --> 00:06:17.510
where $33 million identities were sold
00:06:17.520 --> 00:06:20.870
out by a rogue insider and the company's
00:06:20.880 --> 00:06:24.629
response was to issue store credit. We
00:06:24.639 --> 00:06:28.070
will show you why privacy has become the
00:06:28.080 --> 00:06:31.270
cheapest asset on the balance sheet. The
00:06:31.280 --> 00:06:34.629
system isn't just blinking red, folks.
00:06:34.639 --> 00:06:39.029
It is freezing over. Take the red pill.
00:06:39.039 --> 00:06:44.790
Let's see how cold it really is outside.
00:06:44.800 --> 00:06:49.029
Let's open our first file. Securing the
00:06:49.039 --> 00:06:52.870
borders. I want you to think about Star
00:06:52.880 --> 00:06:56.309
Wars the Empire Strikes Back,
00:06:56.319 --> 00:07:00.390
specifically the Battle of Hoth.
00:07:00.400 --> 00:07:04.790
The rebels are hiding on an ice planet.
00:07:04.800 --> 00:07:08.070
The environment is hostile.
00:07:08.080 --> 00:07:10.790
It is a world where the elements kill
00:07:10.800 --> 00:07:14.629
you faster than the enemy can. If the
00:07:14.639 --> 00:07:18.070
heating systems fail, everyone freezes
00:07:18.080 --> 00:07:22.070
to death in minutes. The Empire knows
00:07:22.080 --> 00:07:25.990
this. And how do they start the siege?
00:07:26.000 --> 00:07:29.189
They don't send the fleet immediately.
00:07:29.199 --> 00:07:33.029
They don't just bombard from the orbit.
00:07:33.039 --> 00:07:37.589
They send a Viper probe droid, a single
00:07:37.599 --> 00:07:40.790
hovering robot that scans the terrain,
00:07:40.800 --> 00:07:44.230
locks onto the thermal signature of the
00:07:44.240 --> 00:07:47.510
shield generator, and transmits the
00:07:47.520 --> 00:07:50.790
coordinates back to the fleet. This
00:07:50.800 --> 00:07:54.390
week, we saw the battle of Hoth play out
00:07:54.400 --> 00:07:58.390
in Eastern Europe, and we realized that
00:07:58.400 --> 00:08:02.710
our own skies are full of probe droids.
00:08:02.720 --> 00:08:06.309
First, let's talk about the siege.
00:08:06.319 --> 00:08:10.230
We call it the calendar killchain. On
00:08:10.240 --> 00:08:13.990
December 20th, just as officers were
00:08:14.000 --> 00:08:16.869
emptying out for the holidays, the
00:08:16.879 --> 00:08:20.710
Romanian National Water Authority, Appel
00:08:20.720 --> 00:08:23.510
Roma, was hit.
00:08:23.520 --> 00:08:28.390
6 days later, Boxing Day, December 26th,
00:08:28.400 --> 00:08:31.430
the Gentleman Ransomware Group struck
00:08:31.440 --> 00:08:34.949
the Old Tinia Energy Complex.
00:08:34.959 --> 00:08:37.430
Let's pause and look at the target
00:08:37.440 --> 00:08:38.949
selection.
00:08:38.959 --> 00:08:42.070
This wasn't a bank. This wasn't a
00:08:42.080 --> 00:08:43.589
casino.
00:08:43.599 --> 00:08:48.630
Alania provides 30% of Romania's power.
00:08:48.640 --> 00:08:51.910
Appel Roma controls the water supply for
00:08:51.920 --> 00:08:54.230
an entire nation.
00:08:54.240 --> 00:08:57.829
These are what we call life safety
00:08:57.839 --> 00:09:01.910
critical systems. Now look at the timing
00:09:01.920 --> 00:09:05.509
December 26th. Historically
00:09:05.519 --> 00:09:08.470
military commanders have always used
00:09:08.480 --> 00:09:10.389
winter.
00:09:10.399 --> 00:09:13.350
Napoleon was defeated by the Russian
00:09:13.360 --> 00:09:17.590
winter. The German army froze outside
00:09:17.600 --> 00:09:19.269
Stalenrad.
00:09:19.279 --> 00:09:23.030
In cyber warfare, the winter general is
00:09:23.040 --> 00:09:25.430
the holiday schedule.
00:09:25.440 --> 00:09:27.910
But don't think this is just a lucky
00:09:27.920 --> 00:09:32.070
guess. This is Osent
00:09:32.080 --> 00:09:36.389
opensource intelligence weaponization.
00:09:36.399 --> 00:09:39.030
The attackers are scraping your
00:09:39.040 --> 00:09:41.670
corporate LinkedIn pages.
00:09:41.680 --> 00:09:45.269
They are monitoring your happy holidays
00:09:45.279 --> 00:09:49.110
posts to see who is active and who is
00:09:49.120 --> 00:09:53.110
checked out. More terrifyingly, they are
00:09:53.120 --> 00:09:56.710
pinging your email servers to harvest
00:09:56.720 --> 00:10:00.310
out of office auto replies. Every time
00:10:00.320 --> 00:10:03.509
your server automatically replies, I am
00:10:03.519 --> 00:10:07.670
out of the office until January 5th. For
00:10:07.680 --> 00:10:10.389
urgent matters, contact a junior
00:10:10.399 --> 00:10:13.990
employee. You are sending a tactical
00:10:14.000 --> 00:10:17.190
scouting report to the enemy.
00:10:17.200 --> 00:10:21.509
You just told them the decision maker is
00:10:21.519 --> 00:10:25.670
gone. The backup contact is less
00:10:25.680 --> 00:10:27.350
experienced.
00:10:27.360 --> 00:10:31.110
They have a 10day window to operate
00:10:31.120 --> 00:10:33.350
without oversight.
00:10:33.360 --> 00:10:37.190
When they strike on Boxing Day, the
00:10:37.200 --> 00:10:40.630
meanantime to respond doubles.
00:10:40.640 --> 00:10:43.430
The
confusion triples.
00:10:43.440 --> 00:10:46.949
Communication chains are broken because
00:10:46.959 --> 00:10:49.829
the decision makers are on a ski slope
00:10:49.839 --> 00:10:53.990
in the apps with spotty reception.
00:10:54.000 --> 00:10:57.509
They didn't just hack a server. They
00:10:57.519 --> 00:11:00.790
hacked the HR schedule.
00:11:00.800 --> 00:11:04.069
And look at the weapon they used. They
00:11:04.079 --> 00:11:08.069
used Bit Locker. For those who don't
00:11:08.079 --> 00:11:12.310
know, Bit Locker is a legitimate Windows
00:11:12.320 --> 00:11:17.110
security tool. It is designed to encrypt
00:11:17.120 --> 00:11:21.269
your hard drive so that if you lose your
00:11:21.279 --> 00:11:25.910
laptop, a thief can't read your data.
00:11:25.920 --> 00:11:29.350
The gentleman group didn't write a fancy
00:11:29.360 --> 00:11:31.190
new virus.
00:11:31.200 --> 00:11:34.470
They gained administrative access and
00:11:34.480 --> 00:11:38.230
then they turned on Bit Locker.
00:11:38.240 --> 00:11:42.150
They used the systems own immune system
00:11:42.160 --> 00:11:46.069
to kill the host. They locked the energy
00:11:46.079 --> 00:11:49.670
company out of its own control servers
00:11:49.680 --> 00:11:53.190
using the very tools installed to
00:11:53.200 --> 00:11:54.790
protect them.
00:11:54.800 --> 00:11:58.630
This is the definition of living off the
00:11:58.640 --> 00:12:01.990
land. Why build a weapon when you can
00:12:02.000 --> 00:12:04.550
just pick the one sitting on the
00:12:04.560 --> 00:12:06.550
victim's desk?
00:12:06.560 --> 00:12:10.949
Then shift your eyes to Ukraine.
00:12:10.959 --> 00:12:15.269
January 8th, Russian strikes coordinated
00:12:15.279 --> 00:12:18.870
with cyber effects left over 1 million
00:12:18.880 --> 00:12:24.230
people without heat and water.
00:12:24.240 --> 00:12:28.470
temperatures were plunging below zero.
00:12:28.480 --> 00:12:32.069
This is the kinetic effect we predicted
00:12:32.079 --> 00:12:36.069
in episode 2. The goal is not data
00:12:36.079 --> 00:12:39.990
theft. The goal is turn off the heat on
00:12:40.000 --> 00:12:43.430
planet hot and let the cold kill the
00:12:43.440 --> 00:12:45.190
opposition.
00:12:45.200 --> 00:12:48.710
This is siege warfare digitized.
00:12:48.720 --> 00:12:51.670
In the Middle Ages, you surrounded a
00:12:51.680 --> 00:12:56.710
castle and starved them out. In 2026,
00:12:56.720 --> 00:12:59.430
you surround the skater network and
00:12:59.440 --> 00:13:02.550
freeze them out. But how do they know
00:13:02.560 --> 00:13:05.269
where to strike? How do they map the
00:13:05.279 --> 00:13:08.389
infrastructure so perfectly?
00:13:08.399 --> 00:13:11.190
Enter the probe droids.
00:13:11.200 --> 00:13:16.069
On January 7th, the FCC finally dropped
00:13:16.079 --> 00:13:19.590
the hammer. They added specific
00:13:19.600 --> 00:13:23.190
foreignmade uncrrewed aircraft systems,
00:13:23.200 --> 00:13:27.110
drones, to the covered list. Basically,
00:13:27.120 --> 00:13:30.790
a ban. They declared them an
00:13:30.800 --> 00:13:35.509
unacceptable national security risk.
00:13:35.519 --> 00:13:40.550
Why now? Because for the last decade, we
00:13:40.560 --> 00:13:43.269
have been buying the Empire's probe
00:13:43.279 --> 00:13:48.550
droids to inspect our own eco base.
00:13:48.560 --> 00:13:52.230
We used these foreign drones to inspect
00:13:52.240 --> 00:13:54.470
our bridges.
00:13:54.480 --> 00:13:58.870
We use them to survey our power lines.
00:13:58.880 --> 00:14:04.069
We use them to map our water reservoirs.
00:14:04.079 --> 00:14:08.310
We use them to film our weddings. We
00:14:08.320 --> 00:14:12.069
bought them because they were cheap. We
00:14:12.079 --> 00:14:15.990
bought them because they had 4K cameras
00:14:16.000 --> 00:14:18.790
and great battery life.
00:14:18.800 --> 00:14:22.550
We thought we were buying a camera.
00:14:22.560 --> 00:14:25.590
We were actually installing a hardware
00:14:25.600 --> 00:14:29.509
Trojan in our own airspace.
00:14:29.519 --> 00:14:32.870
In Empire Strikes Back, the Pro Droid
00:14:32.880 --> 00:14:35.910
transmits the location of the shield
00:14:35.920 --> 00:14:40.550
generator before it self-destructs.
00:14:40.560 --> 00:14:43.990
These drones have been doing the exact
00:14:44.000 --> 00:14:46.389
same thing. Technically, here is what
00:14:46.399 --> 00:14:49.829
happens. The drone collects telemetry
00:14:49.839 --> 00:14:54.389
data, GPS coordinates, flight paths,
00:14:54.399 --> 00:14:58.550
video footage. It stores this data. Then
00:14:58.560 --> 00:15:01.189
when it connects to the internet for a
00:15:01.199 --> 00:15:04.710
firmware update or to sync your flight
00:15:04.720 --> 00:15:08.550
logs to the cloud, it sends a packet to
00:15:08.560 --> 00:15:11.269
a server in Shenzen.
00:15:11.279 --> 00:15:14.949
That packet contains the highresolution
00:15:14.959 --> 00:15:19.350
3D map of the critical substation you
00:15:19.360 --> 00:15:21.269
just inspected.
00:15:21.279 --> 00:15:24.150
It contains the structural weak points
00:15:24.160 --> 00:15:28.310
of the dam you just surveyed.
00:15:28.320 --> 00:15:31.750
It contains the thermal exhaust port of
00:15:31.760 --> 00:15:33.990
the power plant.
00:15:34.000 --> 00:15:37.189
This is the failure of data
00:15:37.199 --> 00:15:39.910
sovereignity. You can pass all the laws
00:15:39.920 --> 00:15:43.990
you want about where data is stored. You
00:15:44.000 --> 00:15:47.750
can write GDPR policies until your hand
00:15:47.760 --> 00:15:49.590
cramps.
00:15:49.600 --> 00:15:53.110
But if the device itself, the physical
00:15:53.120 --> 00:15:55.990
hardware collecting the data is
00:15:56.000 --> 00:16:00.389
hardcoded at the factory to phone home,
00:16:00.399 --> 00:16:03.910
your laws are meaningless.
00:16:03.920 --> 00:16:08.150
You cannot patch a spy. The border isn't
00:16:08.160 --> 00:16:11.110
a line on a map anymore. The border is a
00:16:11.120 -->
00:16:14.310
firmware on the drone hovering over the
00:16:14.320 --> 00:16:16.949
Golden Gate Bridge. The border is a
00:16:16.959 --> 00:16:19.910
skater system controlling the heater in
00:16:19.920 --> 00:16:22.870
a Romanian apartment block.
00:16:22.880 --> 00:16:27.030
And right now the shield generator is
00:16:27.040 --> 00:16:30.949
down. Let's move to the code. Decoding
00:16:30.959 --> 00:16:35.110
the bites. If the physical world is
00:16:35.120 --> 00:16:39.110
under siege, the digital foundation is
00:16:39.120 --> 00:16:43.829
rotting. I want to talk about insection.
00:16:43.839 --> 00:16:47.030
In the movie, the architect builds the
00:16:47.040 --> 00:16:50.150
dream. But if the architect leaves a
00:16:50.160 --> 00:16:53.829
flaw in the design, the dreamer or an
00:16:53.839 --> 00:16:57.110
intruder can manipulate the physics of
00:16:57.120 --> 00:17:01.829
the world. They can fold cities in half.
00:17:01.839 --> 00:17:05.350
They can turn gravity off. They can
00:17:05.360 --> 00:17:08.549
reshape the reality of the dream to suit
00:17:08.559 --> 00:17:10.390
their needs.
00:17:10.400 --> 00:17:13.510
We built the modern web on a framework
00:17:13.520 --> 00:17:15.829
called React.
00:17:15.839 --> 00:17:19.429
It is fast. It is modular. It is
00:17:19.439 --> 00:17:22.630
beautiful. It powers everything from
00:17:22.640 --> 00:17:26.069
your banking app to your social media
00:17:26.079 --> 00:17:27.590
feed.
00:17:27.600 --> 00:17:30.310
But we built it with a flaw in the
00:17:30.320 --> 00:17:31.909
physics.
00:17:31.919 --> 00:17:37.270
Meet React to Shell. CVE
00:17:37.280 --> 00:17:38.950
2025
00:17:38.960 --> 00:17:41.830
555182
00:17:41.840 --> 00:17:47.270
a perfect 10.0 on the CVSS scale.
00:17:47.280 --> 00:17:50.230
For the non-technical audience, the
00:17:50.240 --> 00:17:53.190
common vulnerability scoring system,
00:17:53.200 --> 00:17:59.669
CVSS, goes from 0 to 10. A 10.0 isn't
00:17:59.679 --> 00:18:03.510
just a bad score. It is a fatality. It
00:18:03.520 --> 00:18:05.669
is the blue screen of death for your
00:18:05.679 --> 00:18:09.110
entire enterprise security posture. It
00:18:09.120 --> 00:18:13.190
affects Nex.js and React server
00:18:13.200 --> 00:18:14.870
components.
00:18:14.880 --> 00:18:18.549
This isn't some old legacy software from
00:18:18.559 --> 00:18:23.510
1995 like Cobalt. This is the stuff we
00:18:23.520 --> 00:18:27.029
built the new internet with. The
00:18:27.039 --> 00:18:29.510
vulnerability is called unsafe
00:18:29.520 --> 00:18:31.510
deserialization.
00:18:31.520 --> 00:18:36.390
That's a fancy word for blind trust. Let
00:18:36.400 --> 00:18:39.510
me explain this mechanism because it is
00:18:39.520 --> 00:18:43.669
vital you understand how fragile the web
00:18:43.679 --> 00:18:48.150
really is. Why do we do this? Why do we
00:18:48.160 --> 00:18:50.630
use serialization?
00:18:50.640 --> 00:18:54.150
Because it's efficient. We want our apps
00:18:54.160 --> 00:18:57.350
to be fast. We want seamless data
00:18:57.360 --> 00:18:59.909
transfer between the client and the
00:18:59.919 --> 00:19:03.110
server. We traded security for
00:19:03.120 --> 00:19:06.150
milliseconds of load time. When you send
00:19:06.160 --> 00:19:09.190
data to an application, let's say you
00:19:09.200 --> 00:19:13.270
upload a user profile, that data has to
00:19:13.280 --> 00:19:15.750
be packaged up to travel across the
00:19:15.760 --> 00:19:19.430
internet. We call this serialization.
00:19:19.440 --> 00:19:22.390
It turns a complex object into a stream
00:19:22.400 --> 00:19:25.909
of bytes. When it reaches the server,
00:19:25.919 --> 00:19:29.750
the application has to unpack it. it has
00:19:29.760 --> 00:19:33.110
to turn those bytes back into an object
00:19:33.120 --> 00:19:37.830
it can use. This is deserialization.
00:19:37.840 --> 00:19:41.350
In a secure world, the application
00:19:41.360 --> 00:19:45.029
checks the data before it unpacks it. It
00:19:45.039 --> 00:19:50.070
asks, "Is this just text? Is this just a
00:19:50.080 --> 00:19:53.750
number? Is this safe?" In a React to
00:19:53.760 --> 00:19:56.390
shell world, the application doesn't
00:19:56.400 --> 00:19:59.029
ask, it trusts.
00:19:59.039 --> 00:20:01.830
If you hand it a serialized object that
00:20:01.840 --> 00:20:05.110
contains a command to open a reverse
00:20:05.120 --> 00:20:07.909
shell instead of a user profile, the
00:20:07.919 --> 00:20:11.270
application unpacks it and executes the
00:20:11.280 --> 00:20:14.630
command. It is like handing a bank
00:20:14.640 --> 00:20:18.390
teller a sealed envelope. The teller is
00:20:18.400 --> 00:20:21.350
programmed to open the envelope and
00:20:21.360 --> 00:20:23.750
immediately do whatever is written on
00:20:23.760 --> 00:20:28.070
the note inside. China Nexus groups,
00:20:28.080 --> 00:20:31.430
specifically Earth Lamia and Jackpot
00:20:31.440 --> 00:20:36.149
Panda, weaponized this within ours. They
00:20:36.159 --> 00:20:39.110
aren't waiting for you to patch. They
00:20:39.120 --> 00:20:42.149
are scanning the internet right now.
00:20:42.159 --> 00:20:45.350
They are installing crypto miners. They
00:20:45.360 --> 00:20:48.710
are harvesting cloud credentials.
00:20:48.720 --> 00:20:52.950
We built a glass house for our data. And
00:20:52.960 --> 00:20:56.710
we just handed the enemy a sledgehammer.
00:20:56.720 --> 00:21:01.430
But wait, it gets worse because even if
00:21:01.440 --> 00:21:04.230
your software is secure,
00:21:04.240 --> 00:21:07.909
even if you patch React, even if your
00:21:07.919 --> 00:21:10.710
application layer is a fortress,
00:21:10.720 --> 00:21:14.710
your hardware is compromised.
00:21:14.720 --> 00:21:18.149
Let us talk about god mode.
00:21:18.159 --> 00:21:22.549
In video games, god mode means you can't
00:21:22.559 --> 00:21:27.190
die. You can walk through walls and you
00:21:27.200 --> 00:21:30.070
can reshape the level in the data
00:21:30.080
--> 00:21:33.110
center. God mode is the management
00:21:33.120 --> 00:21:37.430
plane. Cesar just wanders about HP one
00:21:37.440 --> 00:21:43.510
view. CVE 202537164.
00:21:43.520 --> 00:21:45.669
Another 10.0.
00:21:45.679 --> 00:21:47.990
One view is a software that manages the
00:21:48.000 --> 00:21:51.270
physical servers. It sits below the
00:21:51.280 --> 00:21:53.750
operating system. It tells the metal
00:21:53.760 --> 00:21:57.029
what to do. To understand this, we have
00:21:57.039 --> 00:22:00.549
to talk about rings of security.
00:22:00.559 --> 00:22:04.070
Ring three is your applications.
00:22:04.080 --> 00:22:08.230
Chrome, Word, React.
00:22:08.240 --> 00:22:11.190
Ring zero is your operating system
00:22:11.200 --> 00:22:16.630
kernel. Windows, Linux. This is where we
00:22:16.640 --> 00:22:19.990
think the power lies. But there is a
00:22:20.000 --> 00:22:23.830
ring minus one. This is the firmware,
00:22:23.840 --> 00:22:27.669
the hypervisor, the management plane.
00:22:27.679 --> 00:22:32.549
HP1 view lives in ring minus one. Think
00:22:32.559 --> 00:22:35.190
about your security stack. You have
00:22:35.200 --> 00:22:38.470
antivirus. You have EDR, endpoint
00:22:38.480 --> 00:22:40.789
detection and response. You have
00:22:40.799 --> 00:22:42.470
firewalls.
00:22:42.480 --> 00:22:45.590
Where do those tools live? They live in
00:22:45.600 --> 00:22:49.510
ring zero or ring three. They live in
00:22:49.520 --> 00:22:51.669
the operating system.
00:22:51.679 --> 00:22:55.830
If you hack the website, React, you own
00:22:55.840 --> 00:22:58.390
the app. If you hack the management
00:22:58.400 --> 00:23:02.549
plane, one view, you own the physics of
00:23:02.559 --> 00:23:04.549
the data center.
00:23:04.559 --> 00:23:08.310
You can wipe the storage arrays. You can
00:23:08.320 --> 00:23:10.870
reimage the servers.
00:23:10.880 --> 00:23:13.750
You can turn off the cooling fans and
00:23:13.760 --> 00:23:16.310
melt the processors.
00:23:16.320 --> 00:23:19.669
And here is a nightmare scenario.
00:23:19.679 --> 00:23:21.350
Persistence.
00:23:21.360 --> 00:23:24.310
If I hack your Windows OS,
00:23:24.320 --> 00:23:26.710
you can just wipe the hard drive and
00:23:26.720 --> 00:23:30.870
reinstall Windows. The virus is gone.
00:23:30.880 --> 00:23:34.789
But if I hack the management plane, I am
00:23:34.799 --> 00:23:37.750
not on the hard drive. I am on the
00:23:37.760 --> 00:23:41.590
motherboard. I am in the silicon. You
00:23:41.600 --> 00:23:45.270
can wipe the hard drive. You can buy a
00:23:45.280 --> 00:23:48.310
new hard drive. You can reinstall
00:23:48.320 --> 00:23:52.470
Windows a thousand times. But the moment
00:23:52.480 --> 00:23:56.390
you turn that machine back on, I am
00:23:56.400 --> 00:23:57.909
still there.
00:23:57.919 --> 00:24:02.230
I am the ghost in the machine's soul.
00:24:02.240 --> 00:24:06.149
And the scariest part, your fancy edr
00:24:06.159 --> 00:24:10.149
tools. They can't see this. They are
00:24:10.159 --> 00:24:13.350
looking out the window for burglars
00:24:13.360 --> 00:24:16.149
while the monster is coming up through
00:24:16.159 --> 00:24:18.230
the floorboards.
00:24:18.240 --> 00:24:21.750
This is the Matrix analogy. Neo isn't
00:24:21.760 --> 00:24:24.070
fighting Agent Smith inside the
00:24:24.080 --> 00:24:26.310
simulation anymore.
00:24:26.320 --> 00:24:29.990
Neo has gone to the machine city. He is
00:24:30.000 --> 00:24:33.029
talking to the source. He is rewriting
00:24:33.039 --> 00:24:36.549
the code of the matrix itself.
00:24:36.559 --> 00:24:41.190
When an attacker exploits HP1 view, they
00:24:41.200 --> 00:24:43.909
are at the source. They can delete the
00:24:43.919 --> 00:24:46.630
logs that would prove they were ever
00:24:46.640 --> 00:24:49.990
there. They can turn off the defenses
00:24:50.000 --> 00:24:53.110
with a single command.
00:24:53.120 --> 00:24:56.950
When you have a 10.0 0 in the app layer
00:24:56.960 --> 00:25:02.950
react and a 10.0 in the metal layer HP.
00:25:02.960 --> 00:25:05.830
You don't have a security posture.
00:25:05.840 --> 00:25:09.990
You have a sandwich and you are the
00:25:10.000 --> 00:25:11.750
meat.
00:25:11.760 --> 00:25:15.350
The attackers are eating us from the top
00:25:15.360 --> 00:25:19.830
down and the bottom up.
00:25:19.840 --> 00:25:23.510
Which brings us to the bill.
00:25:23.520 --> 00:25:26.549
Dissecting the breach.
00:25:26.559 --> 00:25:30.630
We talk about risk in abstract terms. We
00:25:30.640 --> 00:25:34.470
talk about reputation damage. We talk
00:25:34.480 --> 00:25:37.830
about regulatory fines.
00:25:37.840 --> 00:25:41.110
Let's talk about solvency.
00:25:41.120 --> 00:25:45.510
Let's talk about Jaguar Land Rover. On
00:25:45.520 --> 00:25:49.269
January 5th, JLR released their Q3
00:25:49.279 --> 00:25:51.269
financial results.
00:25:51.279 --> 00:25:53.590
Was a bloodbath.
00:25:53.600 --> 00:25:56.390
Wholesale volumes, the number of cars
00:25:56.400 --> 00:26:00.310
they actually sold to dealers dropped by
00:26:00.320 --> 00:26:03.590
43.3%.
00:26:03.600 --> 00:26:09.669
Almost half of their business gone. Why?
00:26:09.679 --> 00:26:12.870
Not because people stopped wanting Range
00:26:12.880 --> 00:26:14.549
Rovers,
00:26:14.559 --> 00:26:17.590
not because of a recession,
00:26:17.600 --> 00:26:21.110
not because of interest rates, but
00:26:21.120 --> 00:26:23.990
because of a cyber attack back in
00:26:24.000 --> 00:26:27.269
September that halted production at
00:26:27.279 --> 00:26:29.669
their key plants.
00:26:29.679 --> 00:26:33.430
This is the lagging indicator. In
00:26:33.440 --> 00:26:36.789
Moneyball, they talk about statistics
00:26:36.799 --> 00:26:39.430
that tell the truth.
00:26:39.440 --> 00:26:43.269
He gets on base. This is the truth of
00:26:43.279 --> 00:26:46.789
cyber war. It's not just about stolen
00:26:46.799 --> 00:26:51.350
files. It's about cars not built. We
00:26:51.360 -->
00:26:54.950
live in a just in time economy. We were
00:26:54.960 --> 00:26:57.110
shipped at the altar of lean
00:26:57.120 --> 00:27:01.269
manufacturing for 40 years. We removed
00:27:01.279 --> 00:27:03.029
the warehouses.
00:27:03.039 --> 00:27:06.230
We removed the buffer stock. We treated
00:27:06.240 --> 00:27:10.230
inventory as waste to be eliminated.
00:27:10.240 --> 00:27:14.710
Well, in a war, inventory isn't waste.
00:27:14.720 --> 00:27:19.350
Inventory is a bunker. When JLR systems
00:27:19.360 --> 00:27:21.750
went down, they didn't have a pile of
00:27:21.760 --> 00:27:24.230
parts to keep building cars. Just in
00:27:24.240 --> 00:27:26.710
time parts stopped arriving. The
00:27:26.720 --> 00:27:30.390
assembly line stopped moving. We built a
00:27:30.400 --> 00:27:33.110
supply chain that was optimized for
00:27:33.120 --> 00:27:37.190
profit but fragile for disruption.
00:27:37.200 --> 00:27:40.950
If you hack the factory floor, you stop
00:27:40.960 --> 00:27:43.350
the revenue engine.
00:27:43.360 --> 00:27:45.990
Think about the ripple effect here. It
00:27:46.000 --> 00:27:49.510
is not just JLR losing money. It is the
00:27:49.520 --> 00:27:52.230
tire supplier who has thousands of tires
00:27:52.240 --> 00:27:55.909
sitting on a dock with nowhere to go. It
00:27:55.919 --> 00:27:58.230
is the glass manufacturer.
00:27:58.240 --> 00:28:01.350
It is the dealership in Ohio with an
00:28:01.360 --> 00:28:04.789
empty lot and salespeople who can't feed
00:28:04.799 --> 00:28:07.750
their families because they work on
00:28:07.760 --> 00:28:11.029
commission. This attack removed billions
00:28:11.039 --> 00:28:14.470
of dollars from the UK GDP.
00:28:14.480 --> 00:28:18.630
Cyber security is no longer an IT issue.
00:28:18.640 --> 00:28:21.669
It is a solveny issue.
00:28:21.679 --> 00:28:25.830
If you are a CEO listening to this, your
00:28:25.840 --> 00:28:29.669
CISO isn't protecting your email. He is
00:28:29.679 --> 00:28:33.029
protecting your stock price. He is
00:28:33.039 --> 00:28:35.830
protecting your ability to exist as a
00:28:35.840 --> 00:28:39.510
company. The market punished JLR months
00:28:39.520 --> 00:28:42.149
after the attack. The poison is slow
00:28:42.159 --> 00:28:45.750
acting but sometimes the response to a
00:28:45.760 --> 00:28:49.430
breach is even more insulting than the
00:28:49.440 --> 00:28:52.950
breach itself. Let us talk about Kong
00:28:52.960 --> 00:28:56.630
the South Korean e-commerce giant the
00:28:56.640 --> 00:29:00.070
Amazon of Korea. They suffered a massive
00:29:00.080 --> 00:29:03.110
data breach. 33.7
00:29:03.120 --> 00:29:05.110
million users
00:29:05.120 --> 00:29:09.190
names, contact info, transaction history
00:29:09.200 --> 00:29:13.590
exposed. And how did it happen? Was it a
00:29:13.600 --> 00:29:16.710
sophisticated nation state attack? Was
00:29:16.720 --> 00:29:21.350
it a zero day in the kernel? No, it was
00:29:21.360 --> 00:29:23.590
a rogue employee,
00:29:23.600 --> 00:29:27.269
a developer who smashed his laptop and
00:29:27.279 --> 00:29:29.110
threw it in a river to hide the
00:29:29.120 --> 00:29:33.110
evidence. Insider threat, the oldest
00:29:33.120 --> 00:29:35.990
vulnerability in the book.
00:29:36.000 --> 00:29:39.750
High-tech defenses cannot stop low tech
00:29:39.760 --> 00:29:41.269
rage.
00:29:41.279 --> 00:29:44.310
But that is not the red pill here. The
00:29:44.320 --> 00:29:47.590
red pill is the restitution.
00:29:47.600 --> 00:29:51.669
Kong announced a plan to distribute
00:29:51.679 --> 00:29:56.070
$1.17 billion in compensation.
00:29:56.080 --> 00:29:59.190
Sounds generous, right? Here's the
00:29:59.200 --> 00:30:03.190
catch. They are paying it in vouchers.
00:30:03.200 --> 00:30:06.549
Store credit valid only at coupon. They
00:30:06.559 --> 00:30:08.789
are paying for their failure with their
00:30:08.799 --> 00:30:11.510
own funny money.
00:30:11.520 --> 00:30:14.070
I want you to think about the episode of
00:30:14.080 --> 00:30:19.029
Black Mirror called 15 million merits.
00:30:19.039 --> 00:30:22.310
You are trapped in the system. You work
00:30:22.320 --> 00:30:25.590
for the system and when the system fails
00:30:25.600 --> 00:30:30.070
you, they pay you in merits to keep you
00:30:30.080 --> 00:30:32.870
cycling on the bike. This is the company
00:30:32.880 --> 00:30:36.310
store model of cyber security.
00:30:36.320 --> 00:30:40.630
They lost your most private data, your
00:30:40.640 --> 00:30:43.350
identity, your shopping habits, your
00:30:43.360 --> 00:30:46.470
digital life. and their apology is to
00:30:46.480 --> 00:30:50.549
force you to shop more at the very store
00:30:50.559 --> 00:30:54.070
that betrayed you. The valuation works
00:30:54.080 --> 00:30:57.990
out to about $35 per person.
00:30:58.000 --> 00:31:00.549
That is the price of your digital
00:31:00.559 --> 00:31:03.669
identity in 2026.
00:31:03.679 --> 00:31:07.350
$35 in store credit.
00:31:07.360 --> 00:31:12.070
It is an insult disguised as an apology.
00:31:12.080 --> 00:31:15.669
This sets a terrifying precedent. If
00:31:15.679 --> 00:31:18.630
companies can fix a breach by printing
00:31:18.640 --> 00:31:21.190
their own currency, where is the
00:31:21.200 --> 00:31:22.950
deterrent?
00:31:22.960 --> 00:31:26.630
If a bank gets hacked, can they pay you
00:31:26.640 --> 00:31:30.310
back in ATM fee wavers?
00:31:30.320 --> 00:31:34.070
If a hospital leaks your records, can
00:31:34.080 --> 00:31:38.149
they pay you in free Tylenol?
00:31:38.159 --> 00:31:42.470
This is the commoditization of privacy.
00:31:42.480 --> 00:31:45.269
They have turned your data into a
00:31:45.279 --> 00:31:49.110
liability and your compensation into a
00:31:49.120 --> 00:31:51.750
marketing campaign.
00:31:51.760 --> 00:31:56.070
JLR shows us the cost of the stock.
00:31:56.080 --> 00:32:00.630
Coup shows us cost of the soul.
00:32:00.640 --> 00:32:04.630
And in both cases, the price is too
00:32:04.640 --> 00:32:09.269
high. So what do we do? We are being
00:32:09.279 --> 00:32:10.950
squeezed
00:32:10.960 --> 00:32:14.310
from the outside by the calendar kill
00:32:14.320 --> 00:32:17.350
chain. Adversaries weaponizing the
00:32:17.360 --> 00:32:20.870
winter and the holidays. Proving that
00:32:20.880 --> 00:32:23.830
our comfort is their weapon.
00:32:23.840 --> 00:32:26.950
From above, the hardware Trojans in our
00:32:26.960 --> 00:32:29.830
drone fleets, proving that cheap
00:32:29.840 --> 00:32:33.909
hardware has a hidden geopolitical tax.
00:32:33.919 --> 00:32:37.029
From the inside, by the god mode,
00:32:37.039 --> 00:32:39.990
vulnerabilities in our own code, and the
00:32:40.000 --> 00:32:43.350
insider threats throwing laptops into
00:32:43.360 --> 00:32:45.110
reverse.
00:32:45.120 --> 00:32:49.990
The message of episode 4 is simple.
00:32:50.000 --> 00:32:53.509
The foundation is not safe.
00:32:53.519 --> 00:32:57.110
You cannot trust the calendar. Just
00:32:57.120 --> 00:32:59.990
because it's Christmas doesn't mean you
00:33:00.000 --> 00:33:05.190
are safe. It means you are a target.
00:33:05.200 --> 00:33:08.950
You cannot trust the code. Just because
00:33:08.960 --> 00:33:13.590
it's React doesn't mean it is secure.
00:33:13.600 --> 00:33:16.870
You cannot trust the apology.
00:33:16.880 --> 00:33:19.830
Just because they offer you a voucher
00:33:19.840 --> 00:33:24.549
doesn't mean they value your privacy.
00:33:24.559 --> 00:33:27.990
We need to stop assuming that default
00:33:28.000 --> 00:33:30.789
means safe.
00:33:30.799 --> 00:33:34.310
Default is dangerous.
00:33:34.320 --> 00:33:37.110
If you are a defender,
00:33:37.120 --> 00:33:41.110
assume the parasite is already in the
00:33:41.120 --> 00:33:42.630
basement.
00:33:42.640 --> 00:33:45.669
Go hunt for them. Don't wait for the
00:33:45.679 --> 00:33:50.230
alert. The alert is already too late. If
00:33:50.240 --> 00:33:54.070
you are a leader, look at JLR. Ask
00:33:54.080 --> 00:33:57.269
yourself, how many days can we survive
00:33:57.279 --> 00:33:59.269
without revenue?
00:33:59.279 --> 00:34:03.269
The winter is here. The digital cold is
00:34:03.279 --> 00:34:07.190
setting in. Put on a coat. Patch your
00:34:07.200 --> 00:34:08.869
servers.
00:34:08.879 --> 00:34:11.109
And for God's sake, don't take the
00:34:11.119 --> 00:34:13.030
voucher.
00:34:13.040 --> 00:34:15.589
I am Barat Mataparti.
00:34:15.599 --> 00:34:20.470
This is by bites, borders and breaches.
00:34:20.480 --> 00:34:21.750
Stay paranoid.
00:34:21.760 --> 00:34:24.629
>> THIS IS BITES, BORDERS AND BREACHES.
00:34:24.639 --> 00:34:27.909
>> THE SIGNAL is loud. The lesson is
00:34:27.919 --> 00:34:30.310
security. Stand in the guard. The truth
00:34:30.320 --> 00:34:34.159
is heavy. The truth is hard.