跟讀練習: 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 - 通過影片學習英語口語

選擇練習模式

下載應用

C 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

Did Anthropic just save its $1 trillion IPO?

Docker in 100 Seconds

The last real programmers are dying out...

The plan to break apart Google... RIP Chrome

When open-sourcing your code goes wrong...

Google’s AI endgame is here… everything you missed at I/O 2026

OpenAI’s new browser feels familiar…

The most interesting "hack" in history...

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

Firefox and Tor hit with 9.8 critical level exploit

C++ in 100 Seconds

.NET in 100 Seconds

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

Linux in 100 Seconds

Did Google just dethrone OpenAI and Anthropic?

VS Code in 100 Seconds

Linux got wrecked by backdoor attack

Did the AI bubble just pop?

Oligarchy is worse than you think

PirateSoftware is right, this needs to stop

STOP Running Code On Your Computer

SANS Stormcast Wednesday, November 11th, 2026: Microsoft Patch Tuesday Outlook Spoofing (CVE-20…

Did Anthropic Kill Git?

The Man Who Stole MySpace | Samy

We Let $200 GPT-Pro Think for 7 Days on Unsolved Math

I Tested The Viral Reverse Engineering Repo

12 Things That Could Destroy Earth

KSI Accidentally Exposes His Crypto Scams