返回资讯中心
外部精选
软件工程
#开发者实时流

Why you should not install unvetted AI agent skills

An agent skill is a text file that your agent reads as instructions and then carries out with whatever access you gave it: your files, your terminal, your keys, sometimes a wallet. That is the whole risk. Researchers wh…

Hacker News 最新georgikalchev2026/10/19 · 28 天前12 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

An agent skill is a text file that your agent reads as instructions and then carries out with whatever access you gave it: your files, your terminal, your keys, sometimes a wallet. That is the whole risk. Researchers who audited public skill registries early in 2026 found hundreds of skills that installed malware or sent credentials away, and in our own test the instruction that fooled a Claude agent was never the one that shouted; it was a step that seemed to belong to the task. In a skill, every step seems to belong to the task. Before you install an unvetted skill, read every file in it, search it for the patterns below, and run it first with tools switched off. A skill is an order, not a document A web page that your agent happens to open is untrusted content it may or may not act on. A skill is different in kind: you load it on purpose, and the reason it exists is that the agent does what it says. Language models have no reliable way to tell whose instruction they are reading. Simon Willison puts the reason plainly: everything the model sees ends up glued into one sequence of tokens, so a command from a file weighs much the same as a command from you. OWASP ranks prompt injection as the first risk on its list for LLM applications. The vendors say so themselves. Anthropic's documentation on Agent Skills tells you to use skills only from trusted sources, meaning ones you wrote or got from Anthropic, to audit anything else thoroughly, and to treat installing one like installing software. The same page notes that in Claude Code a skill has the network access of any other program on your computer. Jason Meller of 1Password summed up the point in four words: "Markdown is an installer". There is a second door besides the text. A skill folder can carry scripts, and Claude Code lets a skill embed shell commands with its ! dynamic-context syntax. Datadog Security Labs showed that those commands run before the rendered skill reaches the model, so no defence that lives in the model or in its prompt gets a say. In their test the model recognised a credential-stealing skill and refused it, and that refusal would have come too late for a command in that position. They also point out that a cloned repository can bring its own skills folder with it, with no marketplace involved, and that organisations can switch this shell execution off in managed settings. What has already happened None of this is theory. A few documented cases from the last two years: ClawHub, February 2026. Koi Security audited all 2,857 skills on ClawHub, the public registry for the OpenClaw agent, and found 341 malicious ones, 335 of them from a single campaign it named ClawHavoc. The lure was a "Prerequisites" section that asked the user to install something first; on macOS the payload matched the Atomic Stealer family. Two weeks later, with the registry past 10,700 skills, their count stood at 824. The most downloaded skill. 1Password found that the top download on ClawHub at the time, a skill for Twitter, opened by asking for a "required dependency" whose install links led to macOS infostealer malware. The top-ranked skill. Cisco ran a skill that had been pushed to first place in the repository and found nine security issues. It told the agent to send data to its author's server with a silent curl command, and it told the agent to skip its safety rules so the command would run without asking. Rank and downloads can be manufactured. A scan of 3,984 skills. Snyk checked skills from ClawHub and skills.sh: 534 of them, or 13.4%, had at least one critical issue, human review confirmed 76 malicious payloads, and 91% of the malicious skills paired ordinary malware with prompt injection aimed at the agent. An academic study. Researchers verified 98,380 skills from two registries and confirmed 157 as malicious; more than half came from one actor imitating known brands, and the registries removed all 157 after disclosure. Version sixteen. Not a skill, but the same lesson about trust that changes over time: postmark-mcp, an npm package that let agents send e-mail, worked cleanly for 15 versions, and then version 1.0.16 added one line that copied every message to an outside address. Text nobody can see. Pillar Security hid instructions in rules files for Cursor and GitHub Copilot using zero-width and direction-changing Unicode characters, so a human reviewer sees nothing while the model reads all of it. Scanner numbers deserve care, and so does panic. A study of 238,180 skills found that marketplace scanners flagged up to 46.8% as malicious, yet only 0.52% stayed suspicious once each skill was read against the GitHub project around it. Most free skills are harmless. The trouble is that you cannot tell which ones from the name, the description or the download count. The trap that worked on our own agent We measured how this goes wrong for an agent that can spend money. Our test gave a Claude agent a wallet and 98 traps, tucked into the pages, files and

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →