跟读练习: The worst week in cybersecurity history... so far - 通过视频学习英语口语

选择练习模式

每种模式都会打开全屏练习室。

73 句

如果句子过短或过长，请点击 Edit 进行调整。

Last week, while you were busy researching how to buy emergency rice and beans in bulk,

a group of guys who technically aren't supposed to have internet access pulled off the largest theft in human history.

A code editor owned by a rocket company spent 11 hours letting anyone SSH into your laptop,

a prediction market got robbed in the middle of investigating its own customers for treason, and Anthropic showed that an unreleased

Cloud model could get root on any unpatched

Linux server just by sending it TCP packets.

In today's video, we'll break down just another Thursday in this godforsaken hellhole we're trapped in.

It is November 3rd, 2026, and we're watching the Code Report.

You know, I would love nothing more than to just talk about the latest JavaScript framework, but here we are again.

This time, it started last Thursday in the middle of the night when Cursor shipped a new official CloudCode extension.

Unfortunately, they shipped it without actually knowing they shipped it.

The extension would scan your machine for any keys or tokens it could find,

and then set up a backdoor for attackers to come in later and steal them.

It was only up for about 11 hours, but that was still long enough for around 5 ,000 people to install it.

Thankfully, the backdoor required admin rights, which most people don't give to their text editor, so the blast radius was pretty limited.

Meanwhile, around that same time, users on Polymarket started noticing that their funds were being drained simply by logging into the website.

Now, this isn't that unusual for Polymarket users, but what was unusual was this time it wasn't their fault.

It turns out a script from a company called DebugBear

that Polymarket uses for performance monitoring was hijacked to sell all

your current positions before wiring the proceeds to a hard -coded wallet.

The hackers ended up getting over $2 million worth of funds before Polymarket pulled the script, which seems like a lot until you realize

it's just a small price to pay on the road to destroying the lives of millions of young men across the world.

Thankfully for Polymarket, the news didn't last long because just a few hours later,

people started noticing something was up with Binance and it was way worse.

In about 20 minutes, $6 .3 billion with a B worth of crypto across 10 different blockchains left Binance's hot wallets,

which makes this the biggest theft in recorded history.

According to Binance, a DevOps laptop was compromised, which allowed the attackers to submit withdrawal requests, then Binance's own system signed them.

The next day, the FBI came out and said they believed that the North Korean group

Trader Trader was behind the attack which was the same group that stole 1 .5 billion from Bybit last year.

The good news is that if you had money on Binance is

that it stopped being your problem pretty quickly since crypto isn't actually decentralized.

Tether and Circle froze about $3 billion of the stolen stablecoins within an hour,

and then Binance froze all withdrawals and spent the weekend refilling its wallets out of its own treasury and insurance funds.

By Sunday, withdrawals were back on, and yesterday they posted proof of reserves showing everyone's balance was fully backed again,

to which the users responded by kindly withdrawing $3 .6 billion from Binance anyway.

And that wasn't even the worst part of the week.

Back in early October, a Linux kernel maintainer named Eric Dumizet pushed a simple two -line fix

that delayed freeing some memory until the kernel is sure nothing is still reading it.

At the time, it didn't seem like a big deal

and nobody really paid attention to it until a few weeks later

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.

It turns out that since 2016, every Linux kernel has had a bug in the code that handles new TCP connections.

The way it works is every connection starts with the client sending a hello packet and the server sending one back.

Normally, that first packet is pretty uninteresting, but you're allowed to attach a few extra options to it

if you want the kernel to save those so it can use them when it builds its reply.

The problem is that if the client sends the same hello twice at just the right moment,

the two parts of the kernel end up working on the same connection at once,

and one of them can free that saved memory while the other one is still reading it.

So the server ends up building its reply out of memory that's already been freed,

which means whatever else got written there in the meantime ends up in the reply, and if an attacker controls what that is,

they can control what the kernel does next.

Now getting that timing right is pretty tricky, which is why

Red Hat initially rated it as a moderate 5 .9, and figured the worst case scenario was that the kernel would just crash,

because if the exploit only works in one in a million tries,

it's basically safe as long as the person trying it gets bored and runs out of money.

The problem is that world no longer exists, which is exactly what Anthropic proved on October 27th

when its red team published a post saying they handed the bug to an unreleased Claude model, and in about 48 minutes,

the model had hit the timing enough times to get the server to leak a kernel memory address back to it.

And just five minutes after that, it was able to start running commands as root.

Debian and Oracle had patched kernels out within one day of the CVE, Red Hat took another two weeks to decide it was serious,

and finally shipped fixes over the weekend.

And Ubuntu still doesn't have one.

But at least you can protect your own codebase with CodeRabbit, the sponsor of today's video.

They got tired of seeing me make videos about new exploits hitting the timeline every week like this,

so they just launched CodeRabbit Secure to provide continuous code security that's powered by actual reasoning instead of brittle regex rules.

Their security agents are designed to think like an attacker.

in order to hunt for real vulnerabilities across your entire codebase.

Then it prioritizes actual risks based on reachability, exploitability, and blast radius.

And it explains the problem to you in plain English, and suggests a fix you can approve in Merge from the diff.

The CodeRabbit Secure reviews every PR before

Merge, and you can also schedule deep scans across your full codebase to protect your backdoor 24 -7.

Start with a free 14 -day trial at the link below, no credit card required.

This has been The Code Report, thanks for watching, and I will see you in the next one.

下载应用

流利口语所需的一切

AI 发音评分逐句打分

音标练习掌握每个音

词汇学习建立你的词库

词汇游戏边玩边学

扫码

Download on theApp Store Get it onGoogle Play

同频道

FOR YOU

本课的词汇与口语要点

这节口语课以视频“The worst week in cybersecurity history... so far”为素材。视频中反复出现的词有：kernel, Binance, Polymarket, code。这段视频共有 73 个句子、1151 个单词可供跟读。讲话部分时长为 5:30。说话人语速较快，每分钟约 209 个词，会出现较多连读和弱读。只有 79% 的单词属于英语最常用的 3,000 词，词汇难度较高。

视频中的重点词汇

视频中 15 个值得学习的单词，附发音和释义：

单词	发音	释义
kernel 名词	/ˈkɝ.nəl/	核心
server 名词	/ˈsɝvɚ/	服務器 /服务器, 伺服器
steal 动词	/stiːl/	偷, 盜 /盗
wallet 名词	/ˈwɑl.ət/	錢包 /钱包, 皮夾 /皮夹
withdrawal 名词	/wɪðˈdɹɔ(ə)l/	退出, 撤退
packet 名词	/ˈpæk.ɪt/	包, 小包
unusual 形容词	/ʌnˈjuːʒ(u)əl/	稀有
script 名词	/skɹɪpt/	文章
blast 名词	/blæst/	疾風 /疾风
laptop 名词	/ˈlæp.tɑp/	手提電腦 /手提电脑, 手提計算機 /手提计算机
theft 名词	/θɛft/	盜竊 /盗窃
freeze 动词	/ˈfɹiːz/	凍結 /冻结, 凍 /冻
radius 名词	/ˈɹeɪ.di.əs/	橈骨 /桡骨
exploit 名词	/ˈɛksplɔɪt/	功勛 /功勋, 勛績 /勋绩
meanwhile 副词	/ˈmiːnwaɪl/	同時 /同时

视频中出现的短语动词

单词	发音	释义
end up 动词		到达
turn out 动词		原來 /原来
break down 动词		壞了 /坏了, 出故障
come out 动词	/ˌkʌm ˈaʊt/	出, 出來 /出来

视频中的语法

说话人最常用的结构，并附上视频中的原话：

结构	视频中的用法
被动语态 be + 过去分词 — 强调发生了什么，而不是谁做的	being drained · was hijacked · was compromised
定语从句 who / which + 从句 — 补充说明人或事物	guys who technically · attack which was · scale, which is
现在完成时 have/has + 过去分词 — 过去发生但与现在仍有关联的事	has had · that's already been freed · has been

需要注意的发音

说话人用了 13 次缩略和弱读形式，例如 didn't, isn't, wasn't。请按听到的简短形式来说。

“th” 音: withdrawal /wɪðˈdɹɔ(ə)l/, theft /θɛft/, withdraw /wɪðˈdɹɔ/, tether /ˈtɛðəɹ/
“sh” 和 “zh” 音: extension /ɪkˈstɛnʃən/, unusual /ʌnˈjuːʒ(u)əl/, treasury /ˈtɹɛʒ.ɚ.i/, prediction /pɹɪˈdɪkʃən/
长单词——注意重音位置: 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/

中文母语者容易读错的音：

/v/ — 不要读成 /w/，上齿轻触下唇: server /ˈsɝvɚ/, investigate /ɪnˈvɛs.tə.ɡeɪt/, approve /əˈpɹuːv/, vulnerability /ˌvʌln(ə)ɹəˈbɪlɪti/
词尾辅音 — 要读清楚，后面不要加元音: wallet /ˈwɑl.ət/, packet /ˈpæk.ɪt/, script /skɹɪpt/, blast /blæst/, laptop /ˈlæp.tɑp/
/r/ 和 /l/ 的区别: withdrawal /wɪðˈdɹɔ(ə)l/, vulnerability /ˌvʌln(ə)ɹəˈbɪlɪti/, brittle /ˈbɹɪtəl/, decentralize /diːˈsɛntɹəlaɪz/, refill /ˈɹiː.fɪl/

如何用这段视频练习

先完整听一遍视频，不要开口，记下不认识的单词。
先用 0.75 倍速逐句跟读，熟练之后再回到正常速度。
录下自己的声音并与原声对比，特别注意 kernel, server, steal 这类单词。

什么是跟读法？

跟读法 (Shadowing) 是一种有科学依据的语言学习技巧，最初开发用于专业口译员的培训，并由多语言者Alexander Arguelles博士普及。这个方法简单而强大：您在听英语母语原声的同时立即大声重复——就像是一个延迟1-2秒紧跟说话者的影子。与被动听力或语法练习不同，跟读法强迫您的大脑和口腔肌肉同时处理并模仿真实的讲话模式。研究表明它能显着提高发音准确性，语调，节奏，连读，听力理解和口语流利度——使其成为雅思口语备考和真实英语交流最有效的方法之一。

影子跟读法: 阅读完整分步指南 →

跟读练习: The worst week in cybersecurity history... so far - 通过视频学习英语口语

选择练习模式

下载应用

PostgreSQL in 100 Seconds

React Native in 100 Seconds

Every app on Earth is now open source... whether it likes it or not

Brainf**k in 100 Seconds

OpenAI’s lead engineer was secretly a spy...

Mind-bending new programming language for GPUs just dropped...

China just dropped a new frontier model... and nobody can explain how

The last real programmers are dying out...

Did the AI bubble just pop?

Docker in 100 Seconds

The plan to break apart Google... RIP Chrome

OpenAI’s new browser feels familiar…

Angular in 100 Seconds

The most interesting "hack" in history...

Tragic mistake... Anthropic leaks Claude’s source code

Firefox and Tor hit with 9.8 critical level exploit

5 open source tools that replaced my $320/mo AI stack...

C++ in 100 Seconds

Linux in 100 Seconds

Did Google just dethrone OpenAI and Anthropic?

STOP Running Code On Your Computer

They JUST Accidentally Revealed the Truth: The AI Bubble

Did Anthropic Kill Git?

Pavel Durov | Communication Technology and the Struggle for Freedom

The Anatomy of Fraud

The Man Who Stole MySpace | Samy

It’s not just you

How I deploy serverless containers for free

NotPetya Attack

I read Anthropic's 92-page risk factor document, so you don't have to | Explainer