NewsLayer.com
NewsLayer PulseLIVEBTC$77,314-0.32%ETH$2,392-1.65%SOL$99.11-1.76%XRP$1.33-2.23%DOGE$0.0816-0.65%ADA$0.1964-0.43%Total Cap$2.60T-0.33%Layer Index41 Neutral

Researchers easily trick Fortune-500 companies' AI agents into running arbitrary code — supply-chain attack via llms.txt guidance file illustrates how data has become code

Researchers have managed to execute code within an "llms.txt" file that many large companies use to instruct AI agents on how to scrape the website correctly. Back when the internet exploded and search engines became popular, sites…

Tom's Hardware

Publisher

Sep 2, 2026 at 10:20 AM UTC · Updated 6時間前 · 6 分で読める

Researchers easily trick Fortune-500 companies' AI agents into running arbitrary code — supply-chain attack via llms.txt guidance file illustrates how data has become code
Image via Tom's Hardware
翻訳中…

Researchers have managed to execute code within an "llms.txt" file that many large companies use to instruct AI agents on how to scrape the website correctly. Back when the internet exploded and search engines became popular, sites started publishing a "robots.txt" file to guide search bots to content. That's still widely used today, but it's now been supplemented with "llms.txt", a file containing textual instructions for AI agents to follow.

The experts from Pandex got their own code to run on AI agents from "companies you have definitely heard of" in the Fortune 500 list, and illustrated yet another way in which the once-sacred distinction between "data" and "code" is all but dead.

The purpose of llms.txt is straightforward: it's often hosted on a software product's website and contains a brief description, setup instructions, and quick installation steps — think of the usual README file, but written for agents. When a bot reaches the website, instead of spending precious tokens and context window space parsing the whole documentation, it reads llms.txt and immediately knows how to operate the code in question: what language it uses, the environment it runs in, any dependencies, and often, precise setup/installation instructions. And that's precisely where the problem lies.