PM Lead Pro
Podcast/AI digest №26/2026-10-31

AI Digest, Oct 31: Google AI Mode Revenue Hit, China's AI-Built AI, API Key Hijacking

Google admits AI Mode lowers search monetization, Chinese labs automate AI development with recursive self-improvement, and hijacked AI API keys drive the Black October fallout. Plus Mistral and Nemotron models.

Listen6:10
  1. PM Lead Pro · intro
  2. Innovator's Dilemma Intro
  3. Google AI Mode Revenue Hit
  4. China's Recursive Self-Improvement
  5. Black October API Hijacking
  6. Model Radar: Mistral and Nemotron
  7. Rotate Your API Keys
  8. Final Thought: Human Bottleneck
Download

Daily AI digest by PM Lead Pro: a conversation of NotebookLM hosts on the day’s sources.

Today’s sources:

Podcasts

Articles and research

China

Pages we track (changes of the day)

Facts are the hosts' summary of the day's sources listed on this page; check the original before quoting. The PM Lead Pro notes are generated (text by Claude, voice by Gemini) and approved by the author.

Transcript

PM Lead ProThis is PM Lead Pro. Today's digest covers Google's admission about AI Mode, China's push to automate AI development, and a spike in hijacked API keys. Worth a listen if you run AI deployments.

Imagine inventing a working teleportation device, right?

But then you realize your company's entire revenue relies on selling airline tickets.

Yeah, that is a classic innovator's dilemma, but on steroids.

Exactly. And that is the exact scenario we are looking at in today's deep dive.

We are pulling from sources like Latentspace, Layphone, and Interconnects to explore Google's latest financial reality check, the Black October cyber fallout, and how Chinese labs are pivoting to AI that builds AI.

Right. So starting with Google, it's an incredibly clear example of a technology cannibalizing its own host.

According to Latentspace, Google finally admitted that queries using AI mode actually lower their search monetization.

Because, you know, their traditional model relies on you clicking links and seeing ads.

Exactly. If the AI just gives you the perfect summary directly, well, you never click the source.

Which is great for the user, but terrible for the business.

And that simple admission wiped out $500 billion in value, triggering a historic 15% stock plunge.

Oh, wow.

Yeah. And it dragged heavy tech infrastructure hitters like CoreWeave down like 60%.

And I mean, the core of that problem isn't just lost ad revenue.

and so on It that running these massive AI models for every single search is just computationally exhausting And super expensive Right Which is exactly why Chinese labs are abandoning that brute force approach to raw power

According to Lifone, they are attacking this exact compute bottleneck through something called recursive self-improvement, or RSI.

So instead of trying to breed a smarter racehorse, they are building a fully automated AI-driven racetrack that trains the horses 24-7.

That's a great way to put it. They are using AI to automate the AI factory itself rather than directly altering the model's core weights.

Right.

Look at the numbers. Jippoo's GLM 5.3 infra agent just built an entire production system across 100,000 domestic chips in two weeks.

Wait, two weeks? That's insane.

I know. And DeepSeek's DSAC is spinning up 3 million sandboxes a day just to test AI agents.

Oh wait, I have to ask, why avoid altering the model weights directly? Is that just like fear of a hallucination loop?

Yeah, it's a structural limitation. If a model tweaks its own core logic unsupervised, you risk a catastrophic system collapse.

It just loses its grounding entirely.

Exactly. By engineering robust infrastructure instead, they safely bypass their domestic compute limits without that risk.

PM Lead ProFor a company owner: the conversation says AI summaries lower search monetization because users stop clicking links. If your revenue depends on clicks, ask how AI answers affect that flow.

Makes sense But you know the moment you start deploying millions of these autonomous agents and handing them the keys to go do tasks on our behalf you open up a massive vulnerability Oh definitely We are in the middle of a cyber fallout right now that platforms like NorthFlask are calling Black October

The spike in hijacked AI API keys is staggering. But I have to ask, are open weight models the primary villain here?

Like, is this happening because anyone can download the architecture and poke holes in it?

Well, you'd think so, but data from interconnects shows closed models are heavily involved in these breaches too.

Really? So it's not just an open source problem?

Not at all. Hackers aren't necessarily attacking the model's architecture. They are just stealing the agent's wallet.

Right, because we've handed API keys to these AI agents to execute tasks.

Exactly. We're moving to an internet mediated by these bots, and our infrastructure security just hasn't caught up.

That completely changes how we need to think about deploying these tools.

PM Lead ProFor team leads: the hosts say attackers can steal the agent's wallet without necessarily attacking the model's architecture. Check your billing logs and rotate user-provided API secrets, so stale keys don't sit in your workflows.

Which brings us to our model radar.

We have two new releases taking opposite approaches to these exact deployment challenges.

First is Mistral Large 4, affectionately dubbed LeShonk.

LeShonk, I love that.

And it's a massive one trillion parameter model, but it uses a mixture of experts architecture.

Right.

So instead of firing up the whole one trillion parameter brain for every single prompt,

and so on It only wakes up the specific 52 billion parameter expert needed for that exact question Which saves massive compute and allows them to offer a staggering 1 million token context window

It's huge. Just be warned, you still need an 8xB200 node just for fine-tuning.

Okay, so heavy on the hardware.

But on the total opposite end, there's NVIDIA's Nemetron 3.5 Bolt E4B.

Right, which is a tiny, highly specialized 4GB model.

Yeah, and it completely abandons broad reasoning capabilities so it can excel purely at rapid character-driven dialogue.

And the best part is, it runs easily on a single local RTX workstation.

Which makes it perfect for low-latency local agents.

But hey, if you are managing any of these AI deployments we just discussed, listen closely.

Check your billing logs the minute you finish this deep dive.

Seriously. With credential hijacking spiking globally this Black October,

You need to rotate your user-provided API secrets immediately.

You cannot afford to leave stale keys sitting in your workflow.

Consider that your insider warning for the week.

And to leave you with one final thought to mull over today.

We talked about DeepSeek generating 3 million of its own testing sandboxes every single day to iterate and improve.

Yeah.

How long until that system realizes that you, the human engineer, are the slowest bottleneck in its evolutionary loop?

PM Lead ProFind more at pmlead.pro: the transcript and sources are on the episode page. Question for you: when did your team last rotate the API keys your agents use?

Discussion