Shadowing Practice: The worst week in cybersecurity history... so far - Learn English Speaking with Video

Choose a practice mode

Each mode opens a full-screen practice room.

73 sentences
If sentences are too short or too long, click Edit to adjust them.
1
Last week, while you were busy researching how to buy emergency rice and beans in bulk,
2
a group of guys who technically aren't supposed to have internet access pulled off the largest theft in human history.
3
A code editor owned by a rocket company spent 11 hours letting anyone SSH into your laptop,
4
a prediction market got robbed in the middle of investigating its own customers for treason, and Anthropic showed that an unreleased
5
Cloud model could get root on any unpatched
6
Linux server just by sending it TCP packets.
7
In today's video, we'll break down just another Thursday in this godforsaken hellhole we're trapped in.
8
It is November 3rd, 2026, and we're watching the Code Report.
9
You know, I would love nothing more than to just talk about the latest JavaScript framework, but here we are again.
10
This time, it started last Thursday in the middle of the night when Cursor shipped a new official CloudCode extension.
11
Unfortunately, they shipped it without actually knowing they shipped it.
12
The extension would scan your machine for any keys or tokens it could find,
13
and then set up a backdoor for attackers to come in later and steal them.
14
It was only up for about 11 hours, but that was still long enough for around 5 ,000 people to install it.
15
Thankfully, the backdoor required admin rights, which most people don't give to their text editor, so the blast radius was pretty limited.
16
Meanwhile, around that same time, users on Polymarket started noticing that their funds were being drained simply by logging into the website.
17
Now, this isn't that unusual for Polymarket users, but what was unusual was this time it wasn't their fault.
18
It turns out a script from a company called DebugBear
19
that Polymarket uses for performance monitoring was hijacked to sell all
20
your current positions before wiring the proceeds to a hard -coded wallet.
21
The hackers ended up getting over $2 million worth of funds before Polymarket pulled the script, which seems like a lot until you realize
22
it's just a small price to pay on the road to destroying the lives of millions of young men across the world.
23
Thankfully for Polymarket, the news didn't last long because just a few hours later,
24
people started noticing something was up with Binance and it was way worse.
25
In about 20 minutes, $6 .3 billion with a B worth of crypto across 10 different blockchains left Binance's hot wallets,
26
which makes this the biggest theft in recorded history.
27
According to Binance, a DevOps laptop was compromised, which allowed the attackers to submit withdrawal requests, then Binance's own system signed them.
28
The next day, the FBI came out and said they believed that the North Korean group
29
Trader Trader was behind the attack which was the same group that stole 1 .5 billion from Bybit last year.
30
The good news is that if you had money on Binance is
31
that it stopped being your problem pretty quickly since crypto isn't actually decentralized.
32
Tether and Circle froze about $3 billion of the stolen stablecoins within an hour,
33
and then Binance froze all withdrawals and spent the weekend refilling its wallets out of its own treasury and insurance funds.
34
By Sunday, withdrawals were back on, and yesterday they posted proof of reserves showing everyone's balance was fully backed again,
35
to which the users responded by kindly withdrawing $3 .6 billion from Binance anyway.
36
And that wasn't even the worst part of the week.
37
Back in early October, a Linux kernel maintainer named Eric Dumizet pushed a simple two -line fix
38
that delayed freeing some memory until the kernel is sure nothing is still reading it.
39
At the time, it didn't seem like a big deal
40
and nobody really paid attention to it until a few weeks later
41
when it got a 9 .8 out of 10 on the CVSS scale, which is the industry's way of ranking how bad a security bug is.
42
It turns out that since 2016, every Linux kernel has had a bug in the code that handles new TCP connections.
43
The way it works is every connection starts with the client sending a hello packet and the server sending one back.
44
Normally, that first packet is pretty uninteresting, but you're allowed to attach a few extra options to it
45
if you want the kernel to save those so it can use them when it builds its reply.
46
The problem is that if the client sends the same hello twice at just the right moment,
47
the two parts of the kernel end up working on the same connection at once,
48
and one of them can free that saved memory while the other one is still reading it.
49
So the server ends up building its reply out of memory that's already been freed,
50
which means whatever else got written there in the meantime ends up in the reply, and if an attacker controls what that is,
51
they can control what the kernel does next.
52
Now getting that timing right is pretty tricky, which is why
53
Red Hat initially rated it as a moderate 5 .9, and figured the worst case scenario was that the kernel would just crash,
54
because if the exploit only works in one in a million tries,
55
it's basically safe as long as the person trying it gets bored and runs out of money.
56
The problem is that world no longer exists, which is exactly what Anthropic proved on October 27th
57
when its red team published a post saying they handed the bug to an unreleased Claude model, and in about 48 minutes,
58
the model had hit the timing enough times to get the server to leak a kernel memory address back to it.
59
And just five minutes after that, it was able to start running commands as root.
60
Debian and Oracle had patched kernels out within one day of the CVE, Red Hat took another two weeks to decide it was serious,
61
and finally shipped fixes over the weekend.
62
And Ubuntu still doesn't have one.
63
But at least you can protect your own codebase with CodeRabbit, the sponsor of today's video.
64
They got tired of seeing me make videos about new exploits hitting the timeline every week like this,
65
so they just launched CodeRabbit Secure to provide continuous code security that's powered by actual reasoning instead of brittle regex rules.
66
Their security agents are designed to think like an attacker.
67
in order to hunt for real vulnerabilities across your entire codebase.
68
Then it prioritizes actual risks based on reachability, exploitability, and blast radius.
69
And it explains the problem to you in plain English, and suggests a fix you can approve in Merge from the diff.
70
The CodeRabbit Secure reviews every PR before
71
Merge, and you can also schedule deep scans across your full codebase to protect your backdoor 24 -7.
72
Start with a free 14 -day trial at the link below, no credit card required.
73
This has been The Code Report, thanks for watching, and I will see you in the next one.

Download App

Everything you need to speak fluently

AI PronunciationScore every sentence
IPA PracticeMaster every sound
VocabularyBuild your word bank
Vocab GameLearn while playing

Same Channel

FOR YOU

Recommend Video

Vocabulary and speaking notes for this lesson

This speaking lesson is built on the video “The worst week in cybersecurity history... so far”. The speaker keeps coming back to these words: kernel, Binance, Polymarket, code. This video has 73 sentences and 1151 words to shadow. The speech runs for 5:30. The speaker talks fast, about 209 words per minute, so expect linked and reduced sounds. Only 79% of the words are among the 3,000 most common in English, so the vocabulary is demanding.

Key vocabulary in this video

15 words from the video worth learning, with pronunciation and meaning:

WordPronunciationMeaning
kernel noun/ˈkɝ.nəl/The core, center, or essence of an object or system.
server noun/ˈsɝvɚ/A program that provides services to other programs or devices, either in the same computer or over a computer network.
attacker noun/əˈtækɚ/Someone who attacks.
steal verb/stiːl/To take illegally, or without the owner's permission, something owned by someone else without intending to return it.
wallet noun/ˈwɑl.ət/A small case, often flat and often made of leather, for keeping money (especially paper money), credit cards, etc.
withdrawal noun/wɪðˈdɹɔ(ə)l/Receiving from someone's care what one has earlier entrusted to them. Usually refers to money.
packet noun/ˈpæk.ɪt/A small pack or package; a little bundle or parcel
extension noun/ɪkˈstɛnʃən/The act of extending; a stretching out; enlargement in length, breadth, or time; an increase.
unusual adjective/ʌnˈjuːʒ(u)əl/Not usual, out of the ordinary.
script noun/skɹɪpt/A writing; a written document.
blast noun/blæst/A violent gust of wind (in windy weather) or apparent wind (around a moving vehicle).
laptop noun/ˈlæp.tɑp/A laptop computer.
theft noun/θɛft/The act of stealing property.
freeze verb/ˈfɹiːz/Especially of a liquid, to become solid due to low temperature.
scan verb/skæn/To examine sequentially, carefully, or critically; to scrutinize; to behold closely.

Phrasal verbs you will hear

WordPronunciationMeaning
end up verbTo bring to a conclusion.
turn out verbTo end up; to result.
break down verbTo stop functioning.
come out verb/ˌkʌm ˈaʊt/To be discovered; to be revealed.
get over verbTo overcome.
pull off verbTo remove by pulling.
set up verb/ˌsɛt ˈʌp/To make ready for use.

Grammar in this video

The structures the speaker uses most, with the exact words from the video:

StructureIn the video
Passive voice be + past participle — the focus is on what happens, not who does itbeing drained · was hijacked · was compromised
Relative clauses who / which + clause — extra information about a person or thingguys who technically · attack which was · scale, which is
Present perfect have/has + past participle — a past action that still matters nowhas had · that's already been freed · has been

Pronunciation to watch

The speaker uses 13 contractions and reduced forms, such as didn't, isn't, wasn't. Say them the short way, as you hear them.

  • The “th” sounds: withdrawal /wɪðˈdɹɔ(ə)l/, theft /θɛft/, withdraw /wɪðˈdɹɔ/, tether /ˈtɛðəɹ/
  • The “sh” and “zh” sounds: extension /ɪkˈstɛnʃən/, unusual /ʌnˈjuːʒ(u)əl/, treasury /ˈtɹɛʒ.ɚ.i/, prediction /pɹɪˈdɪkʃən/
  • Long words — get the stress right: unusual /ʌnˈjuːʒ(u)əl/, investigate /ɪnˈvɛs.tə.ɡeɪt/, continuous /kənˈtɪn.juː.əs/, technically /ˈtɛk.nɪˌkəl.i/, vulnerability /ˌvʌln(ə)ɹəˈbɪlɪti/

How to practise with this video

  1. Listen to the whole video once without speaking and note the words you do not know.
  2. Start at 0.75× speed, shadow it sentence by sentence, then go back to normal speed once it feels easy.
  3. Record yourself and compare with the original, paying attention to words like kernel, server, attacker.

What is the Shadowing Technique?

Shadowing is a science-backed language learning technique originally developed for professional interpreter training and popularized by polyglot Dr. Alexander Arguelles. The method is simple but powerful: you listen to native English audio and immediately repeat it out loud — like a shadow following the speaker with just a 1–2 second delay. Unlike passive listening or grammar drills, shadowing forces your brain and mouth muscles to simultaneously process and reproduce real speech patterns. Research shows it significantly improves pronunciation accuracy, intonation, rhythm, connected speech, listening comprehension, and speaking fluency — making it one of the most effective methods for IELTS Speaking preparation and real-world English communication.

Shadowing technique: read the full step-by-step guide →