Shadowing-Übung: The worst week in cybersecurity history... so far - Englisch Sprechen Lernen mit Video

Übungsmodus wählen

Jeder Modus öffnet einen Übungsraum im Vollbild.

73 Sätze
Wenn Sätze zu kurz oder zu lang sind, klicke auf Edit, um sie anzupassen.
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 herunterladen

Alles, was du zum fließenden Sprechen brauchst

KI-AussprachebewertungJeder Satz bewertet
IPA-TrainingJeden Laut meistern
WortschatzBaue deinen Wortschatz auf
VokabelspielSpielend lernen

Gleicher Kanal

FOR YOU

Empfohlenes Video

Wortschatz und Sprechhinweise zu dieser Lektion

Diese Sprechübung basiert auf dem Video „The worst week in cybersecurity history... so far“. Diese Wörter kommen am häufigsten vor: kernel, Binance, Polymarket, code. Dieses Video enthält 73 Sätze und 1151 Wörter zum Nachsprechen. Der gesprochene Teil dauert 5:30. Der Sprecher spricht schnell, etwa 209 Wörter pro Minute – rechne mit verbundenen und verkürzten Lauten. Nur 79 % der Wörter gehören zu den 3.000 häufigsten im Englischen, der Wortschatz ist also anspruchsvoll.

Wichtiger Wortschatz in diesem Video

15 lernenswerte Wörter aus dem Video, mit Aussprache und Bedeutung:

WortAusspracheBedeutung
kernel Substantiv/ˈkɝ.nəl/Kern
server Substantiv/ˈsɝvɚ/Server
attacker Substantiv/əˈtækɚ/Angreifer, Angreiferin
steal Verb/stiːl/stehlen, entwenden
wallet Substantiv/ˈwɑl.ət/Portemonnaie, Portmonee
withdrawal Substantiv/wɪðˈdɹɔ(ə)l/Entnahme, Abhebung
packet Substantiv/ˈpæk.ɪt/Päckchen, Packung
extension Substantiv/ɪkˈstɛnʃən/Ausdehnung, Erweiterung
unusual Adjektiv/ʌnˈjuːʒ(u)əl/ungewöhnlich, unüblich
script Substantiv/skɹɪpt/Skript, Skriptum
blast Substantiv/blæst/Windstoß
laptop Substantiv/ˈlæp.tɑp/Laptop, Klapprechner
theft Substantiv/θɛft/Diebstahl
freeze Verb/ˈfɹiːz/gefrieren
radius Substantiv/ˈɹeɪ.di.əs/Speiche, Radius

Phrasal Verbs, die du hören wirst

WortAusspracheBedeutung
end up Verbsich herausstellen, am Ende irgendwo / etwas sein
turn out Verbsich herausstellen als/dass, sich erweisen als
break down Verbversagen, den Geist aufgeben
come out Verb/ˌkʌm ˈaʊt/herauskommen
get over Verbüberwinden
pull off Verbabzupfen, wegziehen
set up Verb/ˌsɛt ˈʌp/aufbauen, für den Einsatz vorbereiten

Grammatik in diesem Video

Die Strukturen, die der Sprecher am häufigsten verwendet, mit den genauen Worten aus dem Video:

StrukturIm Video
Passiv be + Partizip Perfekt – wichtig ist, was geschieht, nicht wer es tutbeing drained · was hijacked · was compromised
Relativsätze who / which + Satz – eine Zusatzinformation über eine Person oder Sacheguys who technically · attack which was · scale, which is
Present Perfect have/has + Partizip Perfekt – eine vergangene Handlung, die jetzt noch wichtig isthas had · that's already been freed · has been

Aussprache, auf die du achten solltest

Der Sprecher verwendet 13 Kurzformen und abgeschwächte Formen, zum Beispiel didn't, isn't, wasn't. Sprich sie in der kurzen Form, so wie du sie hörst.

  • Die „th“-Laute: withdrawal /wɪðˈdɹɔ(ə)l/, theft /θɛft/, withdraw /wɪðˈdɹɔ/, tether /ˈtɛðəɹ/
  • Die Laute „sh“ und „zh“: extension /ɪkˈstɛnʃən/, unusual /ʌnˈjuːʒ(u)əl/, treasury /ˈtɹɛʒ.ɚ.i/, prediction /pɹɪˈdɪkʃən/
  • Lange Wörter – auf die Betonung achten: 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/

Laute, die Deutschsprachigen schwerfallen:

  • /w/ — mit runden Lippen, nicht wie das deutsche „w“ (/v/): wallet /ˈwɑl.ət/, withdrawal /wɪðˈdɹɔ(ə)l/, meanwhile /ˈmiːnwaɪl/, wire /ˈwaɪɚ/, framework /ˈfɹeɪm.wɜːk/
  • Stimmhafter Auslaut — /b/, /d/, /g/, /z/, /v/ am Wortende nicht verhärten: freeze /ˈfɹiːz/, cloud /ˈklaʊ̯d/, log /lɔɡ/, rob /ɹɑb/, proceed /pɹəˈsid/
  • /æ/ — offener als „ä“: attacker /əˈtækɚ/, packet /ˈpæk.ɪt/, blast /blæst/, laptop /ˈlæp.tɑp/, scan /skæn/

So übst du mit diesem Video

  1. Höre dir das ganze Video einmal an, ohne zu sprechen, und notiere die Wörter, die du nicht kennst.
  2. Beginne mit 0,75-facher Geschwindigkeit, sprich Satz für Satz nach und wechsle zur normalen Geschwindigkeit, sobald es leichtfällt.
  3. Nimm dich auf und vergleiche mit dem Original; achte dabei auf Wörter wie kernel, server, attacker.

Was ist die Shadowing-Technik?

Shadowing ist eine wissenschaftlich fundierte Sprachlerntechnik, die ursprünglich für die professionelle Dolmetscherausbildung entwickelt und durch den Polyglotten Dr. Alexander Arguelles populär gemacht wurde. Die Methode ist einfach aber wirkungsvoll: Du hörst englisches Audio von Muttersprachlern und wiederholst es sofort laut — wie ein Schatten, der dem Sprecher mit nur 1–2 Sekunden Verzögerung folgt. Anders als passives Hören oder Grammatikübungen zwingt Shadowing dein Gehirn und deine Mundmuskulatur, gleichzeitig echte Sprachmuster zu verarbeiten und zu reproduzieren. Studien zeigen, dass es Aussprachegenauigkeit, Intonation, Rhythmus, verbundene Sprache, Hörverständnis und Sprechflüssigkeit signifikant verbessert — was es zu einer der effektivsten Methoden für die IELTS Speaking-Vorbereitung und reale englische Kommunikation macht.

Shadowing-Technik: die vollständige Schritt-für-Schritt-Anleitung lesen →