Практика Shadowing: 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.

Скачать приложение

Всё для свободной речи

ИИ-оценка произношенияОценка каждой фразы

Практика IPAОсвойте каждый звук

СловарьСоберите свой словарный запас

Игра со словамиУчитесь играя

Сканировать QR

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% слов входят в 3000 самых частых слов английского языка, поэтому лексика сложная.

Ключевая лексика этого видео

15 слов из видео, которые стоит выучить, с произношением и значением:

Слово	Произношение	Значение
kernel существительное	/ˈkɝ.nəl/	суть, су́щность
server существительное	/ˈsɝvɚ/	се́рвер
attacker существительное	/əˈtækɚ/	напада́ющий, атаку́ющий
steal глагол	/stiːl/	красть, укра́сть
wallet существительное	/ˈwɑl.ət/	бума́жник, кошелёк
withdrawal существительное	/wɪðˈdɹɔ(ə)l/	сня́тие
packet существительное	/ˈpæk.ɪt/	паке́т, па́чка
extension существительное	/ɪkˈstɛnʃən/	расшире́ние, продле́ние
unusual прилагательное	/ʌnˈjuːʒ(u)əl/	необы́чный, необыкнове́нный
script существительное	/skɹɪpt/	скрипт, письмо́
blast существительное	/blæst/	поры́в ве́тра, поры́в
laptop существительное	/ˈlæp.tɑp/	но́утбук, ноутбу́к
theft существительное	/θɛft/	кра́жа, воровство́
freeze глагол	/ˈfɹiːz/	замерза́ть, замёрзнуть
scan глагол	/skæn/	разгля́дывать

Фразовые глаголы, которые вы услышите

Слово	Произношение	Значение
end up глагол		зака́нчиваться, зако́нчиться
turn out глагол		ока́зываться, оказа́ться
break down глагол		ломаться, сломаться
come out глагол	/ˌkʌm ˈaʊt/	выходи́ть, вы́йти
get over глагол		преодолева́ть, преодоле́ть
pull off глагол		оттащить, стянуть
set up глагол	/ˌsɛt ˈʌp/	устана́вливать, установи́ть

Грамматика в этом видео

Конструкции, которые говорящий использует чаще всего, с точными словами из видео:

Конструкция	В видео
Пассивный залог be + причастие прошедшего времени — важно, что происходит, а не кто это делает	being drained · was hijacked · was compromised
Придаточные определительные who / which + предложение — уточнение о человеке или предмете	guys who technically · attack which was · scale, which is
Present Perfect 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/

Звуки, трудные для русскоязычных:

/w/ — губы округлены, это не /v/: wallet /ˈwɑl.ət/, withdrawal /wɪðˈdɹɔ(ə)l/, meanwhile /ˈmiːnwaɪl/, wire /ˈwaɪɚ/, framework /ˈfɹeɪm.wɜːk/
/h/ — лёгкий выдох, а не русское «х»: hacker /hækəɹ/, hijack /ˈhaɪ.d͡ʒæk/
Звонкие согласные в конце слова — не оглушайте их: freeze /ˈfɹiːz/, cloud /ˈklaʊ̯d/, log /lɔɡ/, rob /ɹɑb/, proceed /pɹəˈsid/

Как заниматься с этим видео

Прослушайте всё видео один раз молча и выпишите незнакомые слова.
Начните со скорости 0,75×, повторяйте предложение за предложением и вернитесь к обычной скорости, когда станет легко.
Запишите себя и сравните с оригиналом, обращая внимание на такие слова, как kernel, server, attacker.

Что такое техника Shadowing?

Shadowing — это научно обоснованная техника изучения языка, изначально разработанная для подготовки профессиональных переводчиков и популяризированная полиглотом доктором Александром Аргуэльесом. Метод прост, но эффективен: вы слушаете аудио на английском от носителей языка и немедленно повторяете вслух — как тень, следующая за говорящим с задержкой в 1–2 секунды. В отличие от пассивного прослушивания или грамматических упражнений, Shadowing заставляет мозг и мышцы рта одновременно обрабатывать и воспроизводить реальные речевые паттерны. Исследования показывают, что это значительно улучшает точность произношения, интонацию, ритм, связную речь, понимание на слух и беглость речи — что делает его одним из самых эффективных методов для подготовки к IELTS Speaking и реального общения на английском.

Техника шедоуинга: читать полное пошаговое руководство →

Практика Shadowing: 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

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

Docker in 100 Seconds

The last real programmers are dying out...

The plan to break apart Google... RIP Chrome

Did the AI bubble just pop?

When open-sourcing your code goes wrong...

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

Oligarchy is worse than you think

So I tried Matt's skills...

THIS Is Where the Internet Lives

STOP Running Code On Your Computer

Did Anthropic Kill Git?

Here's what's REALLY Happening...

PirateSoftware is right, this needs to stop

The Man Who Stole MySpace | Samy

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

12 Things That Could Destroy Earth