शैडोइंग अभ्यास: 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 उच्चारण स्कोरहर वाक्य का स्कोर

IPA अभ्यासहर ध्वनि में महारत

शब्दावलीअपना शब्द भंडार बनाएँ

शब्द गेमखेलते हुए सीखें

QR स्कैन करें

Download on theApp Store Get it onGoogle Play

उसी चैनल से

FOR YOU

अनुशंसित वीडियो

173 वाक्य

STOP Running Code On Your Computer

Daily ConversationUniversity StudentsWorking Adults

389 वाक्य

They JUST Accidentally Revealed the Truth: The AI Bubble

Daily ConversationUniversity StudentsWorking Adults

65 वाक्य

Did Anthropic Kill Git?

Daily ConversationUniversity StudentsWorking Adults

266 वाक्य

Pavel Durov | Communication Technology and the Struggle for Freedom

Daily ConversationUniversity StudentsWorking Adults

118 वाक्य

The Anatomy of Fraud

Daily ConversationUniversity StudentsWorking Adults

205 वाक्य

The Man Who Stole MySpace | Samy

Daily ConversationUniversity StudentsWorking Adults

358 वाक्य

It’s not just you

Daily ConversationUniversity StudentsWorking Adults

78 वाक्य

How I deploy serverless containers for free

Daily ConversationUniversity StudentsWorking Adults

137 वाक्य

NotPetya Attack

Daily ConversationWorking Adults

37 वाक्य

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

Daily ConversationUniversity StudentsWorking Adults

इस पाठ की शब्दावली और बोलने के सुझाव

यह स्पीकिंग पाठ वीडियो “The worst week in cybersecurity history... so far” पर आधारित है। सबसे ज़्यादा दोहराए गए शब्द ये हैं: kernel, Binance, Polymarket, code। इस वीडियो में शैडोइंग के लिए 73 वाक्य और 1151 शब्द हैं। बोला गया हिस्सा 5:30 लंबा है। वक्ता तेज़ बोलता है, लगभग 209 शब्द प्रति मिनट, इसलिए जुड़ी हुई और कमज़ोर ध्वनियाँ ज़्यादा मिलेंगी। केवल 79% शब्द अंग्रेज़ी के 3,000 सबसे आम शब्दों में से हैं, इसलिए शब्दावली कठिन है।

इस वीडियो की मुख्य शब्दावली

वीडियो के 15 सीखने लायक शब्द, उच्चारण और अर्थ के साथ:

शब्द	उच्चारण	अर्थ
server संज्ञा	/ˈsɝvɚ/	सर्वर
attacker संज्ञा	/əˈtækɚ/	आक्रमणकारी
steal क्रिया	/stiːl/	चुराना
wallet संज्ञा	/ˈwɑl.ət/	बटुआ
packet संज्ञा	/ˈpæk.ɪt/	पुड़िया, पैकेट
script संज्ञा	/skɹɪpt/	लिपि, लेखन
laptop संज्ञा	/ˈlæp.tɑp/	लैपटॉप
theft संज्ञा	/θɛft/	चोरी
freeze क्रिया	/ˈfɹiːz/	जमना
cloud संज्ञा	/ˈklaʊ̯d/	मेघ, बादल
rank संज्ञा	/ˈɹæŋk/	श्रेणीबद्ध
plain संज्ञा	/pleɪn/	मैदान
wire संज्ञा	/ˈwaɪɚ/	तार
delay संज्ञा	/dɪˈleɪ̯/	देर, विलंब
log संज्ञा	/lɔɡ/	कुंदा, लट्ठा

इस वीडियो का व्याकरण

वक्ता जिन संरचनाओं का सबसे अधिक प्रयोग करता है, वीडियो के असली शब्दों के साथ:

संरचना	वीडियो में
Passive voice be + past participle — ज़ोर इस पर कि क्या होता है, न कि कौन करता है	being drained · was hijacked · was compromised
Relative clauses who / which + उपवाक्य — व्यक्ति या वस्तु के बारे में अतिरिक्त जानकारी	guys who technically · attack which was · scale, which is
Present perfect have/has + past participle — बीता हुआ काम जिसका असर अभी भी है	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/ का फ़र्क़ — /v/ में ऊपर के दाँत निचले होंठ को छूते हैं, /w/ में होंठ गोल होते हैं: server /ˈsɝvɚ/, wallet /ˈwɑl.ət/, withdrawal /wɪðˈdɹɔ(ə)l/, meanwhile /ˈmiːnwaɪl/, wire /ˈwaɪɚ/
/z/ — इसे “ज” (/dʒ/) न बनाएँ: freeze /ˈfɹiːz/, compromise /ˈkɑmpɹəˌmaɪz/, treason /ˈtɹiː.zən/, decentralize /diːˈsɛntɹəlaɪz/, prioritize /pɹaɪˈɒɹ.ə.taɪz/
शब्द की शुरुआत में s + व्यंजन — पहले “इ” न जोड़ें: steal /stiːl/, script /skɹɪpt/, scan /skæn/, sponsor /ˈspɒn.səː/

इस वीडियो से अभ्यास कैसे करें

पहले बिना बोले पूरा वीडियो एक बार सुनें और जो शब्द नहीं आते उन्हें लिख लें।
0.75× गति से शुरू करें, एक-एक वाक्य की शैडोइंग करें, और सहज लगने पर सामान्य गति पर लौटें।
अपनी आवाज़ रिकॉर्ड करें और मूल से तुलना करें, ख़ासकर server, attacker, steal जैसे शब्दों पर ध्यान दें।

शैडोइंग तकनीक क्या है?

शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 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

इस पाठ की शब्दावली और बोलने के सुझाव

इस वीडियो की मुख्य शब्दावली

इस वीडियो का व्याकरण

ध्यान देने योग्य उच्चारण

इस वीडियो से अभ्यास कैसे करें

शैडोइंग तकनीक क्या है?