WEBVTT - What was Stuxnet? Part One

0:00:03.880 --> 0:00:06.880
<v Speaker 1>Get in touch with technology with tech Stuff from how

0:00:06.960 --> 0:00:14.040
<v Speaker 1>stuff works dot com. Hey there, and welcome to tech Stuff.

0:00:14.080 --> 0:00:17.640
<v Speaker 1>I'm your host, Jonathan Strickland. I'm an executive producer here

0:00:17.640 --> 0:00:21.520
<v Speaker 1>at how Stuff Works. And yeah, I still kind of

0:00:21.600 --> 0:00:23.640
<v Speaker 1>have a cold. You can kind of hear it. It's

0:00:23.680 --> 0:00:25.159
<v Speaker 1>not as bad as it was last week when I

0:00:25.160 --> 0:00:28.640
<v Speaker 1>was recording those earlier episodes though, So that's something. Uh,

0:00:28.800 --> 0:00:31.720
<v Speaker 1>since I have a cold, you know, I thought my

0:00:31.800 --> 0:00:33.720
<v Speaker 1>brain got on this little topic. It's sort of this

0:00:33.800 --> 0:00:38.440
<v Speaker 1>free association thing technology colds viruses. How about I talk

0:00:38.479 --> 0:00:42.760
<v Speaker 1>about a famous virus. So we're going to really dive

0:00:42.840 --> 0:00:48.160
<v Speaker 1>in to the story behind stucks net, a famous piece

0:00:48.280 --> 0:00:52.960
<v Speaker 1>of malware that made headlines in and I've talked about

0:00:52.960 --> 0:00:55.320
<v Speaker 1>it before on this show. In fact, Chris Palette and

0:00:55.360 --> 0:00:58.440
<v Speaker 1>I did an episode about stucks net several years ago,

0:00:58.760 --> 0:01:03.000
<v Speaker 1>but at the time not as much information was available

0:01:03.040 --> 0:01:06.720
<v Speaker 1>about what was going on. Tech Stuff technically launched two

0:01:06.840 --> 0:01:10.640
<v Speaker 1>years before stocks Net made headlines. So this is actually

0:01:10.640 --> 0:01:13.440
<v Speaker 1>an opportunity for me to look back at something that

0:01:13.560 --> 0:01:16.280
<v Speaker 1>developed over the course of the history of this show

0:01:17.000 --> 0:01:21.039
<v Speaker 1>and learn more about where it came from, what's purpose was,

0:01:21.720 --> 0:01:26.559
<v Speaker 1>and how that whole story unfolded. Before I really dive

0:01:26.680 --> 0:01:30.840
<v Speaker 1>into the story, I want to mention one of the

0:01:30.920 --> 0:01:36.039
<v Speaker 1>sources I used when I was researching these two episodes. Uh,

0:01:36.080 --> 0:01:40.080
<v Speaker 1>this would be a book titled Countdown to Zero Day,

0:01:40.200 --> 0:01:43.279
<v Speaker 1>stucks Net and the Launch of the World's First Digital Weapon.

0:01:43.800 --> 0:01:46.920
<v Speaker 1>The book goes into great detail regarding the story of

0:01:46.920 --> 0:01:52.160
<v Speaker 1>stocks Net. It also gives wonderful background information on the

0:01:52.280 --> 0:01:59.400
<v Speaker 1>key figures of cryptography researchers, cybersecurity researchers, all these people

0:01:59.440 --> 0:02:03.600
<v Speaker 1>who were very much instrumental in discovering and uncovering stuck

0:02:03.680 --> 0:02:06.240
<v Speaker 1>s net and figuring out what it did and and

0:02:06.280 --> 0:02:10.079
<v Speaker 1>who was probably behind it since that was never something

0:02:10.080 --> 0:02:12.240
<v Speaker 1>that was officially acknowledged, but come on, we know who

0:02:12.320 --> 0:02:14.920
<v Speaker 1>it actually was. I'll talk about that in these episodes.

0:02:15.320 --> 0:02:18.040
<v Speaker 1>That's a great book. If you want more information about

0:02:18.120 --> 0:02:21.800
<v Speaker 1>stucks Net after this episode, go check that out, count

0:02:21.800 --> 0:02:24.360
<v Speaker 1>Down to Zero Day, stucks Net and the Launch of

0:02:24.360 --> 0:02:28.400
<v Speaker 1>the World's First Digital Weapon. It goes into way more

0:02:28.480 --> 0:02:32.160
<v Speaker 1>detail than I'm going to cover in these episodes. Now,

0:02:32.840 --> 0:02:35.880
<v Speaker 1>these episodes are also going to contain a lot of

0:02:36.000 --> 0:02:41.280
<v Speaker 1>history and politics in them because stucks net, unlike many

0:02:41.360 --> 0:02:46.160
<v Speaker 1>other examples of malware was not intended to be a

0:02:46.440 --> 0:02:51.600
<v Speaker 1>type of uh computer virus to create monetary gain for

0:02:51.639 --> 0:02:56.920
<v Speaker 1>the people who designed it, or even just make people irritated.

0:02:57.120 --> 0:02:59.880
<v Speaker 1>It wasn't that kind of malware. You may have a

0:03:00.040 --> 0:03:03.200
<v Speaker 1>counter and malware that was meant to try and extort

0:03:03.240 --> 0:03:07.480
<v Speaker 1>money from someone where it locks down a computer and

0:03:07.600 --> 0:03:10.360
<v Speaker 1>the only way to get access, at least according to

0:03:10.600 --> 0:03:15.160
<v Speaker 1>the messengersy receive, is to pay a ransom to the hackers.

0:03:15.240 --> 0:03:18.680
<v Speaker 1>We call that ransomware. Stuck's Net was not that type

0:03:18.680 --> 0:03:22.720
<v Speaker 1>of malware. Nor was it just some sort of capricious

0:03:22.840 --> 0:03:26.840
<v Speaker 1>code that someone created in order to turn computer hard

0:03:26.960 --> 0:03:31.280
<v Speaker 1>drives into giant concrete blocks. It was neither of those things.

0:03:31.280 --> 0:03:37.040
<v Speaker 1>It had a very specific intent, and it was very

0:03:37.120 --> 0:03:40.760
<v Speaker 1>much a at least all signs at least pointed to

0:03:40.840 --> 0:03:44.440
<v Speaker 1>it being very much a state sponsored piece of software,

0:03:44.480 --> 0:03:49.640
<v Speaker 1>meaning that some government agency or agencies was behind the

0:03:49.680 --> 0:03:53.240
<v Speaker 1>development of this. So it sets it apart from a

0:03:53.240 --> 0:03:56.760
<v Speaker 1>lot of other versions of malware. And in order to

0:03:56.840 --> 0:03:59.040
<v Speaker 1>understand it, I think it's good to begin with a

0:03:59.120 --> 0:04:04.320
<v Speaker 1>quick history lesson of Iran's nuclear program, because that was

0:04:04.480 --> 0:04:09.680
<v Speaker 1>the ultimate target of stocks net back in the nineteen fifties. Iran,

0:04:09.920 --> 0:04:14.680
<v Speaker 1>under the leadership of shaw Mohammad Reza PALAVII, had received

0:04:14.680 --> 0:04:18.400
<v Speaker 1>the nod from the world community to pursue a nuclear

0:04:18.480 --> 0:04:22.320
<v Speaker 1>power program. At that same time, nuclear powers like the

0:04:22.400 --> 0:04:25.839
<v Speaker 1>United States, we're trying to discourage other nations from developing

0:04:25.920 --> 0:04:29.560
<v Speaker 1>nuclear weapons. So they were essentially saying, hey, nuclear power,

0:04:29.920 --> 0:04:34.560
<v Speaker 1>tots cool nuclear weapons, Let's not make this worse because

0:04:34.680 --> 0:04:40.159
<v Speaker 1>nuclear proliferation was becoming a big fear among various powers

0:04:40.160 --> 0:04:42.480
<v Speaker 1>in the world and of course populations in the world.

0:04:43.040 --> 0:04:46.000
<v Speaker 1>So it was sort of an Atoms for Peace kind

0:04:46.040 --> 0:04:49.359
<v Speaker 1>of initiative, saying, let's go and develop nuclear power for

0:04:49.400 --> 0:04:52.719
<v Speaker 1>a country's that's great. That way you can generate electricity,

0:04:52.760 --> 0:04:57.440
<v Speaker 1>but let's stay away from building the bombs. Iran's program

0:04:57.520 --> 0:05:00.559
<v Speaker 1>was launched with the understanding that the country was only

0:05:00.600 --> 0:05:05.520
<v Speaker 1>going to build these power plants, not weaponry, although all

0:05:05.560 --> 0:05:09.080
<v Speaker 1>indications showed that the long term plan for Iran was

0:05:09.120 --> 0:05:13.360
<v Speaker 1>in fact to develop nuclear weapons at some point. As

0:05:13.400 --> 0:05:16.400
<v Speaker 1>part of this early agreement, the United States would sell

0:05:16.520 --> 0:05:20.040
<v Speaker 1>to Iran the enriched uranium its power plants would need

0:05:20.080 --> 0:05:22.960
<v Speaker 1>as fuel, so Iran wouldn't need to create its own

0:05:23.080 --> 0:05:27.679
<v Speaker 1>uranium enrichment facilities. It would just purchase enriched uranium ready

0:05:27.760 --> 0:05:31.800
<v Speaker 1>to go from the United States. And in fact, the US, Germany,

0:05:31.880 --> 0:05:37.400
<v Speaker 1>and France were all totally supportive of Iran's efforts, perhaps

0:05:37.920 --> 0:05:41.760
<v Speaker 1>because those countries also stood to benefit from it. They

0:05:41.760 --> 0:05:44.520
<v Speaker 1>were all going to make a boatload of cash by

0:05:44.520 --> 0:05:48.279
<v Speaker 1>selling equipment and fuel to Iran, so there was a

0:05:48.360 --> 0:05:54.400
<v Speaker 1>financial incentive to support Iran's efforts to create nuclear power plants.

0:05:54.440 --> 0:05:57.080
<v Speaker 1>All of this was despite the fact that the tools

0:05:57.200 --> 0:06:01.120
<v Speaker 1>used to create nuclear power plants could receivably be put

0:06:01.160 --> 0:06:04.080
<v Speaker 1>to use to build nuclear weapons. So you could have

0:06:04.160 --> 0:06:07.080
<v Speaker 1>someone say, hey, I just need this technology because I

0:06:07.080 --> 0:06:09.800
<v Speaker 1>want to make a power plant, but in reality they

0:06:09.880 --> 0:06:13.640
<v Speaker 1>might be using that technology to make boom booms. So

0:06:14.240 --> 0:06:16.960
<v Speaker 1>the thing that the U United States said that kind

0:06:16.960 --> 0:06:22.360
<v Speaker 1>of justified their choice to support this program was, Hey,

0:06:22.520 --> 0:06:26.640
<v Speaker 1>the Shah, he's awesome. We get along so well, we're

0:06:26.680 --> 0:06:32.040
<v Speaker 1>like besties. And so there's no way that Iran, even

0:06:32.040 --> 0:06:34.520
<v Speaker 1>if they did develop nuclear weapons, would be a threat

0:06:34.600 --> 0:06:38.000
<v Speaker 1>to US, their their allies. So let's go ahead and

0:06:38.040 --> 0:06:40.360
<v Speaker 1>go all in. Let's go ahead and make some money.

0:06:40.400 --> 0:06:44.640
<v Speaker 1>Come on, capitalism, woo. It's not like Iran will ever

0:06:44.680 --> 0:06:48.400
<v Speaker 1>have a problem with the United States. And then nineteen

0:06:48.480 --> 0:06:52.880
<v Speaker 1>seventy nine happened. In nineteen seventy nine, the Ayatollah Ruala

0:06:53.000 --> 0:06:57.120
<v Speaker 1>Kamaney overthrew the shop. Now Kamany did not share the

0:06:57.160 --> 0:07:01.200
<v Speaker 1>Shah's opinion of the United States, and suddenly the U

0:07:01.440 --> 0:07:06.400
<v Speaker 1>S was tugging at its collar and saying yikes. So

0:07:06.520 --> 0:07:10.320
<v Speaker 1>Germany in the US withdrew their support for Iran's nuclear

0:07:10.320 --> 0:07:14.640
<v Speaker 1>program and the Komani Aetola. Komani was not terribly interested

0:07:14.680 --> 0:07:19.160
<v Speaker 1>in pursuing a nuclear power program either, so the power

0:07:19.200 --> 0:07:21.760
<v Speaker 1>plants were pretty much abandoned for a few years. They

0:07:21.800 --> 0:07:26.560
<v Speaker 1>were also the frequent target of bombing raids during various

0:07:27.000 --> 0:07:30.320
<v Speaker 1>conflicts that Iran got into over the course of the eighties.

0:07:30.680 --> 0:07:34.680
<v Speaker 1>Now that Aatola would eventually renew the nuclear program. In

0:07:34.720 --> 0:07:38.560
<v Speaker 1>the nineteen eighties, after rumors spread that Iraq was developing

0:07:38.600 --> 0:07:42.640
<v Speaker 1>nuclear weapons and Saddam Hussein, the leader of Iraq at

0:07:42.680 --> 0:07:46.800
<v Speaker 1>the time, had already used chemical weapons against Iran during

0:07:46.840 --> 0:07:50.840
<v Speaker 1>the Iran Iraq War, the Aetola hired on an engineer

0:07:50.880 --> 0:07:56.480
<v Speaker 1>from Pakistan to help Iran, using plans for centrifuges that

0:07:56.560 --> 0:08:00.600
<v Speaker 1>the engineer had stolen from European companies. So This engineer

0:08:00.600 --> 0:08:03.200
<v Speaker 1>had worked on behalf of these European companies and then

0:08:03.320 --> 0:08:08.960
<v Speaker 1>essentially did a little industrial theft, stealing the plans for

0:08:09.000 --> 0:08:13.280
<v Speaker 1>centrifuges so that they could create a similar program in

0:08:13.400 --> 0:08:17.280
<v Speaker 1>nations like Pakistan. This was all happening in secret, obviously,

0:08:17.720 --> 0:08:20.120
<v Speaker 1>but Iran had gotten word of it, and so they

0:08:20.160 --> 0:08:25.040
<v Speaker 1>contacted this Pakistani engineer who agreed to help out Iran.

0:08:25.440 --> 0:08:30.000
<v Speaker 1>In nineteen Iran entered into a contract with Russia to

0:08:30.080 --> 0:08:34.000
<v Speaker 1>complete a nuclear power reactor at Boucher. This site in

0:08:34.040 --> 0:08:36.760
<v Speaker 1>Iran had been one of the original plan power plants

0:08:36.960 --> 0:08:41.040
<v Speaker 1>way back in nineteen fifty seven, but the various conflicts

0:08:41.080 --> 0:08:43.880
<v Speaker 1>between fifty seven and ninety five had delayed and even

0:08:43.920 --> 0:08:47.160
<v Speaker 1>destroyed the work that had been done on the location.

0:08:47.559 --> 0:08:51.319
<v Speaker 1>Iran and Russia were going to also build a uranium

0:08:51.440 --> 0:08:55.800
<v Speaker 1>enrichment plant kind of co located with this nuclear power plant,

0:08:56.240 --> 0:08:59.000
<v Speaker 1>but the United States stepped in and said to Russia, hey,

0:08:59.120 --> 0:09:03.440
<v Speaker 1>we think that's like a bad idea man, and Russia

0:09:03.480 --> 0:09:07.800
<v Speaker 1>eventually said dah and backed off. And that was supposedly that,

0:09:08.559 --> 0:09:12.640
<v Speaker 1>except it totally wasn't just that. In two thousand, Iran

0:09:12.760 --> 0:09:17.959
<v Speaker 1>started building a new facility at Natan's another site in Iran.

0:09:18.080 --> 0:09:25.400
<v Speaker 1>Iranian officials claimed that this facility was a desert eradication location,

0:09:26.120 --> 0:09:29.680
<v Speaker 1>but satellite imagery eventually showed that something else was up

0:09:29.880 --> 0:09:33.200
<v Speaker 1>in that site. The design of the facility suggested it

0:09:33.240 --> 0:09:36.880
<v Speaker 1>was going to house something super secret that was to

0:09:37.000 --> 0:09:40.720
<v Speaker 1>be protected from missile strikes and air strikes. And the

0:09:40.760 --> 0:09:44.840
<v Speaker 1>reason they were drawing this conclusion was that Iran was

0:09:44.880 --> 0:09:49.160
<v Speaker 1>clearly excavating a lot of land building a large underground

0:09:49.200 --> 0:09:54.040
<v Speaker 1>facility something that needed to be uh insulated from potential

0:09:54.080 --> 0:09:59.040
<v Speaker 1>air attack, and the entrance hallway into the facility had

0:09:59.040 --> 0:10:01.480
<v Speaker 1>a big U turn in it. It wasn't a straight

0:10:01.520 --> 0:10:05.280
<v Speaker 1>shot down into the heart of the facility. That you

0:10:05.480 --> 0:10:08.760
<v Speaker 1>turn was an indication that perhaps this was a way

0:10:09.000 --> 0:10:13.400
<v Speaker 1>to avoid a smart missile flying down the entryway and

0:10:13.520 --> 0:10:16.080
<v Speaker 1>hitting a target. If it had to turn nine degrees

0:10:16.240 --> 0:10:20.080
<v Speaker 1>or eighty degrees, then chances are no missile would actually

0:10:20.080 --> 0:10:23.240
<v Speaker 1>be able to do that, and it was thus a

0:10:23.360 --> 0:10:26.640
<v Speaker 1>tactic to avoid damage in the case of an air strike.

0:10:27.040 --> 0:10:31.840
<v Speaker 1>But why would you need that for some innocent desert

0:10:31.840 --> 0:10:35.160
<v Speaker 1>eradication facility. Why would it need to be underground and

0:10:35.200 --> 0:10:38.600
<v Speaker 1>have these kind of measures in place In two thousand two,

0:10:38.679 --> 0:10:42.600
<v Speaker 1>some whistleblowers alerted the u N that this facility would

0:10:42.679 --> 0:10:52.360
<v Speaker 1>actually be a uranium enrichment plant. Now, Iranian officials eventually said, okay, yeah,

0:10:52.520 --> 0:10:55.000
<v Speaker 1>but we were gonna tell you about it. We just

0:10:55.040 --> 0:10:57.800
<v Speaker 1>hadn't done that yet because there wasn't really any need to.

0:10:57.920 --> 0:11:02.240
<v Speaker 1>Were still months away from going online, so it's not

0:11:02.400 --> 0:11:06.360
<v Speaker 1>like there's any chance that this thing is is already

0:11:06.480 --> 0:11:10.560
<v Speaker 1>producing enriched uranium. We just want to have a facility

0:11:10.800 --> 0:11:13.400
<v Speaker 1>to create nuclear fuel that we're going to use for

0:11:13.400 --> 0:11:15.840
<v Speaker 1>our power plants. We want to be self sufficient, is all.

0:11:15.880 --> 0:11:17.880
<v Speaker 1>We don't want to have to buy our fuel from

0:11:17.960 --> 0:11:22.240
<v Speaker 1>other nations. The u N stepped up inspections of the facility,

0:11:22.320 --> 0:11:25.600
<v Speaker 1>or at least attempted to, although it initially encountered a

0:11:25.600 --> 0:11:28.439
<v Speaker 1>lot of resistance from Iran. The u N would say,

0:11:28.440 --> 0:11:30.720
<v Speaker 1>all right, well, we're ready to come in and investigate

0:11:30.760 --> 0:11:34.720
<v Speaker 1>this facility, and then the people in Iran would say, sorry,

0:11:34.760 --> 0:11:36.960
<v Speaker 1>it's not ready yet. Come back next month. And then

0:11:36.960 --> 0:11:38.600
<v Speaker 1>they would come back next month and say, all right,

0:11:38.600 --> 0:11:40.120
<v Speaker 1>we're ready to look at the facility and say, you

0:11:40.120 --> 0:11:41.760
<v Speaker 1>know what, we lost the keys, don't know where the

0:11:41.840 --> 0:11:45.640
<v Speaker 1>keys are. Could you come back maybe another day, and

0:11:45.679 --> 0:11:49.840
<v Speaker 1>it became increasingly clear, at least to the the investigators,

0:11:49.880 --> 0:11:52.079
<v Speaker 1>that something was up, and that there was a lot

0:11:52.120 --> 0:11:56.120
<v Speaker 1>of activity going on, perhaps to cover tracks, perhaps to

0:11:56.160 --> 0:11:59.440
<v Speaker 1>get rid of evidence, although it's impossible to say, because

0:11:59.520 --> 0:12:01.840
<v Speaker 1>unless you actually are there to witness what is happening,

0:12:01.840 --> 0:12:05.760
<v Speaker 1>you don't really know, but it seemed to imply that

0:12:05.800 --> 0:12:09.240
<v Speaker 1>there was something hainky going on. Eventually they were able

0:12:09.320 --> 0:12:14.720
<v Speaker 1>to set up a regular inspection schedule of this facility,

0:12:14.840 --> 0:12:18.360
<v Speaker 1>and they were there to make sure that the uranium

0:12:18.360 --> 0:12:21.520
<v Speaker 1>that was being produced was meant for nuclear power and

0:12:21.600 --> 0:12:26.040
<v Speaker 1>not nuclear weapons. And meanwhile, countries like the United States

0:12:26.080 --> 0:12:30.520
<v Speaker 1>were getting awfully antsy about Iran. On July six, two

0:12:30.520 --> 0:12:34.720
<v Speaker 1>thousand nine, Wiki Leaks hosted a note written by founder

0:12:34.800 --> 0:12:39.920
<v Speaker 1>Julian Assange that referenced some sort of serious nuclear accident

0:12:40.320 --> 0:12:43.720
<v Speaker 1>that had happened at the uranium enrichment facility. Now this

0:12:43.720 --> 0:12:47.160
<v Speaker 1>would have been shortly after the stux Net virus would

0:12:47.160 --> 0:12:50.640
<v Speaker 1>initially be released, but at this time, no one outside

0:12:50.800 --> 0:12:54.719
<v Speaker 1>of the people involved in stocks Net would have possibly

0:12:54.800 --> 0:12:59.839
<v Speaker 1>known about the virus and become public knowledge. Yet, in January,

0:13:00.160 --> 0:13:04.520
<v Speaker 1>a United Nations agency called the International Atomic Energy Agency

0:13:04.720 --> 0:13:07.920
<v Speaker 1>or I a e A. Began to notice that something

0:13:07.960 --> 0:13:13.520
<v Speaker 1>unusual was happening to the centrifuges at Iran's Natan's uranium

0:13:13.640 --> 0:13:16.880
<v Speaker 1>enrichment plant. They saw that there was a failure rate

0:13:16.880 --> 0:13:20.800
<v Speaker 1>that was unusually high. The agents would inspect the facilities

0:13:20.840 --> 0:13:23.440
<v Speaker 1>at least once a month and then occasionally with some

0:13:23.520 --> 0:13:27.199
<v Speaker 1>surprise inspections, and the whole point was just to make

0:13:27.200 --> 0:13:29.840
<v Speaker 1>sure that nothing illegal was happening, that Iran was in

0:13:29.880 --> 0:13:33.160
<v Speaker 1>fact not trying to stockpile enriched uranium in the effort

0:13:33.200 --> 0:13:39.920
<v Speaker 1>to build bombs. This was an important uh thing that

0:13:39.960 --> 0:13:42.280
<v Speaker 1>the U N was doing, but it also was not

0:13:42.360 --> 0:13:44.720
<v Speaker 1>the most efficient way of doing it if you wanted

0:13:44.760 --> 0:13:51.200
<v Speaker 1>to recognize trends, because they would swap out who went

0:13:51.360 --> 0:13:56.959
<v Speaker 1>to investigate the facility each time. That kind of makes sense.

0:13:57.000 --> 0:14:01.080
<v Speaker 1>You don't want one group to get compromised in any

0:14:01.120 --> 0:14:05.920
<v Speaker 1>way or fooled in some way. Sending new people sends

0:14:06.000 --> 0:14:08.520
<v Speaker 1>new sets of eyes. But it also meant that until

0:14:08.559 --> 0:14:11.839
<v Speaker 1>you were looking at aggregated data, you could not necessarily

0:14:11.920 --> 0:14:16.400
<v Speaker 1>see that something unusual is happening, And something unusual was

0:14:16.480 --> 0:14:20.480
<v Speaker 1>happening specifically to the centrifuges. Now to understand that. It

0:14:20.720 --> 0:14:23.440
<v Speaker 1>also helps to understand what the heck the centrifugures were

0:14:23.440 --> 0:14:25.480
<v Speaker 1>being used for in the first place, Like what is

0:14:25.520 --> 0:14:30.240
<v Speaker 1>their purpose in the process of refining uranium. Well, first,

0:14:30.720 --> 0:14:33.680
<v Speaker 1>nuclear fuel needs to be made up of between three

0:14:33.760 --> 0:14:37.760
<v Speaker 1>and a half to five percent uranium two thirty five isotope.

0:14:38.200 --> 0:14:41.840
<v Speaker 1>So isotopes are two or more forms of the same element,

0:14:42.160 --> 0:14:45.080
<v Speaker 1>in which the atoms of the different isotopes have a

0:14:45.080 --> 0:14:49.520
<v Speaker 1>different number of neutrons. Chemically, the two atoms behave the

0:14:49.560 --> 0:14:53.080
<v Speaker 1>same way, but they'll have different atomic masses because of

0:14:53.080 --> 0:14:56.080
<v Speaker 1>the difference in neutrons uh, and they'll have different decay

0:14:56.160 --> 0:14:59.040
<v Speaker 1>rates and things of that nature as well. So there

0:14:59.040 --> 0:15:03.760
<v Speaker 1>are three may jr isotopes of uranium that occur naturally

0:15:04.320 --> 0:15:07.960
<v Speaker 1>uh within the Earth's crust. So if you mine uranium,

0:15:07.960 --> 0:15:11.400
<v Speaker 1>you're gonna come up with a mixture of different isotopes

0:15:11.520 --> 0:15:15.320
<v Speaker 1>at different concentrations. Most of it, in fact, more than

0:15:15.440 --> 0:15:19.960
<v Speaker 1>nine of the stuff that occurs naturally is uranium two

0:15:19.960 --> 0:15:23.600
<v Speaker 1>thirty eight, less than one percent of it is uranium

0:15:23.680 --> 0:15:26.000
<v Speaker 1>two thirty five, and then you get a ten ty

0:15:26.120 --> 0:15:29.520
<v Speaker 1>tiny bit that's uranium two thirty four. If you want

0:15:29.520 --> 0:15:32.960
<v Speaker 1>to make nuclear fuel, you need a much higher percentage

0:15:32.960 --> 0:15:35.480
<v Speaker 1>of uranium two thirty five than what you find in nature.

0:15:35.520 --> 0:15:38.000
<v Speaker 1>In nature it's less than a percent, and fuel you

0:15:38.040 --> 0:15:39.680
<v Speaker 1>need it to be at least three and a half

0:15:39.800 --> 0:15:43.120
<v Speaker 1>to five percent. By the time you're getting into the

0:15:43.240 --> 0:15:47.040
<v Speaker 1>enrichment process. You need the uranium to be in gas form,

0:15:47.520 --> 0:15:51.200
<v Speaker 1>so you would get uranium or you would refine that

0:15:51.360 --> 0:15:54.600
<v Speaker 1>down to uranium oxide, and then you would take that

0:15:54.680 --> 0:15:57.680
<v Speaker 1>to a conversion plant that would take the uranium oxide

0:15:57.720 --> 0:16:02.200
<v Speaker 1>and turn it into a gas called uranium hexafluoride. This

0:16:02.320 --> 0:16:04.960
<v Speaker 1>gas has various isotubes of uranium in it. You have

0:16:05.040 --> 0:16:08.280
<v Speaker 1>both uranium two thirty eight and two thirty five, and

0:16:08.360 --> 0:16:10.720
<v Speaker 1>you have it in the concentrations you would expect because

0:16:10.760 --> 0:16:13.520
<v Speaker 1>it's from the stuff you mind from the ground. You

0:16:13.560 --> 0:16:18.680
<v Speaker 1>then feed that gas into tubes inside a centrifuge. Centrifuges

0:16:18.760 --> 0:16:21.800
<v Speaker 1>spin and they can spend it really high velocities. We're

0:16:21.800 --> 0:16:25.240
<v Speaker 1>talking tens of thousands of revolutions per minute now. When

0:16:25.280 --> 0:16:29.520
<v Speaker 1>they spin, it separates out the materials of different weight

0:16:29.800 --> 0:16:33.200
<v Speaker 1>within those tubes. The heavy stuff moves towards the edges

0:16:33.240 --> 0:16:35.760
<v Speaker 1>of the tubes, the sides of the tubes, and the

0:16:35.960 --> 0:16:39.040
<v Speaker 1>lighter stuff will move towards the center. So if you

0:16:39.120 --> 0:16:43.320
<v Speaker 1>spend the centrifugures at the right speed and you then

0:16:43.440 --> 0:16:47.200
<v Speaker 1>effectively scoop out the middle of the tube, you can

0:16:47.320 --> 0:16:50.440
<v Speaker 1>separate the uranium two thirty five from the uranium two

0:16:50.440 --> 0:16:52.320
<v Speaker 1>thirty eight. Now you actually have to do this in

0:16:52.360 --> 0:16:55.600
<v Speaker 1>a lot of different stages. You put them through one centrifuge,

0:16:55.640 --> 0:16:58.160
<v Speaker 1>you do the scooping process, you doing about another centrifuge.

0:16:58.240 --> 0:16:59.920
<v Speaker 1>You have to do this multiple times in order to

0:17:00.080 --> 0:17:04.679
<v Speaker 1>really get the right concentrations. Eventually you can do this

0:17:04.840 --> 0:17:07.920
<v Speaker 1>enough to manufacture the uranium pellets that you would use

0:17:08.119 --> 0:17:11.560
<v Speaker 1>for nuclear fuel. If you wanted to make a nuclear weapon,

0:17:11.920 --> 0:17:15.359
<v Speaker 1>you'd follow the same process, but you need way more

0:17:15.520 --> 0:17:19.360
<v Speaker 1>uranium two thirty five. Nuclear weapons typically have a proportion

0:17:19.400 --> 0:17:23.320
<v Speaker 1>of or more uranium two thirty five in them. Sometimes

0:17:23.320 --> 0:17:27.520
<v Speaker 1>it's or greater, so you need a lot more uranium,

0:17:27.600 --> 0:17:29.360
<v Speaker 1>and then you have to refine a lot of it

0:17:29.720 --> 0:17:31.400
<v Speaker 1>and rich a lot of it in order to get

0:17:31.440 --> 0:17:35.919
<v Speaker 1>to that level of uranium two thirty five. But it

0:17:36.040 --> 0:17:38.959
<v Speaker 1>is exactly the same process, it's just a matter of

0:17:39.480 --> 0:17:43.920
<v Speaker 1>more stuff. Centrifuges, as they turn out, are are delicate.

0:17:44.440 --> 0:17:47.560
<v Speaker 1>They're the ones that Iran was using. We're supposed to

0:17:47.600 --> 0:17:52.160
<v Speaker 1>have a ten year lifespan, but these are moving pieces

0:17:52.280 --> 0:17:55.919
<v Speaker 1>of machinery. They have mechanical parts, and they work at

0:17:56.000 --> 0:18:00.280
<v Speaker 1>high speeds, so eventually they'll fail. They may fail because

0:18:00.320 --> 0:18:04.400
<v Speaker 1>of mechanical error, human error, all sorts of different stuff

0:18:04.440 --> 0:18:07.880
<v Speaker 1>could cause them to break down. And because of that,

0:18:08.040 --> 0:18:11.879
<v Speaker 1>typically in a year you might have to replace about

0:18:11.920 --> 0:18:15.280
<v Speaker 1>ten of the centrifugures you have, even if they're brand new.

0:18:16.200 --> 0:18:19.400
<v Speaker 1>But the thing that the i a e A. Discovered

0:18:20.080 --> 0:18:24.000
<v Speaker 1>eventually after they looked at aggregated data, was that the

0:18:24.119 --> 0:18:27.680
<v Speaker 1>number of centrifuges that they were replacing at this uranium

0:18:27.680 --> 0:18:32.400
<v Speaker 1>and enrichment facility was much higher than that they had

0:18:32.400 --> 0:18:35.240
<v Speaker 1>centrifugures at this point, So you would expect about eight

0:18:35.280 --> 0:18:38.200
<v Speaker 1>hundred and seventy of them need to be replaced every year,

0:18:38.560 --> 0:18:41.240
<v Speaker 1>but apparently the number was actually much higher than that,

0:18:41.280 --> 0:18:44.560
<v Speaker 1>perhaps as high as two thousand or more, although the

0:18:44.600 --> 0:18:48.359
<v Speaker 1>actual figures were never published. But the i a e A.

0:18:48.600 --> 0:18:51.600
<v Speaker 1>Was keeping track of this stuff. They just didn't notice

0:18:51.640 --> 0:18:55.159
<v Speaker 1>the trend until they were looking at again a sequence

0:18:55.359 --> 0:18:58.160
<v Speaker 1>of these visits and then realized, hey, that that seems

0:18:58.200 --> 0:19:01.400
<v Speaker 1>like a pretty high number to place that many centrifuges.

0:19:01.480 --> 0:19:06.359
<v Speaker 1>Wonder what's happening with this? Well, while this was going on, uh,

0:19:06.520 --> 0:19:10.280
<v Speaker 1>there were other things happening that we're indicating that something

0:19:10.400 --> 0:19:14.919
<v Speaker 1>unusual had been unleashed in the world of computers. The

0:19:14.960 --> 0:19:17.000
<v Speaker 1>folks at I A e A at this point did

0:19:17.040 --> 0:19:20.760
<v Speaker 1>not suspect any kind of computer virus. They weren't sure

0:19:20.800 --> 0:19:23.040
<v Speaker 1>what was causing the centrifuges to fail. It could have

0:19:23.080 --> 0:19:26.400
<v Speaker 1>just been that they were really bad centrifugus, that Iran

0:19:26.520 --> 0:19:30.159
<v Speaker 1>had purchased them from a bad source, although Iran was

0:19:30.240 --> 0:19:32.959
<v Speaker 1>stating that they had actually made the whole thing themselves,

0:19:33.000 --> 0:19:36.080
<v Speaker 1>that the centrifugures were based off their own design, although

0:19:36.080 --> 0:19:41.479
<v Speaker 1>again the United Nations officials the investigators were not buying it.

0:19:41.640 --> 0:19:44.400
<v Speaker 1>They said, wow, these things look an awful lot like

0:19:45.080 --> 0:19:47.160
<v Speaker 1>the ones that were being used in Europe a few

0:19:47.240 --> 0:19:49.120
<v Speaker 1>years ago. In fact, if I didn't know any better,

0:19:49.160 --> 0:19:51.600
<v Speaker 1>I would say that these were direct copies of that

0:19:51.680 --> 0:19:55.920
<v Speaker 1>and that they were based off stolen information. But Iran's

0:19:55.920 --> 0:19:59.520
<v Speaker 1>messaging was that no, these were of our design and

0:19:59.720 --> 0:20:02.480
<v Speaker 1>we built them at any rate. I A e A

0:20:02.640 --> 0:20:06.520
<v Speaker 1>wasn't sure why these centrifuges were starting to fail at

0:20:06.520 --> 0:20:09.760
<v Speaker 1>that same time, or actually a little bit later. In June,

0:20:10.760 --> 0:20:14.840
<v Speaker 1>there was a cybersecurity professional named Seragei Ulasson in Belarus

0:20:15.119 --> 0:20:18.880
<v Speaker 1>who was investigating some really weird computer behavior that had

0:20:18.920 --> 0:20:23.119
<v Speaker 1>been reported in an Iranian computer. The computer in question

0:20:23.240 --> 0:20:28.400
<v Speaker 1>was caught in an endless crash and reboot cycle and

0:20:29.280 --> 0:20:32.639
<v Speaker 1>they weren't really sure what was causing it. The culprit

0:20:33.240 --> 0:20:36.400
<v Speaker 1>looked like it might have been the anti virus software

0:20:36.640 --> 0:20:40.040
<v Speaker 1>that was on the computer, that something was not compatible,

0:20:40.680 --> 0:20:44.600
<v Speaker 1>and the antivirus software came from the company that uh

0:20:44.720 --> 0:20:47.840
<v Speaker 1>Sarageulawson was working for. He was working for this company

0:20:47.840 --> 0:20:52.520
<v Speaker 1>called virus Block Ada. The Iranian computer had that anti

0:20:52.600 --> 0:20:55.760
<v Speaker 1>virus program on it. It was purchased originally from a reseller,

0:20:55.880 --> 0:20:58.840
<v Speaker 1>so it wasn't purchased directly from the Belarus company, but

0:20:59.000 --> 0:21:02.920
<v Speaker 1>rather an Ira Auny and company that had the right

0:21:03.119 --> 0:21:07.840
<v Speaker 1>to re sell this anti virus software, and originally the

0:21:07.840 --> 0:21:10.800
<v Speaker 1>person who owned the computer or the the agency that

0:21:10.920 --> 0:21:15.840
<v Speaker 1>owned the computer contacted the reseller and said, I'm getting

0:21:15.880 --> 0:21:18.480
<v Speaker 1>this error. It's the computer just keeps crashing and trying

0:21:18.480 --> 0:21:22.640
<v Speaker 1>to reboot. What's going on the reseller eventually fielded that

0:21:23.119 --> 0:21:28.199
<v Speaker 1>question up to Lawson. Lawson got permission to log into

0:21:28.240 --> 0:21:31.560
<v Speaker 1>this problematic computer using a remote log in, and he

0:21:31.640 --> 0:21:33.520
<v Speaker 1>began to look around to see what the heck was

0:21:33.560 --> 0:21:37.840
<v Speaker 1>going on, and he eventually suspected the machine had been

0:21:37.880 --> 0:21:41.679
<v Speaker 1>infected by some malware and that this malware included a

0:21:41.800 --> 0:21:46.440
<v Speaker 1>root kit quick refresher. A root kit is software that

0:21:46.520 --> 0:21:51.160
<v Speaker 1>gives an unauthorized party access to control of a computer system.

0:21:51.520 --> 0:21:55.040
<v Speaker 1>Hackers use this to get a back door access and

0:21:55.080 --> 0:21:57.960
<v Speaker 1>get information on computers, or they do it to create

0:21:58.080 --> 0:22:02.000
<v Speaker 1>boton nets. Moreover, a root kit masks this activity. It

0:22:02.240 --> 0:22:05.639
<v Speaker 1>acts as like a shield to hide it from the

0:22:05.640 --> 0:22:08.800
<v Speaker 1>host computer in an effort to escape detection. So a

0:22:08.840 --> 0:22:12.000
<v Speaker 1>good root kit is doing all this allowing someone to

0:22:12.160 --> 0:22:16.920
<v Speaker 1>remotely access your computer, but you can't tell because it's

0:22:17.040 --> 0:22:20.640
<v Speaker 1>hiding all that activity from you. Well, like all malware,

0:22:20.720 --> 0:22:23.719
<v Speaker 1>root kits are only useful if the targeted machine doesn't

0:22:23.720 --> 0:22:26.959
<v Speaker 1>have suitable anti virus protection on it. It could be

0:22:27.280 --> 0:22:30.040
<v Speaker 1>out of date, or it might not have antivirus software

0:22:30.040 --> 0:22:33.240
<v Speaker 1>on it at all, or it might be so new

0:22:33.960 --> 0:22:38.639
<v Speaker 1>that antivirus software doesn't yet have a profile on that

0:22:38.720 --> 0:22:41.240
<v Speaker 1>type of root kit. Which means that it will escape

0:22:41.280 --> 0:22:44.960
<v Speaker 1>the anti virus software's detection because it doesn't know to

0:22:45.040 --> 0:22:48.760
<v Speaker 1>look for it. Once anti virus software companies learn of

0:22:48.800 --> 0:22:51.520
<v Speaker 1>a piece of malware, they can then adjust their software

0:22:51.640 --> 0:22:54.480
<v Speaker 1>to identify and block those programs. But if there is

0:22:54.520 --> 0:22:58.160
<v Speaker 1>a gap there, the malware can go for a while

0:22:58.240 --> 0:23:01.399
<v Speaker 1>without detection, and it means that all machines can be

0:23:01.480 --> 0:23:04.919
<v Speaker 1>vulnerable to those attacks until someone catches on. And that

0:23:05.040 --> 0:23:08.240
<v Speaker 1>seems to be what was going on in this case.

0:23:08.680 --> 0:23:11.080
<v Speaker 1>Now I have a lot more to say about the

0:23:11.160 --> 0:23:13.760
<v Speaker 1>early detection of stucks net, but before I get into that,

0:23:13.880 --> 0:23:23.959
<v Speaker 1>let's take a quick break to thank our sponsor. Alright,

0:23:24.000 --> 0:23:28.960
<v Speaker 1>So a lawson realized that whomever was responsible for creating

0:23:29.000 --> 0:23:33.679
<v Speaker 1>this malware that was causing this this computer to crash repeatedly,

0:23:34.280 --> 0:23:37.600
<v Speaker 1>had done so by finding what is called a zero

0:23:37.920 --> 0:23:42.400
<v Speaker 1>day exploit. A zero day exploit is a vulnerability within

0:23:42.480 --> 0:23:46.040
<v Speaker 1>a piece of software code that has not yet been

0:23:46.080 --> 0:23:51.080
<v Speaker 1>identified by anybody else, including the people who made the

0:23:51.160 --> 0:23:54.400
<v Speaker 1>software code in the first place. The software coders are

0:23:54.440 --> 0:23:57.560
<v Speaker 1>likely completely unaware of it. In fact, that's that's really

0:23:57.600 --> 0:24:00.879
<v Speaker 1>what makes it zero day is the fact that you know,

0:24:00.920 --> 0:24:02.879
<v Speaker 1>you come out with like a new version of of

0:24:02.880 --> 0:24:05.919
<v Speaker 1>an operating system, for example, and you are not aware

0:24:06.000 --> 0:24:09.680
<v Speaker 1>that that part of that operating system has this glaring

0:24:09.760 --> 0:24:14.280
<v Speaker 1>flaw in it that uh could be exploited. That's a

0:24:14.400 --> 0:24:18.240
<v Speaker 1>zero day exploit, and that ignorance is an incredibly powerful

0:24:18.240 --> 0:24:21.879
<v Speaker 1>weapon for hackers. They will end up writing code that

0:24:22.040 --> 0:24:24.600
<v Speaker 1>can exploit this vulnerability, and they know that there's no

0:24:24.640 --> 0:24:28.679
<v Speaker 1>protection against it because the responsible parties for the software

0:24:28.960 --> 0:24:33.240
<v Speaker 1>have not even realized that there's a potential for exploitation.

0:24:33.600 --> 0:24:36.000
<v Speaker 1>The lawson figured out that the malware had to have

0:24:36.080 --> 0:24:40.919
<v Speaker 1>been distributed by a USB thumb drive initially. Later on,

0:24:41.200 --> 0:24:43.480
<v Speaker 1>researchers would figure out that the code would allow up

0:24:43.480 --> 0:24:47.320
<v Speaker 1>to three machines to be infected by the same USB

0:24:47.560 --> 0:24:51.040
<v Speaker 1>flash drive before the malware would prompt a computer to

0:24:51.119 --> 0:24:54.800
<v Speaker 1>delete the contents of the flash drive, so it's kind

0:24:54.800 --> 0:24:58.040
<v Speaker 1>of like a self destruct button. After three infections, the

0:24:58.160 --> 0:25:01.520
<v Speaker 1>drive would be wiped. F a propagation could happen across

0:25:01.560 --> 0:25:05.760
<v Speaker 1>a compromised network through computer computer connections, and later on

0:25:06.119 --> 0:25:10.080
<v Speaker 1>they discovered even other different ways that the virus can

0:25:10.080 --> 0:25:12.920
<v Speaker 1>move from computer to computer. It did not, however, move

0:25:13.000 --> 0:25:17.560
<v Speaker 1>across the Internet. This was a piece of malware that

0:25:17.640 --> 0:25:21.920
<v Speaker 1>was designed to infect computers that were on local networks

0:25:21.920 --> 0:25:25.240
<v Speaker 1>but perhaps not connected to the Internet at large. So

0:25:25.680 --> 0:25:28.560
<v Speaker 1>that was why they were using USB drives in the

0:25:28.600 --> 0:25:31.080
<v Speaker 1>first place. Now, that did come with a disadvantage. It

0:25:31.119 --> 0:25:34.280
<v Speaker 1>means that you have to get physical access to a

0:25:34.359 --> 0:25:39.000
<v Speaker 1>machine to get the malware from the USB drive onto

0:25:39.000 --> 0:25:42.240
<v Speaker 1>the computer, and that drastically reduces the number of computers

0:25:42.240 --> 0:25:45.680
<v Speaker 1>you could potentially infect. So why would you do this, Well,

0:25:45.720 --> 0:25:48.280
<v Speaker 1>one reason to go with the USB delivery mechanism is

0:25:48.320 --> 0:25:52.360
<v Speaker 1>to target computers that have an air gap. And that

0:25:52.440 --> 0:25:54.480
<v Speaker 1>air gap is what I was talking about a second ago.

0:25:54.600 --> 0:25:57.720
<v Speaker 1>That's a computer or even a network of computers that

0:25:57.760 --> 0:26:01.879
<v Speaker 1>has no direct connection to the wider Internet at large.

0:26:02.200 --> 0:26:05.320
<v Speaker 1>As an air gap between the Internet and the computer

0:26:05.480 --> 0:26:08.560
<v Speaker 1>or system of computers, it's kind of like a self

0:26:08.560 --> 0:26:11.840
<v Speaker 1>contained island. It's cut off from the rest of the world,

0:26:12.160 --> 0:26:15.199
<v Speaker 1>and it keeps the system safe from most forms of

0:26:15.240 --> 0:26:19.119
<v Speaker 1>hacker intrusions. If there are no pathways that lead to

0:26:19.160 --> 0:26:21.800
<v Speaker 1>the system, there's not a whole lot of hacker can do.

0:26:22.440 --> 0:26:25.600
<v Speaker 1>A true air gap system would have no connectivity to

0:26:25.640 --> 0:26:28.760
<v Speaker 1>the Internet at all. Now, some systems have what we

0:26:28.880 --> 0:26:31.520
<v Speaker 1>call an air gap but they really have limited and

0:26:31.600 --> 0:26:35.480
<v Speaker 1>controlled access to the Internet, typically through a computer or router.

0:26:35.560 --> 0:26:38.360
<v Speaker 1>The acts as a gatekeeper or portal. But if you

0:26:38.400 --> 0:26:41.199
<v Speaker 1>put your malware on a USB stick and then you

0:26:41.240 --> 0:26:44.320
<v Speaker 1>convince someone with a physical access to the machine to

0:26:44.440 --> 0:26:49.080
<v Speaker 1>insert the USB drive and air gap isn't really a problem.

0:26:49.119 --> 0:26:52.160
<v Speaker 1>It might, however, mean that you, as a hacker, will

0:26:52.240 --> 0:26:55.800
<v Speaker 1>remain unaware of your success. If the target machine has

0:26:55.800 --> 0:26:58.200
<v Speaker 1>no way to phone home, if there's no way for

0:26:58.240 --> 0:27:02.520
<v Speaker 1>the target machine to indicate hey, success, then you may

0:27:02.560 --> 0:27:06.640
<v Speaker 1>just be hoping that whatever you planned on doing was working. So,

0:27:06.680 --> 0:27:09.639
<v Speaker 1>like I said, all the vectors of attack for stocks

0:27:09.680 --> 0:27:14.200
<v Speaker 1>net were based off of either USB or local network connections,

0:27:14.560 --> 0:27:19.000
<v Speaker 1>but not over the Internet. And also the USB stick

0:27:19.080 --> 0:27:22.600
<v Speaker 1>attack did not use auto run, at least not after

0:27:22.680 --> 0:27:26.000
<v Speaker 1>the first initial wave of attacks. There were three separate

0:27:26.040 --> 0:27:29.000
<v Speaker 1>waves of attacks, and the second and third one did

0:27:29.000 --> 0:27:32.360
<v Speaker 1>not use the auto run feature. A lot of malware

0:27:32.520 --> 0:27:35.240
<v Speaker 1>does depend on auto run, and that's a feature that

0:27:35.280 --> 0:27:38.720
<v Speaker 1>will automatically launch a program from something like a USB

0:27:38.920 --> 0:27:41.919
<v Speaker 1>drive or an optical drive once you insert the media.

0:27:41.960 --> 0:27:44.440
<v Speaker 1>You're probably familiar with this. Let's say that you've got

0:27:44.840 --> 0:27:47.879
<v Speaker 1>a DVD, an actual movie on a DVD and you

0:27:47.920 --> 0:27:50.680
<v Speaker 1>put it into your computer, and the computer automatically launches

0:27:50.920 --> 0:27:54.320
<v Speaker 1>the DVD player software so that you can watch it

0:27:54.640 --> 0:27:58.240
<v Speaker 1>as soon as the DVD has gone into the optical drive. Well,

0:27:58.280 --> 0:28:01.120
<v Speaker 1>that speeds things up for the user, makes it more convenient,

0:28:01.160 --> 0:28:03.560
<v Speaker 1>you don't have to hunt for the right program. But

0:28:03.680 --> 0:28:07.800
<v Speaker 1>it does present a security risk because if the software

0:28:07.840 --> 0:28:11.880
<v Speaker 1>on the media is malicious, the computer is just automatically

0:28:11.960 --> 0:28:16.320
<v Speaker 1>launched bad software. But here's the thing. You can turn

0:28:16.520 --> 0:28:20.120
<v Speaker 1>off the auto run feature and a lot of systems

0:28:20.240 --> 0:28:23.479
<v Speaker 1>will do that because it is a way to limit

0:28:23.600 --> 0:28:27.479
<v Speaker 1>the risk and the vulnerability of those systems. You just

0:28:27.560 --> 0:28:30.879
<v Speaker 1>turn off auto run and then your planned form of

0:28:30.920 --> 0:28:34.000
<v Speaker 1>attack is not going to work. Someone puts that media

0:28:34.080 --> 0:28:36.560
<v Speaker 1>into a computer where the auto run has been switched off,

0:28:36.800 --> 0:28:40.280
<v Speaker 1>they'll get prompted or they'll they'll have the chance to

0:28:40.480 --> 0:28:43.680
<v Speaker 1>run that stuff themselves. But chances are you go, if

0:28:43.720 --> 0:28:46.600
<v Speaker 1>you don't recognize a program, you're not just gonna launch it.

0:28:47.000 --> 0:28:49.360
<v Speaker 1>You might do some snooping first and find out if

0:28:49.400 --> 0:28:51.760
<v Speaker 1>this is in fact something you want to run. So

0:28:51.840 --> 0:28:55.480
<v Speaker 1>to remove that possibility, you might want to not use

0:28:55.520 --> 0:29:00.120
<v Speaker 1>auto run feature to launch your malware. So that's what

0:29:00.360 --> 0:29:03.680
<v Speaker 1>the hackers responsible for stucks net did. They decided that

0:29:03.720 --> 0:29:07.120
<v Speaker 1>they would use a different approach. They targeted what are

0:29:07.200 --> 0:29:10.880
<v Speaker 1>called l n K files. So an l n K

0:29:11.120 --> 0:29:15.160
<v Speaker 1>file carries the information to display icons next to file

0:29:15.240 --> 0:29:19.000
<v Speaker 1>types and applications like Windows Explorer. So if you've opened

0:29:19.040 --> 0:29:21.480
<v Speaker 1>up a file directory type of program and you've seen

0:29:21.480 --> 0:29:24.160
<v Speaker 1>those little icons next to file names, that's due to

0:29:24.240 --> 0:29:27.360
<v Speaker 1>an l n K file. This was a pretty sophisticated

0:29:27.360 --> 0:29:30.240
<v Speaker 1>form of attack, and as far as Lawson could figure out,

0:29:30.280 --> 0:29:32.520
<v Speaker 1>it was the first of its type. Not turned out

0:29:33.120 --> 0:29:35.200
<v Speaker 1>that it was not the very first of its type,

0:29:35.480 --> 0:29:39.360
<v Speaker 1>but the previous implementations of this attack had not really

0:29:39.360 --> 0:29:44.800
<v Speaker 1>received widespread coverage, so it was still really new. Adding

0:29:44.840 --> 0:29:47.880
<v Speaker 1>to this sophistication was the fact that there were four

0:29:48.000 --> 0:29:51.040
<v Speaker 1>different versions of the l en k files on those

0:29:51.160 --> 0:29:54.640
<v Speaker 1>USB sticks, and that meant that they could affect up

0:29:54.680 --> 0:29:58.600
<v Speaker 1>to seven different versions of Windows. That increased the number

0:29:58.600 --> 0:30:00.640
<v Speaker 1>of potential targets for the mal where so if a

0:30:00.720 --> 0:30:03.160
<v Speaker 1>computer was running one version of Windows, or maybe the

0:30:03.160 --> 0:30:05.920
<v Speaker 1>next one or the next one, it still might be vulnerable.

0:30:06.440 --> 0:30:10.880
<v Speaker 1>The only real thing that limited it was it needed

0:30:10.920 --> 0:30:14.640
<v Speaker 1>to be a thirty two bit installation of Windows. If

0:30:14.680 --> 0:30:17.640
<v Speaker 1>it were a sixty four bit installation, the virus was

0:30:17.680 --> 0:30:20.719
<v Speaker 1>not going to work on it. Later on, researchers at

0:30:20.760 --> 0:30:25.680
<v Speaker 1>the security firm Kaspersky UH discovered other zero day exploits

0:30:25.680 --> 0:30:27.680
<v Speaker 1>that the virus took advantage of. So there wasn't just

0:30:27.920 --> 0:30:34.280
<v Speaker 1>one zero day vulnerability that stucks net could glom onto.

0:30:34.600 --> 0:30:37.200
<v Speaker 1>There were three more that Kaspersky found at that point.

0:30:37.840 --> 0:30:42.360
<v Speaker 1>One exploited a print spooler vulnerability, and it would propagate

0:30:42.480 --> 0:30:46.080
<v Speaker 1>the virus across networks that had a shared network printer

0:30:46.160 --> 0:30:48.720
<v Speaker 1>and a lot of a lot of networks do the

0:30:48.760 --> 0:30:53.760
<v Speaker 1>other two vectors use something called privilege escalation, which is

0:30:53.800 --> 0:30:56.200
<v Speaker 1>where a program is able to leverage exploits to gain

0:30:56.600 --> 0:31:00.800
<v Speaker 1>eventually a system level control over computer is even if

0:31:00.840 --> 0:31:04.000
<v Speaker 1>those computers have been locked down. The combination of all

0:31:04.040 --> 0:31:07.000
<v Speaker 1>the exploits suggested that the people responsible for the virus

0:31:07.400 --> 0:31:12.040
<v Speaker 1>were serious heavy hitters who really desperately wanted to target

0:31:12.120 --> 0:31:15.880
<v Speaker 1>specific computers. And it raised some really big questions why

0:31:15.920 --> 0:31:20.520
<v Speaker 1>would you use four zero day exploits because common logic

0:31:20.600 --> 0:31:24.000
<v Speaker 1>said you should just stick to one at a time.

0:31:24.320 --> 0:31:28.000
<v Speaker 1>Once a zero day exploit is discovered, the clock is

0:31:28.040 --> 0:31:33.120
<v Speaker 1>ticking before someone patches that respective software to plug up

0:31:33.120 --> 0:31:36.680
<v Speaker 1>that vulnerability so that the exploit won't work anymore. So

0:31:36.720 --> 0:31:41.640
<v Speaker 1>the zero day exploit is only really valuable until people

0:31:41.680 --> 0:31:43.960
<v Speaker 1>discover it. If you have more than one zero day

0:31:43.960 --> 0:31:47.840
<v Speaker 1>exploit involved in your malware, then you run the risk

0:31:48.120 --> 0:31:52.280
<v Speaker 1>of someone discovering all of those exploits if the malware

0:31:52.320 --> 0:31:56.440
<v Speaker 1>itself becomes evident, and if they find all of those exploits,

0:31:56.440 --> 0:31:59.880
<v Speaker 1>that all of those can be patched, which means you

0:32:00.080 --> 0:32:03.080
<v Speaker 1>lose all of those vectors of attack in a single

0:32:03.200 --> 0:32:08.520
<v Speaker 1>cell swoop. So this was kind of considered a big gamble.

0:32:08.680 --> 0:32:11.520
<v Speaker 1>Why would you throw all of your eggs into this

0:32:11.680 --> 0:32:15.200
<v Speaker 1>basket having all of four zero day exploits. By the way,

0:32:15.200 --> 0:32:17.720
<v Speaker 1>there was a fifth one actually that they had not

0:32:17.840 --> 0:32:21.320
<v Speaker 1>yet discovered, though that one ended up getting patched after

0:32:21.360 --> 0:32:25.040
<v Speaker 1>the first wave of attacks, uh not because of stocks net.

0:32:25.240 --> 0:32:30.480
<v Speaker 1>The fifth vulnerability had been independently discovered through other means

0:32:31.040 --> 0:32:34.880
<v Speaker 1>and had been patched, But ultimately that did mean five

0:32:34.920 --> 0:32:39.680
<v Speaker 1>different zero day vulnerabilities were used when designing stucks net.

0:32:39.760 --> 0:32:42.640
<v Speaker 1>Over the course of the life of stucks neet. On

0:32:42.760 --> 0:32:45.960
<v Speaker 1>top of those zero day exploits, the virus used four

0:32:46.160 --> 0:32:49.880
<v Speaker 1>other means to copy and send itself along to other machines.

0:32:50.200 --> 0:32:53.320
<v Speaker 1>So in total it had nine different methods to spread

0:32:53.360 --> 0:32:56.600
<v Speaker 1>the virus. One of them leveraged of vulnerability in special

0:32:56.840 --> 0:33:02.160
<v Speaker 1>Semens software to gain system level privileges. Siemens is a

0:33:02.240 --> 0:33:05.440
<v Speaker 1>company it's in Germany that creates all sorts of different

0:33:05.520 --> 0:33:10.680
<v Speaker 1>kinds of software. The software in particular that stocks net

0:33:10.720 --> 0:33:14.240
<v Speaker 1>was concerned with was for something called p lcs programmable

0:33:14.240 --> 0:33:18.760
<v Speaker 1>logic circuits, so are controllers rather logic controllers. So these

0:33:18.760 --> 0:33:25.880
<v Speaker 1>are little implementations that allow computers to communicate with various devices,

0:33:25.920 --> 0:33:30.320
<v Speaker 1>typically that are used in industrial applications, so it might

0:33:30.360 --> 0:33:34.720
<v Speaker 1>be like a conveyor belt or valve system, that kind

0:33:34.720 --> 0:33:37.880
<v Speaker 1>of thing, which is a pretty odd thing for viruses

0:33:38.040 --> 0:33:42.440
<v Speaker 1>to target. Typically, there was another clever way that the

0:33:42.480 --> 0:33:46.240
<v Speaker 1>malware could spread. It would create a file sharing server

0:33:46.400 --> 0:33:50.160
<v Speaker 1>folder on every computer it infected if that computer were

0:33:50.160 --> 0:33:54.080
<v Speaker 1>connected to other infected machines. So it's a computer on

0:33:54.080 --> 0:33:56.560
<v Speaker 1>a network and other computers on the network also got

0:33:56.600 --> 0:33:59.120
<v Speaker 1>infected by stocks net. They would chat with each other

0:33:59.320 --> 0:34:02.240
<v Speaker 1>and they would com hair notes. They would say, hey,

0:34:02.360 --> 0:34:04.680
<v Speaker 1>one version of stucks net are you running. I've got

0:34:04.720 --> 0:34:07.520
<v Speaker 1>one point two and they might say, well, I've got

0:34:07.520 --> 0:34:11.080
<v Speaker 1>one point to one. Hey, your version is more current

0:34:11.120 --> 0:34:13.240
<v Speaker 1>than my version is, Give me some of that sweet

0:34:13.239 --> 0:34:17.600
<v Speaker 1>stucks net, And sure enough the system would propagate the

0:34:17.680 --> 0:34:21.440
<v Speaker 1>latest version of stucks net across its network. So it

0:34:21.520 --> 0:34:25.759
<v Speaker 1>was kind of appear to appear approach to spreading the

0:34:25.840 --> 0:34:28.120
<v Speaker 1>latest and greatest version of stuck set. And if someone

0:34:28.200 --> 0:34:31.560
<v Speaker 1>came in and infected a new computer with an even

0:34:31.840 --> 0:34:35.760
<v Speaker 1>more recent version of stocks net, then shortly that version

0:34:35.760 --> 0:34:39.160
<v Speaker 1>of stucks net would propagate across the other infected computers

0:34:39.239 --> 0:34:41.200
<v Speaker 1>on the network. It was a way of making sure

0:34:41.480 --> 0:34:44.399
<v Speaker 1>everyone was on the same page, even without them being

0:34:44.600 --> 0:34:48.200
<v Speaker 1>aware of it. The malware would install two driver modules

0:34:48.280 --> 0:34:53.600
<v Speaker 1>on the infected computer, and uh these driver modules were

0:34:54.400 --> 0:34:58.919
<v Speaker 1>they were posing as as software drivers. Software drivers are

0:34:59.760 --> 0:35:03.839
<v Speaker 1>lee aisons between a computer and some other piece of hardware. So,

0:35:03.960 --> 0:35:07.359
<v Speaker 1>for example, if you have a separate computer mouse, or

0:35:07.400 --> 0:35:09.840
<v Speaker 1>a microphone that you plug into your computer, or a

0:35:09.880 --> 0:35:13.560
<v Speaker 1>webcam that you plug into your computer, the driver is

0:35:13.640 --> 0:35:18.040
<v Speaker 1>what allows for meaningful communication between that device and your computer.

0:35:18.400 --> 0:35:21.640
<v Speaker 1>You may have occasionally had an issue where one of

0:35:21.640 --> 0:35:24.520
<v Speaker 1>your peripherals no longer seems to work on your computer,

0:35:24.800 --> 0:35:26.920
<v Speaker 1>and it's because the driver is out of date. It

0:35:27.000 --> 0:35:29.200
<v Speaker 1>may be that there was an update to the operating

0:35:29.239 --> 0:35:33.600
<v Speaker 1>system and that update has broken that communication channel between

0:35:33.760 --> 0:35:36.680
<v Speaker 1>your peripheral and your computer, and it requires that you

0:35:36.800 --> 0:35:41.120
<v Speaker 1>update your software drivers so that now the two machines

0:35:41.200 --> 0:35:44.800
<v Speaker 1>can talk to each other again. That's what the malware

0:35:44.840 --> 0:35:49.840
<v Speaker 1>would install. These these apparently innocent, at least on casual glance,

0:35:50.680 --> 0:35:55.920
<v Speaker 1>driver modules onto the infected computer. Now normally, later versions

0:35:55.960 --> 0:35:59.480
<v Speaker 1>of Windows would send an alert to a user whenever

0:35:59.480 --> 0:36:03.319
<v Speaker 1>an up of software was to be installed. If you've

0:36:03.400 --> 0:36:06.160
<v Speaker 1>used Windows seven or later than you know about this.

0:36:06.200 --> 0:36:09.080
<v Speaker 1>You get that little window that pops up and says, hey,

0:36:09.120 --> 0:36:11.120
<v Speaker 1>I see that you're trying to install this thing. Is

0:36:11.160 --> 0:36:14.399
<v Speaker 1>that really your intention? Because it gives you the chance

0:36:14.440 --> 0:36:17.320
<v Speaker 1>to say, heck no, I didn't know that was happening,

0:36:17.440 --> 0:36:20.040
<v Speaker 1>stop it, and then you could investigate, and if it

0:36:20.120 --> 0:36:22.360
<v Speaker 1>were malware, you would know something was up and you

0:36:22.360 --> 0:36:25.880
<v Speaker 1>can maybe do something about it. So the goal of

0:36:25.920 --> 0:36:28.880
<v Speaker 1>the hackers is not to have this window pop up.

0:36:29.040 --> 0:36:32.720
<v Speaker 1>So this malware stocks Net was a lot more insidious

0:36:33.080 --> 0:36:38.200
<v Speaker 1>than just a fake driver. It contained a digital certificate

0:36:38.560 --> 0:36:43.760
<v Speaker 1>from a legitimate Taiwanese hardware company called real tech Semiconductor

0:36:44.480 --> 0:36:49.319
<v Speaker 1>digital certificates are like authorized signatures. These are away for

0:36:49.400 --> 0:36:53.280
<v Speaker 1>companies to authenticate that the software they distribute in fact

0:36:53.400 --> 0:36:57.160
<v Speaker 1>actually comes from them, and big players that are trusted

0:36:57.400 --> 0:37:00.880
<v Speaker 1>can use those certificates to authenticate. Driver is another software

0:37:01.000 --> 0:37:04.080
<v Speaker 1>machines without the need for that pop up notification. You're

0:37:04.080 --> 0:37:07.000
<v Speaker 1>not gonna get it every time, because essentially what's happening

0:37:07.040 --> 0:37:10.279
<v Speaker 1>is Microsoft says, hey, there's this software that wants to

0:37:10.360 --> 0:37:13.960
<v Speaker 1>execute on this machine. Oh wait, this software is from

0:37:13.960 --> 0:37:17.160
<v Speaker 1>such and such company, and I know they're cool, And

0:37:17.280 --> 0:37:20.680
<v Speaker 1>it's a digital certificate that tells me that it's absolutely

0:37:20.760 --> 0:37:24.480
<v Speaker 1>from that company because they protect their certification process, so

0:37:24.520 --> 0:37:27.560
<v Speaker 1>I know it's not from anyone else, so I don't

0:37:27.560 --> 0:37:30.080
<v Speaker 1>need to worry the user. I'm not gonna send that

0:37:30.120 --> 0:37:32.960
<v Speaker 1>pop up because everything's totally on the up and up,

0:37:33.080 --> 0:37:37.319
<v Speaker 1>so as long as the software is authenticated as being

0:37:37.400 --> 0:37:40.759
<v Speaker 1>from a trusted source, there's no extra step in there.

0:37:41.000 --> 0:37:44.400
<v Speaker 1>But that created a pathway for potential attacks, though at

0:37:44.400 --> 0:37:47.160
<v Speaker 1>the time not very many people were considering that. One

0:37:47.160 --> 0:37:50.760
<v Speaker 1>person who was was a security expert with the Finnish

0:37:50.920 --> 0:37:55.080
<v Speaker 1>company f Secure. That is a company from Finland, not

0:37:55.160 --> 0:38:00.320
<v Speaker 1>a company that finished things, and in July he pointed

0:38:00.320 --> 0:38:02.239
<v Speaker 1>out that if a hacker were to get access to

0:38:02.320 --> 0:38:06.880
<v Speaker 1>digital certificates, they could potentially sneak in malware onto computers

0:38:07.040 --> 0:38:09.719
<v Speaker 1>using that, which was exactly what was going on with

0:38:09.760 --> 0:38:14.600
<v Speaker 1>stucks net. Now, this researcher wasn't aware of stocks neet

0:38:14.640 --> 0:38:17.279
<v Speaker 1>at the time. He was just saying, hey, this is

0:38:17.320 --> 0:38:19.719
<v Speaker 1>a potential problem. And as it turns out, it wasn't

0:38:19.760 --> 0:38:22.080
<v Speaker 1>just a potential problem, it was a real problem that

0:38:22.160 --> 0:38:25.839
<v Speaker 1>was going on at that very moment. Moreover, digital certificates

0:38:25.840 --> 0:38:28.520
<v Speaker 1>have an expiration date, and this is to help make

0:38:28.520 --> 0:38:32.200
<v Speaker 1>sure that they remain secure. You have to renew your

0:38:32.200 --> 0:38:35.920
<v Speaker 1>certificate so that it doesn't stick around long enough for

0:38:36.040 --> 0:38:38.280
<v Speaker 1>bad actors to get hold of it and then leverage

0:38:38.280 --> 0:38:41.000
<v Speaker 1>it the way the malware authors had done in the

0:38:41.000 --> 0:38:45.000
<v Speaker 1>case of stocks net. So you end up creating a

0:38:45.000 --> 0:38:47.920
<v Speaker 1>certificate that has an expiration date on it. After the

0:38:47.960 --> 0:38:53.759
<v Speaker 1>expiration date, you you then administer a new certificate that

0:38:54.040 --> 0:38:57.680
<v Speaker 1>has new code on it, but it still has that authentication.

0:38:58.040 --> 0:38:59.640
<v Speaker 1>And that way, if anyone tries to use the old

0:38:59.640 --> 0:39:02.759
<v Speaker 1>certific of get, then an operating system like Windows can

0:39:02.800 --> 0:39:05.960
<v Speaker 1>say wait a minute, that certificate is out of date. Uh,

0:39:06.000 --> 0:39:08.480
<v Speaker 1>I'm going to alert the user because that could be

0:39:08.520 --> 0:39:11.279
<v Speaker 1>an indication that someone had gotten a hold of an

0:39:11.280 --> 0:39:14.279
<v Speaker 1>old authentication certificate and they're trying to pass it off

0:39:14.320 --> 0:39:19.920
<v Speaker 1>as legitimate. So anytime a certificate expires, it's no longer

0:39:19.960 --> 0:39:24.719
<v Speaker 1>really useful for the case of malware distributors. So some

0:39:24.760 --> 0:39:30.319
<v Speaker 1>companies will hire out their certificates, like they'll create certificates,

0:39:30.440 --> 0:39:32.879
<v Speaker 1>and then other parties will come to them and say, hey,

0:39:33.239 --> 0:39:36.080
<v Speaker 1>we have created the software. We would like to say

0:39:36.080 --> 0:39:39.120
<v Speaker 1>that we created it in partnership with you, and in return,

0:39:39.520 --> 0:39:42.960
<v Speaker 1>you can put your authentication certificate on this software, which

0:39:43.000 --> 0:39:45.520
<v Speaker 1>will help us out a lot. Uh So some companies

0:39:45.520 --> 0:39:48.400
<v Speaker 1>will actually do that. Others are way more protective of

0:39:48.400 --> 0:39:51.600
<v Speaker 1>their digital certificates. No one was sure at this point

0:39:51.640 --> 0:39:56.120
<v Speaker 1>if Real Tech had their certificate stolen somehow, if if

0:39:56.120 --> 0:39:59.279
<v Speaker 1>the hackers had managed to uh illegally get hold of

0:39:59.320 --> 0:40:02.120
<v Speaker 1>this digit at all certificate, or if there had been

0:40:02.200 --> 0:40:05.480
<v Speaker 1>some other form of transaction involved, if fuel Ticket perhaps

0:40:06.239 --> 0:40:10.600
<v Speaker 1>licensed out essentially they're certificate. Circumstantial evidence suggested that it

0:40:10.760 --> 0:40:15.000
<v Speaker 1>was a stolen certificate. Looking at the malware code, it

0:40:15.040 --> 0:40:18.480
<v Speaker 1>appeared that one of the driver modules had its certification

0:40:18.640 --> 0:40:22.920
<v Speaker 1>signed to it just six minutes after the original code

0:40:22.920 --> 0:40:25.880
<v Speaker 1>had been compiled. This was found out by converting the

0:40:25.920 --> 0:40:29.120
<v Speaker 1>code into binary and then being very meticulous about looking

0:40:29.200 --> 0:40:32.239
<v Speaker 1>for the data for any sort of time stamp information. Now,

0:40:32.280 --> 0:40:35.440
<v Speaker 1>it is possible to fudge things like the date and

0:40:35.560 --> 0:40:42.319
<v Speaker 1>time of compiling, but that's not necessarily easy to do,

0:40:42.480 --> 0:40:45.360
<v Speaker 1>so you could say that the compiled dates not really

0:40:45.360 --> 0:40:48.480
<v Speaker 1>a smoking gun, but it does suggest that the certification

0:40:48.520 --> 0:40:51.440
<v Speaker 1>had been sticking around in the pocket of whomever had

0:40:51.440 --> 0:40:55.800
<v Speaker 1>been designing stucks net and then immediately slapped onto stucks

0:40:55.800 --> 0:40:58.520
<v Speaker 1>net once the code was compiled and ready to go. Now,

0:40:58.560 --> 0:41:00.279
<v Speaker 1>I've got a lot more to say in the first

0:41:00.320 --> 0:41:02.919
<v Speaker 1>episode about stuck s net, but before I continue, let's

0:41:02.960 --> 0:41:13.520
<v Speaker 1>take another quick break to thank our sponsor. Lawson would

0:41:13.520 --> 0:41:17.640
<v Speaker 1>reach out to both real Tech and Microsoft to alert

0:41:17.760 --> 0:41:21.800
<v Speaker 1>both companies of this vulnerability because it had that digital

0:41:21.840 --> 0:41:26.680
<v Speaker 1>certification from real Tech and it was affecting Microsoft based machines.

0:41:27.239 --> 0:41:30.240
<v Speaker 1>He had not figured out what the malware was actually

0:41:30.320 --> 0:41:34.160
<v Speaker 1>for yet that would be the payload. He was understanding

0:41:34.160 --> 0:41:37.200
<v Speaker 1>a little bit of how the malware would infect machines,

0:41:38.000 --> 0:41:40.000
<v Speaker 1>but he didn't know what it was supposed to do.

0:41:41.000 --> 0:41:45.040
<v Speaker 1>He didn't know it could potentially infect millions of computers

0:41:45.040 --> 0:41:48.359
<v Speaker 1>around the world because that digital certification gave it kind

0:41:48.400 --> 0:41:52.839
<v Speaker 1>of a v I P pass onto machines, and if

0:41:52.840 --> 0:41:55.560
<v Speaker 1>it was meant to steal information or cause mischief, he

0:41:55.600 --> 0:41:58.600
<v Speaker 1>wanted to nip that in the bud. One interesting tidbit

0:41:58.719 --> 0:42:01.160
<v Speaker 1>is whomever it des I in the malware have been

0:42:01.200 --> 0:42:02.960
<v Speaker 1>really careful to do it in such a way that

0:42:03.000 --> 0:42:07.239
<v Speaker 1>the major anti virus packages out there wouldn't suspect a thing.

0:42:07.680 --> 0:42:10.560
<v Speaker 1>It was compatible with all the major anti virus packages,

0:42:11.000 --> 0:42:14.799
<v Speaker 1>so most people wouldn't have any way of telling that

0:42:14.920 --> 0:42:19.040
<v Speaker 1>something hinky was going on. Clearly, the hackers who designed

0:42:19.080 --> 0:42:22.280
<v Speaker 1>this had worked with computers that had these anti virus

0:42:22.280 --> 0:42:25.360
<v Speaker 1>software packages installed on them to make sure that it

0:42:25.400 --> 0:42:29.759
<v Speaker 1>would slip under the radar. But Virus Block Ada was

0:42:30.200 --> 0:42:34.000
<v Speaker 1>a small operation, and it may have been able to

0:42:34.840 --> 0:42:37.880
<v Speaker 1>have this this incompatibility problem where it was causing the

0:42:37.920 --> 0:42:41.400
<v Speaker 1>computer to crash and reboot over and over again, simply

0:42:41.440 --> 0:42:45.160
<v Speaker 1>because the people who were designing the stux Net virus

0:42:45.360 --> 0:42:49.360
<v Speaker 1>had never really encountered this particular anti virus platform before,

0:42:49.400 --> 0:42:52.480
<v Speaker 1>and they weren't able to make sure that stux Net

0:42:52.640 --> 0:42:56.200
<v Speaker 1>would not be picked up by it, and so it

0:42:56.280 --> 0:43:00.760
<v Speaker 1>was a real enigma. Lawson couldn't even get the virus

0:43:00.840 --> 0:43:05.200
<v Speaker 1>to regularly replicate the problems he was seeing, so he

0:43:05.239 --> 0:43:08.880
<v Speaker 1>wasn't really certain what was happening. Uh. It was largely

0:43:08.920 --> 0:43:11.920
<v Speaker 1>a matter of luck that this happened at all and

0:43:12.000 --> 0:43:14.919
<v Speaker 1>brought people's attention to it. After two weeks without hearing

0:43:14.960 --> 0:43:18.840
<v Speaker 1>anything back from Microsoft Real Tech Who, Lawson posted information

0:43:18.880 --> 0:43:22.280
<v Speaker 1>about what he had found both to his company's website

0:43:22.560 --> 0:43:27.080
<v Speaker 1>and on an English speaking cyber security forum. He did

0:43:27.120 --> 0:43:29.719
<v Speaker 1>that on July twelve, two thousand and ten. That was

0:43:29.760 --> 0:43:33.320
<v Speaker 1>the same day that the Finnish security firm was talking

0:43:33.320 --> 0:43:36.960
<v Speaker 1>about how digital certificates from trusted sources could become a

0:43:37.040 --> 0:43:40.839
<v Speaker 1>vector for malware on July. Just a few days later,

0:43:41.160 --> 0:43:45.320
<v Speaker 1>security researcher and tech journalist Brian Krebs posted about the malware,

0:43:45.680 --> 0:43:48.280
<v Speaker 1>and it quickly became the talk of the cyber security

0:43:48.360 --> 0:43:52.160
<v Speaker 1>sphere at that point. Microsoft is the company that actually

0:43:52.200 --> 0:43:55.520
<v Speaker 1>gave the malware its name, and the company named it

0:43:55.600 --> 0:43:59.000
<v Speaker 1>that by combining some elements of code that were found

0:43:59.320 --> 0:44:02.440
<v Speaker 1>in the virus itself, including the file name for one

0:44:02.480 --> 0:44:05.920
<v Speaker 1>of the driver modules, which was m R x net

0:44:06.320 --> 0:44:10.520
<v Speaker 1>dot sis. At this time, virus Block Ada had updated

0:44:10.520 --> 0:44:14.560
<v Speaker 1>its anti virus software to sniff out stucks net. It

0:44:14.600 --> 0:44:18.120
<v Speaker 1>was looking for any sort of markers that would identify

0:44:18.239 --> 0:44:21.120
<v Speaker 1>stucks net, and the company discovered that the malicious code

0:44:21.120 --> 0:44:25.200
<v Speaker 1>had infected many computers across the Middle East. In particular,

0:44:25.400 --> 0:44:30.480
<v Speaker 1>on July, a Slovakian security firm called e Set e

0:44:30.800 --> 0:44:34.600
<v Speaker 1>s Et discovered a new driver module that seemed to

0:44:34.600 --> 0:44:36.719
<v Speaker 1>be very similar to the stocks net one that was

0:44:36.760 --> 0:44:40.279
<v Speaker 1>previously identified. This one had a digital certificate from a

0:44:40.320 --> 0:44:44.879
<v Speaker 1>different company called j Micron Technology, which was also from

0:44:44.920 --> 0:44:47.520
<v Speaker 1>Taiwan and in fact was located just a couple of

0:44:47.520 --> 0:44:51.799
<v Speaker 1>blocks away from Real Tech. The malware appeared otherwise to

0:44:51.840 --> 0:44:55.120
<v Speaker 1>be pretty much the same as its predecessor, So why

0:44:55.120 --> 0:44:58.239
<v Speaker 1>did it have a different digital certificate? Well, part of

0:44:58.280 --> 0:45:00.399
<v Speaker 1>the reason was that the real tex orti get had

0:45:00.480 --> 0:45:03.520
<v Speaker 1>expired in June two thousand and ten, so you couldn't

0:45:03.520 --> 0:45:06.200
<v Speaker 1>infect new computers using it. Windows would not allow a

0:45:06.320 --> 0:45:09.160
<v Speaker 1>driver with an expired digital certificate to install itself on

0:45:09.160 --> 0:45:13.440
<v Speaker 1>a computer without notifying the user. The new legitimate digital

0:45:13.480 --> 0:45:17.239
<v Speaker 1>certificate from j Micron Technology could sidestep that problem. The

0:45:17.280 --> 0:45:21.400
<v Speaker 1>new attack may have launched on July four, just two

0:45:21.520 --> 0:45:26.279
<v Speaker 1>days after Ulison had made his findings public, and it's

0:45:26.320 --> 0:45:30.640
<v Speaker 1>possible that the malware was released hurriedly in reaction to

0:45:30.880 --> 0:45:33.680
<v Speaker 1>the announcement, and it what might have been an attempt

0:45:33.800 --> 0:45:37.279
<v Speaker 1>to infect as many computers as possible before Microsoft could

0:45:37.280 --> 0:45:41.319
<v Speaker 1>patch the vulnerability. There's some evidence to support this hypothesis,

0:45:41.400 --> 0:45:43.799
<v Speaker 1>as the code in this release was a little less

0:45:43.840 --> 0:45:47.200
<v Speaker 1>buttoned down than the original attack had been back in

0:45:47.440 --> 0:45:49.880
<v Speaker 1>two thousand nine. And by some evidence, I mean there

0:45:49.880 --> 0:45:53.200
<v Speaker 1>were some sloppy mistakes. The digital certificate contained a block

0:45:53.239 --> 0:45:57.040
<v Speaker 1>of information about the company that issued the certificate, kind

0:45:57.040 --> 0:45:59.600
<v Speaker 1>of like a you know, a little bit of information

0:45:59.680 --> 0:46:03.920
<v Speaker 1>about J Mikron, and that bit of information included a

0:46:04.080 --> 0:46:06.799
<v Speaker 1>u r L to a J Mikron website, except there

0:46:06.840 --> 0:46:09.759
<v Speaker 1>was a typo in the u r L, and so

0:46:09.840 --> 0:46:13.399
<v Speaker 1>any attempt to visit that particular address would return a

0:46:13.480 --> 0:46:17.200
<v Speaker 1>Server not Found error. Uh. If anyone had tried it,

0:46:17.239 --> 0:46:19.280
<v Speaker 1>they might have said, well, this is kind of strange

0:46:19.360 --> 0:46:22.960
<v Speaker 1>that a company would issue a digital certificate and yet

0:46:23.000 --> 0:46:25.080
<v Speaker 1>have the wrong u r L in there. You would

0:46:25.080 --> 0:46:27.520
<v Speaker 1>think that for something that important they would make absolutely

0:46:27.560 --> 0:46:30.960
<v Speaker 1>certain they had correct information included so that was one

0:46:31.000 --> 0:46:34.360
<v Speaker 1>red flag. There were also fields within the certificate that

0:46:34.440 --> 0:46:38.560
<v Speaker 1>had the value change me written in them instead of

0:46:38.560 --> 0:46:41.320
<v Speaker 1>whatever information should have been there. Now clearly that was

0:46:41.360 --> 0:46:43.799
<v Speaker 1>a note written by a hacker to his or her

0:46:43.880 --> 0:46:47.440
<v Speaker 1>team as a placeholder, you know, don't let this go

0:46:47.520 --> 0:46:51.360
<v Speaker 1>out before you change it, but it was never actually

0:46:51.360 --> 0:46:54.720
<v Speaker 1>replaced or changed. Those elements suggest the malware was rushed

0:46:54.719 --> 0:46:57.719
<v Speaker 1>out the door ahead of plan. Researchers later determined that

0:46:57.760 --> 0:47:01.799
<v Speaker 1>the original attacks happened in three waves. June of two

0:47:01.840 --> 0:47:04.400
<v Speaker 1>thousand nine was the first one and used an auto

0:47:04.520 --> 0:47:09.600
<v Speaker 1>run attack. March and April were the second two attacks,

0:47:10.080 --> 0:47:13.680
<v Speaker 1>and then after that you end up with these approaches

0:47:13.760 --> 0:47:17.400
<v Speaker 1>that we're using a different digital certificate. It didn't appear

0:47:17.440 --> 0:47:20.600
<v Speaker 1>to have anything to do with identity theft, didn't have

0:47:20.640 --> 0:47:23.680
<v Speaker 1>anything to do with creating a botan net, So why

0:47:23.680 --> 0:47:27.400
<v Speaker 1>would you design code that can infect millions of machines

0:47:28.120 --> 0:47:31.480
<v Speaker 1>but it didn't actually cause harm to the host computers

0:47:31.840 --> 0:47:36.360
<v Speaker 1>or do anything else of any real consequence. Frank Baldwin,

0:47:36.560 --> 0:47:40.680
<v Speaker 1>a cybersecurity expert in Germany, discovered the first clues as

0:47:40.719 --> 0:47:45.040
<v Speaker 1>two stucks nets purpose. Baldwin had analyzed the code and

0:47:45.080 --> 0:47:48.160
<v Speaker 1>noticed that appeared to have been designed to target computers

0:47:48.360 --> 0:47:51.080
<v Speaker 1>that had a particular type of software on it. That

0:47:51.200 --> 0:47:55.279
<v Speaker 1>software came from the German company Siemens that I mentioned earlier. Now,

0:47:55.280 --> 0:47:58.759
<v Speaker 1>they make lots of different stuff, including software for other

0:47:58.800 --> 0:48:02.520
<v Speaker 1>businesses and particular software, or to be more specific, the

0:48:02.680 --> 0:48:07.040
<v Speaker 1>two programs that this virus was searching for. Whenever it

0:48:07.040 --> 0:48:09.080
<v Speaker 1>would infect a computer, it would look to see if

0:48:09.520 --> 0:48:13.040
<v Speaker 1>one or both of these programs was installed. Also on

0:48:13.040 --> 0:48:17.040
<v Speaker 1>that computer, there were for industrial control systems. It's the

0:48:17.080 --> 0:48:19.880
<v Speaker 1>sort of thing you would find in a manufacturing facility,

0:48:20.120 --> 0:48:23.520
<v Speaker 1>so again like the controllers for things like valves or

0:48:23.560 --> 0:48:28.600
<v Speaker 1>conveyor belts or other simple interconnected systems. Now, Baldwin's hypothesis

0:48:29.280 --> 0:48:32.400
<v Speaker 1>was that the malware was a type of industrial espionage.

0:48:32.640 --> 0:48:35.319
<v Speaker 1>He thought perhaps a company had created this malware in

0:48:35.360 --> 0:48:38.719
<v Speaker 1>an attempt to spy on competitors and learn how they

0:48:38.760 --> 0:48:42.880
<v Speaker 1>operate in an effort to gain a market advantage over them.

0:48:42.960 --> 0:48:47.120
<v Speaker 1>That wasn't exactly the right track, but at least showed

0:48:47.160 --> 0:48:51.000
<v Speaker 1>that this malware was meant for a very specific reason.

0:48:51.640 --> 0:48:54.320
<v Speaker 1>What that reason was I've kind of alluded to already,

0:48:54.360 --> 0:48:56.480
<v Speaker 1>but we're going to dive into more of that in

0:48:56.520 --> 0:49:00.560
<v Speaker 1>our next episode to really look at how ducks Net

0:49:00.920 --> 0:49:06.680
<v Speaker 1>unraveled and what were the motivations behind it, who was responsible,

0:49:07.080 --> 0:49:10.359
<v Speaker 1>and what was the fallout from this stuff. Uh, there's

0:49:10.400 --> 0:49:13.319
<v Speaker 1>no pun in that there was no nuclear fallout. I

0:49:13.320 --> 0:49:15.399
<v Speaker 1>want to be clear about that, because otherwise this would

0:49:15.440 --> 0:49:19.800
<v Speaker 1>be a very dark series of episodes. As it stands,

0:49:19.840 --> 0:49:23.320
<v Speaker 1>it's still pretty scary because we're talking about cyber warfare

0:49:23.360 --> 0:49:30.000
<v Speaker 1>at this point, using computers to create real world physical effects,

0:49:30.880 --> 0:49:33.520
<v Speaker 1>which is pretty phenomenal. Up to this point, most people

0:49:33.560 --> 0:49:36.520
<v Speaker 1>thought of that as being just theoretical, that computers could

0:49:36.520 --> 0:49:39.720
<v Speaker 1>do a lot of damage to data and could create

0:49:39.760 --> 0:49:44.360
<v Speaker 1>a nuisance, but couldn't necessarily cause physical damage to the

0:49:44.400 --> 0:49:48.480
<v Speaker 1>real world around us. Stocks Net proved we shouldn't be

0:49:48.520 --> 0:49:50.920
<v Speaker 1>so sure about that again. I'll talk about that more

0:49:50.920 --> 0:49:53.600
<v Speaker 1>in our next episode. If you guys have suggestions for

0:49:53.840 --> 0:49:56.879
<v Speaker 1>tech topics I should cover in the future, maybe it's

0:49:56.880 --> 0:49:59.680
<v Speaker 1>a company, maybe it's a specific technology, maybe it's a

0:49:59.760 --> 0:50:02.480
<v Speaker 1>per soon in tech who you think I should profile,

0:50:03.040 --> 0:50:05.279
<v Speaker 1>let me know. Or if there's someone you think I

0:50:05.280 --> 0:50:08.160
<v Speaker 1>should interview or have on as a guest co host,

0:50:08.440 --> 0:50:10.279
<v Speaker 1>let me know that as well. You can get in

0:50:10.320 --> 0:50:12.959
<v Speaker 1>touch with me through email. The address for the show

0:50:13.120 --> 0:50:16.040
<v Speaker 1>is tech stuff at how stuff works dot com, or

0:50:16.120 --> 0:50:18.240
<v Speaker 1>draw me a line on Facebook or Twitter. The handle

0:50:18.280 --> 0:50:21.680
<v Speaker 1>for both of those is tech stuff hs W. Follow

0:50:21.800 --> 0:50:24.920
<v Speaker 1>us on Instagram, and of course you can watch me

0:50:25.000 --> 0:50:29.520
<v Speaker 1>record this show live at twitch dot tv slash tech stuff.

0:50:29.640 --> 0:50:32.960
<v Speaker 1>I typically record on Wednesdays and Friday's. There's a chat

0:50:33.040 --> 0:50:35.240
<v Speaker 1>room there. You can join in on the merry band

0:50:35.400 --> 0:50:40.960
<v Speaker 1>and have fund high spirited conversation about that weird thing

0:50:41.040 --> 0:50:43.040
<v Speaker 1>I just said and had to go back and fix

0:50:43.160 --> 0:50:46.800
<v Speaker 1>so that the podcast listeners will never know, but you'll

0:50:46.840 --> 0:50:50.759
<v Speaker 1>know because you're pretty darn cool. Well that's it for

0:50:50.840 --> 0:50:54.400
<v Speaker 1>me for now. I'll talk to you again really soon

0:51:00.120 --> 0:51:02.520
<v Speaker 1>for more on this and thousands of other topics. Is

0:51:02.520 --> 0:51:13.160
<v Speaker 1>that how stuff works dot com m