Shadowing Practice: The worst week in cybersecurity history... so far - Learn English Speaking with Video
Kies een oefenmodus
Elke modus opent een volledig scherm oefenruimte.
73 zinnen
Als zinnen te kort of te lang zijn, klik op Bewerken om ze aan te passen.
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.
App downloaden
Alles wat je nodig hebt om vloeiend te spreken
AI UitspraakScoor elke zin
IPA OefeningBeheers elk geluid
WoordenschatBouw je woordenschat op
WoordenspelLeren terwijl je speelt
Zelfde Kanaal
C11
PostgreSQL in 100 Seconds
American AccentDaily ConversationWorking Adults
C11
React Native in 100 Seconds
American AccentDaily ConversationUniversity Students
C13
Every app on Earth is now open source... whether it likes it or not
American AccentDaily ConversationWorking Adults
C14
Brainf**k in 100 Seconds
American AccentDaily ConversationUniversity Students
C12
Mind-bending new programming language for GPUs just dropped...
American AccentDaily ConversationUniversity Students
C130
Docker in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C12
The last real programmers are dying out...
American AccentDaily ConversationUniversity StudentsWorking Adults
C16
The plan to break apart Google... RIP Chrome
American AccentBusiness EnglishDaily ConversationUniversity Students
C11
Did the AI bubble just pop?
American AccentDaily ConversationUniversity StudentsWorking Adults
C19
When open-sourcing your code goes wrong...
American AccentBusiness EnglishUniversity StudentsWorking Adults
B23
OpenAI’s new browser feels familiar…
American AccentBusiness EnglishUniversity StudentsWorking Adults
C19
The most interesting "hack" in history...
American AccentBusiness EnglishUniversity StudentsWorking Adults
C15
Tragic mistake... Anthropic leaks Claude’s source code
American AccentBusiness EnglishUniversity StudentsWorking Adults
B23
Firefox and Tor hit with 9.8 critical level exploit
American AccentBusiness EnglishUniversity StudentsWorking Adults
C12
C++ in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C25
.NET in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C12
China just dropped a new frontier model... and nobody can explain how
American AccentDaily ConversationUniversity StudentsWorking Adults
B24
Linux in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C13
Did Google just dethrone OpenAI and Anthropic?
American AccentDaily ConversationUniversity StudentsWorking Adults
C116
VS Code in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
FOR YOU
Aanbevolen Video
C16
51 zinnen
Linux got wrecked by backdoor attack
American AccentDaily ConversationUniversity StudentsWorking Adults
C11
754 zinnen
Oligarchy is worse than you think
American AccentDaily ConversationUniversity StudentsWorking Adults
C1678 zinnen
So I tried Matt's skills...
American AccentDaily ConversationUniversity StudentsWorking Adults
B21
398 zinnen
THIS Is Where the Internet Lives
American AccentDaily ConversationUniversity StudentsWorking Adults
C13
173 zinnen
STOP Running Code On Your Computer
Daily ConversationUniversity StudentsWorking Adults
C11
65 zinnen
Did Anthropic Kill Git?
Daily ConversationUniversity StudentsWorking Adults
C13
444 zinnen
Here's what's REALLY Happening...
American AccentDaily ConversationWorking Adults
C11
292 zinnen
PirateSoftware is right, this needs to stop
American AccentDaily ConversationWorking Adults
B21
205 zinnen
The Man Who Stole MySpace | Samy
Daily ConversationUniversity StudentsWorking Adults
C12
182 zinnen
We Let $200 GPT-Pro Think for 7 Days on Unsolved Math
Daily ConversationUniversity StudentsWorking Adults
C12
169 zinnen
12 Things That Could Destroy Earth
Daily ConversationUniversity StudentsWorking Adults
Woordenschat en spreektips bij deze les
Deze spreekles is gebaseerd op de video “The worst week in cybersecurity history... so far”. Deze woorden komen het vaakst terug: kernel, Binance, Polymarket, code. Deze video bevat 73 zinnen en 1151 woorden om na te spreken. Het gesproken deel duurt 5:30. De spreker praat snel, ongeveer 209 woorden per minuut, dus reken op verbonden en ingeslikte klanken. Slechts 79% van de woorden hoort bij de 3.000 meest gebruikte Engelse woorden, dus de woordenschat is pittig.
Belangrijke woorden in deze video
15 woorden uit de video die het leren waard zijn, met uitspraak en betekenis:
| Woord | Uitspraak | Betekenis |
|---|---|---|
| kernel zelfstandig naamwoord | /ˈkɝ.nəl/ | graan |
| server zelfstandig naamwoord | /ˈsɝvɚ/ | server |
| attacker zelfstandig naamwoord | /əˈtækɚ/ | aanvaller |
| steal werkwoord | /stiːl/ | stelen, ontvreemden |
| wallet zelfstandig naamwoord | /ˈwɑl.ət/ | portemonnee, portefeuille |
| packet zelfstandig naamwoord | /ˈpæk.ɪt/ | pakket, pak |
| extension zelfstandig naamwoord | /ɪkˈstɛnʃən/ | uitbreiding, extensie |
| unusual bijvoeglijk naamwoord | /ʌnˈjuːʒ(u)əl/ | ongebruikelijk, ongewoon |
| script zelfstandig naamwoord | /skɹɪpt/ | geschrift |
| blast zelfstandig naamwoord | /blæst/ | windstoot, rukwind |
| laptop zelfstandig naamwoord | /ˈlæp.tɑp/ | laptop, notebook |
| theft zelfstandig naamwoord | /θɛft/ | diefstal, dieverij |
| freeze werkwoord | /ˈfɹiːz/ | bevriezen |
| scan werkwoord | /skæn/ | afspeuren |
| radius zelfstandig naamwoord | /ˈɹeɪ.di.əs/ | spaakbeen, radius |
Phrasal verbs die je zult horen
| Woord | Uitspraak | Betekenis |
|---|---|---|
| end up werkwoord | belanden, terechtkomen | |
| turn out werkwoord | uitvallen, resulteren | |
| break down werkwoord | stukgaan, kapot gaan | |
| come out werkwoord | /ˌkʌm ˈaʊt/ | uitkomen |
| set up werkwoord | /ˌsɛt ˈʌp/ | bereiden, voorbereiden |
Grammatica in deze video
De structuren die de spreker het meest gebruikt, met de exacte woorden uit de video:
| Structuur | In de video |
|---|---|
| Lijdende vorm be + voltooid deelwoord — het gaat om wat er gebeurt, niet om wie het doet | being drained · was hijacked · was compromised |
| Betrekkelijke bijzinnen who / which + zin — extra informatie over een persoon of ding | guys who technically · attack which was · scale, which is |
| Present perfect have/has + voltooid deelwoord — iets uit het verleden dat nu nog telt | has had · that's already been freed · has been |
Uitspraak om op te letten
De spreker gebruikt 13 samentrekkingen en verkorte vormen, zoals didn't, isn't, wasn't. Spreek ze kort uit, zoals je ze hoort.
- De “th”-klanken: withdrawal /wɪðˈdɹɔ(ə)l/, theft /θɛft/, withdraw /wɪðˈdɹɔ/, tether /ˈtɛðəɹ/
- De klanken “sh” en “zh”: extension /ɪkˈstɛnʃən/, unusual /ʌnˈjuːʒ(u)əl/, treasury /ˈtɹɛʒ.ɚ.i/, prediction /pɹɪˈdɪkʃən/
- Lange woorden — let op de klemtoon: 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/
Klanken die Nederlandstaligen lastig vinden:
- Stemhebbende eindmedeklinker — /b/, /d/, /g/, /z/, /v/ niet verscherpen: freeze /ˈfɹiːz/, cloud /ˈklaʊ̯d/, log /lɔɡ/, rob /ɹɑb/, proceed /pɹəˈsid/
- /æ/ — opener dan de Nederlandse “e”: attacker /əˈtækɚ/, packet /ˈpæk.ɪt/, blast /blæst/, laptop /ˈlæp.tɑp/, scan /skæn/
- /g/ — een harde plofklank, geen Nederlandse “g”: log /lɔɡ/, investigate /ɪnˈvɛs.tə.ɡeɪt/, godforsaken /ˌɡɒd.fə(ɹ)ˈseɪ.kɪn/
Zo oefen je met deze video
- Luister de hele video één keer zonder te spreken en noteer de woorden die je niet kent.
- Begin op 0,75× snelheid, spreek zin voor zin na en ga terug naar normale snelheid zodra het makkelijk gaat.
- Neem jezelf op en vergelijk met het origineel; let daarbij op woorden als kernel, server, attacker.
Wat is de Shadowing-techniek?
Shadowing is een wetenschappelijk onderbouwde taalleermethode die oorspronkelijk is ontwikkeld voor professionele tolkentraining en gepopulariseerd door polyglot Dr. Alexander Arguelles. De methode is eenvoudig maar krachtig: je luistert naar native Engelse audio en herhaalt het onmiddellijk hardop — als een schaduw die de spreker volgt met slechts 1–2 seconden vertraging. In tegenstelling tot passief luisteren of grammaticadrills, dwingt shadowing je hersenen en mondspieren om echte spraakpatronen tegelijkertijd te verwerken en te reproduceren. Onderzoek toont aan dat het de uitspraaknauwkeurigheid, intonatie, ritme, verbonden spraak, luisterbegrip en spreekvaardigheid aanzienlijk verbetert — waardoor het een van de meest effectieve methoden is voor IELTS Speaking-voorbereiding en echte Engelse communicatie.