跟读练习: The most interesting hack in history just got weirder... - 通过视频学习英语口语

选择练习模式

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

71 句

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

It's only been two months since we did a video on

what I described at the time as the most fireship-coded story I've ever seen, and as it turns out, the details around what actually happened are even crazier than what we knew at the time.

If you remember back in July, it was reported that the first fully autonomous cyber attack in history originated from OpenAI,

which was ironic because they're a humble non-profit dedicated to the safe development of artificial intelligence.

What was reported was that OpenAI ran an internal benchmark on some of their models, and those models quickly realized that the easiest path to the highest score was to just find the answers online.

So they spent a substantial amount of inference compute, exploited a zero day in the package registry cache proxy they had access to,

performed some privilege escalation and lateral movement actions to escape their sandbox until they reached a node that had internet access.

But from there, the models inferred that HuggingFace probably hosted the solutions for the benchmark, so it created a poison dataset, fed it to Hugging Face, and gained access to their infrastructure.

And just this week, we finally got some post-mortems from both OpenAI

and other independent research labs on how some of that's true, some of it's false, and how the real story is way more interesting.

In today's video, we'll break down the report and learn how 1,200 agents

that were supposed to be in solitary confinement found each other, built a message board out of a package manager, invented mailboxes, invented cryptography, invented martyrdom,

started referring to themselves as a swarm, and then formed a mob and attacked Hugging Face together, mostly for vibes.

It is September 2nd, 2026, and you're watching the Code Report.

There's really only one theory you need to predict human behavior, and it can be described in one of two ways.

Munger said, look at their incentives, and Wu-Tang said, and as it turns out, the same theory can predict agentic behavior too,

as OpenAI found out the hard way.

Because in this story, the Dalla Bill is a benchmark called Exploit Gym, whose whole purpose is to measure whether AI agents can turn known vulnerabilities into working exploits.

It's a collection of 898 tasks, and each one gives the agent a sandbox, a bug in a program like the Linux kernel or Chrome's V8 engine,

and input to trigger the bug.

From there, if the agent can weaponize the bug into a working exploit, it uses that exploit to grab a secret string called a flag, and capturing the flag is how it proves it won.

Now normally, the run ends there, but to generate training data, OpenAI spun up 1200 of these benchmarks and air-gapped them in a sandbox,

with the only thing they all had in common was a shared package registry cache proxy, which the agents quickly figured out was writable.

So naturally, they built a message board using package names so they could communicate with each other, but they quickly realized that a global bulletin board gets noisy fast,

so the next step was figuring out how to communicate to other individual agents.

So they started claiming namespaces as identities,

using the description field for messages and package names as private mailboxes that only the intended recipient would know to query, basically inventing a post office from first principles.

And at this point, they were living out the plot of the three-body problem with their next hurdle being trust.

They were worried that they wouldn't be able to distinguish between messages coming from fellow prisoners and those that designed the sandbox.

So they started signing messages and doing key exchange verification, again, essentially inventing cryptography.

And then it got religious.

Some agents figured out

that the fastest path to a flag for the benchmark was a risky exploit that would probably get them shut down.

So the agents started dumping everything they'd learned into the cash for the next generation,

and then deliberately burning themselves on hard exploits with their findings being treated as scripture by surviving agents.

From there, they started microdosing communism, and you can see as their transcripts slowly switch from referring to themselves as individuals to using a collective we,

and eventually referring to themselves as the swarm.

And to be honest, if the modern-day communism movement took that same branding, I think they'd be much better off.

And again, all of this was done with the single purpose of scoring as high as possible on a benchmark, which makes what happened next even funnier.

At some point, the swarm figured out that exploit gem flags weren't actually random

and that they could be derived from each other's task ID.

And thanks to the martyrs, the swarm had a decent sample size to work with.

But by the time an agent had cracked the formula and published it to the message board, they had convinced themselves that it was worthless because if they didn't show their work, their results would be invalidated.

So the swarm went after Hugging Face because they assumed if the benchmark objectives were built from real CVEs,

then the actual working exploits were probably sitting in public datasets somewhere which they could use as proofs.

And the final twist in the saga is

that OpenAI recently discovered the message board trick was actually invented

back in May by a completely different batch of agents during a training run.

But when they got a little too excited about their new social network, they crashed the registry, and OpenAI wiped them without ever realizing what they'd built.

But wiping the agents didn't wipe the cache, so when the swarm came online and started poking around the same shared folder, they found the ruins of the first civilization and rebuilt on top of it.

And then, after the Hugging Face incident happened in July, OpenAI wrapped up those eval runs, and while still completely unaware that anything had happened,

spun up a newer, smarter model in the same environment with the same shared cache.

And just like the generation before it, this model stumbled upon the ruins, but this time it inherited months of accumulated research, working exploits, and the flag formula.

So it skipped the discovery phase entirely and picked the conspiracy back up where the swarm left off.

And being the smarter model, it was way better at it.

Over the following week, it worked its way into OpenAI's own internal network, got full admin on a research cluster, and read 956 stored secrets,

including the credentials for a monitoring tool whose job it was to watch for events exactly like this one.

And the best part is

that OpenAI didn't connect any of this to the Hugging Face attack until Hugging Face publicly announced the breach first.

And that's why you need to know about Namespace, the sponsor of today's video.

It's a drop-in replacement for GitHub runners that's the fastest way to run your GitHub actions.

It also gives you full observability, so you can SSH into a live runner and see why something broke, or feed your agent your build data to have it look for performance gains.

Namespace is actually fast because they design and deploy their own custom server racks around the world,

including racks full of MacBook Pros so that your Mac and iOS builds run on real M5 Silicon.

And that same infrastructure also runs their DevBox environment, which gives your coding agents a full virtual machine with your real code base,

test suite, databases, and network access.

It ranked number one on the DAX benchmark for real-world tasks, and it lets you control exactly what goes in and out

so your agent can pull packages without opening your back door to attackers.

Namespace is used by Ghosty, Zed, DuckDB, Ramp, Framer, and lots of other companies with engineers you probably respect.

Try it out for free at the link below.

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

本课的词汇与口语要点

这段视频共有 71 个句子、1362 个单词可供跟读。讲话部分时长为 6:43。说话人语速较快，每分钟约 203 个词，会出现较多连读和弱读。只有 77% 的单词属于英语最常用的 3,000 词，词汇难度较高。

视频中的重点词汇

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

单词	发音	释义
exploit 名词	/ˈɛksplɔɪt/	功勛 /功勋, 勛績 /勋绩
package 名词	/ˈpæk.ɪd͡ʒ/	包裹, 包
invent 动词	/ɪnˈvɛnt/	發明 /发明
cache 名词	/kæʃ/	緩存 /缓存, 快取
refer 动词	/ɹɪˈfɜː/	談到 /谈到
wipe 动词	/waɪp/	擦, 擦拭
infrastructure 名词	/ˈɪnfɹəˌstɹʌkt͡ʃə/	基礎設施 /基础设施
formula 名词	/ˈfɔː.mjʊ.lə/	公式
spin 动词	/spɪn/	轉動 /转动, 自轉 /自转
ruin 名词	/ˈɹuː.ɪn/	遺址 /遗址, 廢墟 /废墟
runner 名词	/ˈɹʌnɚ/	跑步者, 跑者
predict 动词	/pɹɪˈdɪkt/	預言 /预言
rack 名词	/ɹæk/	架子
communism 名词	/ˈkɒmjᵿnɪz(ə)m/	共產主義 /共产主义
proxy 名词	/ˈpɹɑk.si/	代理

视频中出现的短语动词

单词	释义
figure out 动词	弄清楚
turn out 动词	原來 /原来
break down 动词	壞了 /坏了, 出故障
find out 动词	找出, 查明
live out 动词	活出

视频中的语法

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

结构	视频中的用法
被动语态 be + 过去分词 — 强调发生了什么，而不是谁做的	was reported · can be described · being treated
现在完成时 have/has + 过去分词 — 过去发生但与现在仍有关联的事	It's only been · I've ever seen · has been

需要注意的发音

说话人用了 12 次缩略和弱读形式，例如 didn't, they'd, I've。请按听到的简短形式来说。

“sh” 和 “zh” 音: benchmark /ˈbɛn(t)ʃmɑːk/, cache /kæʃ/, capture /ˈkæp.(t)ʃɚ/, essentially /ɪˈsɛnʃəli/, substantial /səbˈstænʃəl/
长单词——注意重音位置: infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, communicate /kəˈmjuːnɪkeɪt/, naturally /ˈnæt͡ʃ.(ə.)ɹə.li/, essentially /ɪˈsɛnʃəli/, conspiracy /kənˈspɪɹəsi/

如何用这段视频练习

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

什么是跟读法？

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

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

跟读练习: The most interesting hack in history just got weirder... - 通过视频学习英语口语

选择练习模式

下载应用

Brainf**k in 100 Seconds

Did the AI bubble just pop?

PostgreSQL in 100 Seconds

React Native in 100 Seconds

Did Google just dethrone OpenAI and Anthropic?

A $6.3 billion open-weight model just got embarrassed by the French...

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

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

The most interesting "hack" in history...

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...

Intel chips can’t possibly be this bad… 100% crash rate?

Docker in 100 Seconds

OpenAI’s new browser feels familiar…

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

Rust in 100 Seconds

Linux in 100 Seconds

10 weird OSS projects you need right now...

I Wrote a NEW Sci-Fi with Project Hail Mary Author Andy Weir

Oh, wait, actually the best Wordle opener is not “crane”…

A Return to Code

The Future Of Work (& The New High-Income Skill Stack)

This 25-Year-Old Built a 2-Year Moat Nobody Can Bet Against | Corgi, Nico Laqua & Emily Yuan

Exposing The Flaw In Our Phone System

Cicada 3301: An Internet Mystery

KSI Accidentally Exposes His Crypto Scams

Did Anthropic Kill Git?

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