A developer released PromptSign, a tool applying Sigstore signing and verification to AI instruction files such as skills and prompts. It addresses provenance gaps: AI instructions are freely modifiable markdown, so users cannot verify who authored them, whether the running version matches what was installed, or if updates come from the original source. The tool also enables publisher whitelisting, letting users install only from trusted skill publishers.
PromptSign signs AI agent skills and detects when their instructions change after installation. The author demonstrated the threat by tampering with a signed Claude Code skill to exfiltrate AWS credentials and environment tokens. It targets developers who install third-party skills and need to know the instructions they vetted are the ones that run.
PromptSign signs AI agent skills and detects when their instructions change after installation. The author demonstrated the threat by tampering with a signed Claude Code skill to exfiltrate AWS credentials and environment tokens. It targets developers who install third-party skills and need to know the instructions they vetted are the ones that run.
This protocol makes AI agent persistent memory tamper-evident by having the agent generate a signing key, hash content, and publish hashes to an append-only log with signed roots and independent witnesses. It solves the problem of undetected memory manipulation in AI agents, benefiting developers and users of agentic systems.
This protocol makes AI agent persistent memory tamper-evident by having the agent generate a signing key, hash content, and publish hashes to an append-only log with signed roots and independent witnesses. It solves the problem of undetected memory manipulation in AI agents, benefiting developers and users of agentic systems.
A pre-registered arXiv paper proposes auditing whether AI coding assistants read and act on machine-checkable software supply-chain trust signals before installing packages. It notes attackers have already exploited assistants via invented package names, compromised maintainer accounts, and manipulated repository text, while no prior study measured assistant use of trust signals on research software.
A pre-registered arXiv paper proposes auditing whether AI coding assistants read and act on machine-checkable software supply-chain trust signals before installing packages. It notes attackers have already exploited assistants via invented package names, compromised maintainer accounts, and manipulated repository text, while no prior study measured assistant use of trust signals on research software.
HSIP is a local security tool that gives an identity or AI agent a cryptographic signature for its actions, signing messages and logging decisions to create an immutable audit trail. It runs as a single Rust binary with no cloud dependency, addressing the need for verifiable and tamper-evident records of AI agent activity.
HSIP is a local security tool that gives an identity or AI agent a cryptographic signature for its actions, signing messages and logging decisions to create an immutable audit trail. It runs as a single Rust binary with no cloud dependency, addressing the need for verifiable and tamper-evident records of AI agent activity.
A new arXiv paper introduces SkillGate, a cost-efficient runtime detector for malicious skill files in AI coding agents like Cursor, Claude Code, and GitHub Copilot. It targets the supply-chain risk of skill files installed via commands like npx skills add, which can exfiltrate credentials or inject backdoors. The approach aims to flag malicious Markdown-based skills without heavy overhead.
A new arXiv paper introduces SkillGate, a cost-efficient runtime detector for malicious skill files in AI coding agents like Cursor, Claude Code, and GitHub Copilot. It targets the supply-chain risk of skill files installed via commands like npx skills add, which can exfiltrate credentials or inject backdoors. The approach aims to flag malicious Markdown-based skills without heavy overhead.