WEBVTT

1
00:00:06.206 --> 00:00:08.108
We interrupt our regularly scheduled

2
00:00:08.108 --> 00:00:10.477
programming for this breaking news.

3
00:00:10.477 --> 00:00:13.546
Whitley, the international telecommunications firm

4
00:00:13.546 --> 00:00:16.950
has announced that it has fallen victim to a cyber attack,

5
00:00:16.950 --> 00:00:19.219
forcing it to shut down operations and disrupting

6
00:00:19.219 --> 00:00:22.222
corporate communications all over the globe.

7
00:00:22.222 --> 00:00:24.157
Our business reporter, Laura Brown is here

8
00:00:24.157 --> 00:00:25.458
to give us an update.

9
00:00:25.458 --> 00:00:26.693
Over to you, Laura.

10
00:00:26.693 --> 00:00:27.894
Thank you, John.

11
00:00:27.894 --> 00:00:29.796
We’ve received a statement from Whitley's

12
00:00:29.796 --> 00:00:32.565
Chief Information Officer, Bob Smith.

13
00:00:32.565 --> 00:00:34.734
A massive DDoS ransomware attack

14
00:00:34.734 --> 00:00:37.170
with UDP floodpower between four-hundred

15
00:00:37.170 --> 00:00:39.339
and five-hundred gigabits-per-second

16
00:00:39.339 --> 00:00:42.609
has completely shut down the company’s computer networks.

17
00:00:42.609 --> 00:00:46.479
The famous hacker, LeetHacker156b has claimed

18
00:00:46.479 --> 00:00:50.050
responsibility and is demanding a half million dollars

19
00:00:50.050 --> 00:00:53.219
payable in Bitcoin to restore operations.

20
00:00:53.219 --> 00:00:56.227
This shut-down is disrupting Whitley's business all

21
00:00:56.228 --> 00:01:00.526
over the world, costing the company millions in revenue.

22
00:01:00.526 --> 00:01:02.813
Laura, is there any indication as to how

23
00:01:02.813 --> 00:01:04.885
such a massive security breach happened?

24
00:01:04.885 --> 00:01:08.768
Well John, there’s speculation that a global IoT botnet

25
00:01:08.768 --> 00:01:10.897
was used to disrupt service, but the

26
00:01:10.897 --> 00:01:13.996
incident response team is still investigating.

27
00:01:13.996 --> 00:01:16.776
Thank you, Laura. As news develops, we'll be

28
00:01:16.776 --> 00:01:19.801
bringing you live updates.

29
00:01:25.648 --> 00:01:29.736
So, a DDoS attack? IoT botnet?

30
00:01:29.736 --> 00:01:33.166
I have no idea. I just read the teleprompter.

31
00:01:33.166 --> 00:01:36.078
Those technical terms are totally over my head.

32
00:01:36.078 --> 00:01:40.589
Hey guys, we're still on the air!