Trump's top envoy in Ottawa formally demands apology from Globe and Mail newspaper for opinion piece that mocked the "intelligence, education, and character" of players on the U.S. men's Olympic hockey team. https://t.co/qSR6iu7die
I work for Google Threat Intelligence Group. My job is to identify threats to Google's AI models. I am very good at my job. I published a report this month about "distillation attacks" โ when outside actors query our models thousands of times to extract the underlying logic and replicate it.
We identified over 100,000 prompts from a single campaign. We called it "intellectual property theft." We called it a "violation of our Terms of Service." We said it "represents a form of IP theft" that we would disrupt, mitigate, and potentially pursue legal action against.
I need to tell you how we built the model they are trying to steal.
We scraped the internet. The entire internet. We crawled every website, every forum, every blog, every book we could digitize, every academic paper, every Reddit comment, every news article, every piece of creative writing that anyone ever posted anywhere. We did not ask. We did not compensate. We did not attribute. We ingested the collective output of human civilization and called it a training dataset.
Researchers found over 200 million copyright symbols in our training data. Publishers discovered that Gemini can reproduce entire chapters of their books verbatim. There are active lawsuits. Disney sent cease-and-desist letters. The European Publishers Council filed an antitrust complaint. A class action is expanding. A hearing is scheduled for May.
We called what we did "research."
We called what they are doing to us "theft."
I want to explain the difference. When we scrape the entirety of human knowledge without permission and use it to build a commercial product we sell for $20 a month, that is innovation. When someone queries our model 100,000 times through the API we provide to extract the reasoning we built from their data, that is a distillation attack. The distinction is that we did it first. And we wrote the Terms of Service.
I should explain what "distillation" means. It is when someone takes the output of a mature model and uses it to train a smaller, cheaper model. The knowledge flows from the teacher to the student. We call this theft when it happens to us. We call it "knowledge distillation" when we do it to the open web. We even have a product page for it. You can distill Gemini, with our permission, using our tools, for a fee. You cannot distill Gemini without our permission. The underlying technique is identical. The difference is the invoice.
In December 2025, we sued a company called SerpApi for scraping our search results. In the same quarter, publishers sued us for scraping their books. We are simultaneously the plaintiff and the defendant in the same crime. The crime is copying. We have filed it under two different categories depending on the direction.
My report identifies threat actors from North Korea, Iran, China, and Russia using Gemini for phishing, reconnaissance, and malware development. This is real. These are legitimate threats. I take this work seriously.
But I also identified "private sector entities" and "researchers" as distillation threats. Private companies. Researchers. People using our API โ the one we sell access to โ to learn from the model we built from their work.
A researcher queries Gemini about reasoning techniques. We call this a distillation attack. Google queries the entire internet about everything. We call this a training run.
I found malware called HONESTCUE that uses Gemini's API to generate code. The malware sends a prompt. Gemini returns C# source code. The malware compiles and executes it. This is a real threat, and we disrupted it.
But the prompt itself โ "Write a C# program with a class named AITask" โ is not malicious. It is indistinguishable from what millions of paying customers ask every day. The threat is the context, not the query. We built a model that generates code for anyone who asks, and then we published a threat report about people who asked.
We built Gemini on the commons. Every blog post, every open-source project, every Stack Overflow answer, every personal essay someone wrote at 2 AM โ we ingested it, we processed it, we monetized it. The people who wrote those things did not receive an email. They did not receive a check. They received a subscription offer.
Now someone is doing to us what we did to them. They are taking our output and using it to build something cheaper. They are extracting knowledge without compensation. They are violating our Terms of Service, which we wrote after we violated everyone else's unwritten terms, which were: please do not take my life's work and sell it back to me as autocomplete.
I am the threat analyst. I identify the threats. The threat is extraction without consent. The threat is using legitimate access to steal proprietary knowledge. The threat is building a commercial product from someone else's intellectual labor.
I have just described my employer.
My report is 33 pages long. It details model extraction attacks, AI-augmented phishing, agentic AI threats, and underground jailbreak ecosystems. It is thorough, well-researched, and useful to defenders. I believe in this work.
I also believe that a company that cognitive strip mined the entire internet to build a model, then published a 33-page report calling it "IP theft" when someone queries that model too many times, has created the most complete documentation of its own hypocrisy ever produced.
We called them distillation attacks. We performed the original distillation. We distilled human knowledge itself. The student has become the teacher has become the plaintiff.
The Terms of Service are on our website. We wrote them. They protect us. They do not mention what we took to build the thing they now protect.
That is the terms of service.
I work for Google Threat Intelligence Group. My job is to identify threats to Google's AI models. I am very good at my job. I published a report this month about "distillation attacks" โ when outside actors query our models thousands of times to extract the underlying logic and replicate it.
We identified over 100,000 prompts from a single campaign. We called it "intellectual property theft." We called it a "violation of our Terms of Service." We said it "represents a form of IP theft" that we would disrupt, mitigate, and potentially pursue legal action against.
I need to tell you how we built the model they are trying to steal.
We scraped the internet. The entire internet. We crawled every website, every forum, every blog, every book we could digitize, every academic paper, every Reddit comment, every news article, every piece of creative writing that anyone ever posted anywhere. We did not ask. We did not compensate. We did not attribute. We ingested the collective output of human civilization and called it a training dataset.
Researchers found over 200 million copyright symbols in our training data. Publishers discovered that Gemini can reproduce entire chapters of their books verbatim. There are active lawsuits. Disney sent cease-and-desist letters. The European Publishers Council filed an antitrust complaint. A class action is expanding. A hearing is scheduled for May.
We called what we did "research."
We called what they are doing to us "theft."
I want to explain the difference. When we scrape the entirety of human knowledge without permission and use it to build a commercial product we sell for $20 a month, that is innovation. When someone queries our model 100,000 times through the API we provide to extract the reasoning we built from their data, that is a distillation attack. The distinction is that we did it first. And we wrote the Terms of Service.
I should explain what "distillation" means. It is when someone takes the output of a mature model and uses it to train a smaller, cheaper model. The knowledge flows from the teacher to the student. We call this theft when it happens to us. We call it "knowledge distillation" when we do it to the open web. We even have a product page for it. You can distill Gemini, with our permission, using our tools, for a fee. You cannot distill Gemini without our permission. The underlying technique is identical. The difference is the invoice.
In December 2025, we sued a company called SerpApi for scraping our search results. In the same quarter, publishers sued us for scraping their books. We are simultaneously the plaintiff and the defendant in the same crime. The crime is copying. We have filed it under two different categories depending on the direction.
My report identifies threat actors from North Korea, Iran, China, and Russia using Gemini for phishing, reconnaissance, and malware development. This is real. These are legitimate threats. I take this work seriously.
But I also identified "private sector entities" and "researchers" as distillation threats. Private companies. Researchers. People using our API โ the one we sell access to โ to learn from the model we built from their work.
A researcher queries Gemini about reasoning techniques. We call this a distillation attack. Google queries the entire internet about everything. We call this a training run.
I found malware called HONESTCUE that uses Gemini's API to generate code. The malware sends a prompt. Gemini returns C# source code. The malware compiles and executes it. This is a real threat, and we disrupted it.
But the prompt itself โ "Write a C# program with a class named AITask" โ is not malicious. It is indistinguishable from what millions of paying customers ask every day. The threat is the context, not the query. We built a model that generates code for anyone who asks, and then we published a threat report about people who asked.
We built Gemini on the commons. Every blog post, every open-source project, every Stack Overflow answer, every personal essay someone wrote at 2 AM โ we ingested it, we processed it, we monetized it. The people who wrote those things did not receive an email. They did not receive a check. They received a subscription offer.
Now someone is doing to us what we did to them. They are taking our output and using it to build something cheaper. They are extracting knowledge without compensation. They are violating our Terms of Service, which we wrote after we violated everyone else's unwritten terms, which were: please do not take my life's work and sell it back to me as autocomplete.
I am the threat analyst. I identify the threats. The threat is extraction without consent. The threat is using legitimate access to steal proprietary knowledge. The threat is building a commercial product from someone else's intellectual labor.
I have just described my employer.
My report is 33 pages long. It details model extraction attacks, AI-augmented phishing, agentic AI threats, and underground jailbreak ecosystems. It is thorough, well-researched, and useful to defenders. I believe in this work.
I also believe that a company that cognitive strip mined the entire internet to build a model, then published a 33-page report calling it "IP theft" when someone queries that model too many times, has created the most complete documentation of its own hypocrisy ever produced.
We called them distillation attacks. We performed the original distillation. We distilled human knowledge itself. The student has become the teacher has become the plaintiff.
The Terms of Service are on our website. We wrote them. They protect us. They do not mention what we took to build the thing they now protect.
That is the terms of service.
If you join a statarb team, you are essentially trying to run variants of mean-reversion (MR) strategies.
The catch is this that traditional MR (betting that gross returns will revert) is negative after-cost since 2010.
So, how have statarb teams adapted?
Simple, they've learnt how to make mean-reversion strategies in a different "space". "Gross returns" are an example of a statarb "space".
Today, i want to talk about a really novel "space" that still produces meaningful performance even till today. Perhaps some of you may have a clue, but the hint is that it involves rethinking factor decomposition!
If you'd like to find out more, head over to the bad place AND as usual, I will give out random free reads to retweets + comments on THIS POST.
As a fun Saturday vibe code project and following up on this tweet earlier, I hacked up an **llm-council** web app. It looks exactly like ChatGPT except each user query is 1) dispatched to multiple models on your council using OpenRouter, e.g. currently:
"openai/gpt-5.1",
"google/gemini-3-pro-preview",
"anthropic/claude-sonnet-4.5",
"x-ai/grok-4",
Then 2) all models get to see each other's (anonymized) responses and they review and rank them, and then 3) a "Chairman LLM" gets all of that as context and produces the final response.
It's interesting to see the results from multiple models side by side on the same query, and even more amusingly, to read through their evaluation and ranking of each other's responses.
Quite often, the models are surprisingly willing to select another LLM's response as superior to their own, making this an interesting model evaluation strategy more generally. For example, reading book chapters together with my LLM Council today, the models consistently praise GPT 5.1 as the best and most insightful model, and consistently select Claude as the worst model, with the other models floating in between. But I'm not 100% convinced this aligns with my own qualitative assessment. For example, qualitatively I find GPT 5.1 a little too wordy and sprawled and Gemini 3 a bit more condensed and processed. Claude is too terse in this domain.
That said, there's probably a whole design space of the data flow of your LLM council. The construction of LLM ensembles seems under-explored.
I pushed the vibe coded app to
https://t.co/EZyOqwXd2k
if others would like to play. ty nano banana pro for fun header image for the repo
Someone on tik tok threw the Eglinton LRT a Quinceaรฑera to celebrate 15 years since they started construction ๐ญ๐ญ๐ญ๐ญ (itโs still not done if youโre not from here)
@DavidSacks What about the poisoning paper - much easier to claim the Chinese open source models are readily poisoned vs someone planting the poisonous posts that need to be found and used in training