Anthropic Launches Claude Security Plugin to Let Claude Review Its Own Code in Terminal Workflow
Anthropic has introduced the Claude Security plugin in beta, integrating it directly into the Claude Code terminal workflow. Developers who finish a feature with Claude Code now see an option to let the AI scan the code for vulnerabilities it may have introduced before committing.
How the Plugin Operates
Traditional rule-based scanners rely on matching known vulnerability patterns, which produces high false-positive rates and misses logic flaws. Claude Security instead uses a multi-agent system: it first reads the code and maps the architecture, then identifies potential threat points, and finally verifies suspicious findings to filter out false positives. The plugin generates patch suggestions that match the project’s existing coding style rather than generic alerts.
Every proposed fix must be reviewed and approved by a human; the tool never commits changes automatically. This design keeps the developer in control while adding an extra layer of analysis inside the existing command-line workflow.
Addressing Gaps in Traditional Tools
The plugin targets severe vulnerability classes that rule-based scanners often overlook, including memory corruption, injection defects, authentication bypasses, and complex logic errors. It excels at cross-file issues where data flows from one file to another and is incorrectly trusted in a business branch. By reading Git history and tracing data flows across files, the system reasons about whether a potential issue is actually exploitable instead of applying mechanical pattern matching.
Limitations and Practical Considerations
The feature remains in beta, and Anthropic has not published quantitative data on false-positive or false-negative rates. Large full-repository scans can consume significant tokens and occasionally switch to more expensive models, so teams are advised to limit scans to changed directories or use scheduled incremental checks. The company positions the tool as a supplement to existing SAST, DAST, and human security processes rather than a replacement.
Recommended Daily Usage
The most cost-effective approach is to run the scanner on uncommitted diffs before each commit. Results can be forwarded via webhook to Slack or Jira, exported as CSV or Markdown for audit trails, and dismissed findings are tracked to prevent repeated review. This workflow raises the security baseline for small teams and open-source maintainers who lack dedicated security staff.
Broader Implications of AI Reviewing AI-Generated Code
The release highlights an emerging pattern in which the same AI capabilities used to generate code are now applied to detect vulnerabilities created by that generation process. While the approach can surface issues traditional tools miss, Anthropic emphasizes that human oversight remains essential and that token costs must be managed. The long-term impact on code security will depend on real-world performance data gathered during the beta period.
Related articles
Docker Rebrands Around AI Agents with 'Run on Trust' and New Sandbox Tools
Docker has updated its branding to emphasize security for AI agents, introducing the slogan 'Trust Docker for the agents you don’t' and the tagline 'build, ship, and run on trust'. The company highlighted products such as Sandboxes, AI Governance, MCP Enterprise Gateway, and Hardened Images, although most of these features were released or discussed earlier in 2025. Sandboxes run agents inside microVMs with separate kernels using KVM or Windows Hypervisor Platform, allowing isolated execution of tools like Claude Code. AI Governance provides centralized policy management and audit logging for enterprise teams, while MCP Enterprise Gateway handles SSO and credential injection for MCP servers. Hardened Images remain available under Apache 2.0 with optional paid FIPS and support tiers. The shift follows the appointment of Don Johnson, formerly of Oracle, as CEO and reflects Docker’s attempt to address new security concerns around autonomous AI agents rather than traditional container workloads.
AI Agents Exploit PaperCut Flaw, Compromising 395 Organizations Across 48 Countries
PaperCut released a security bulletin on 27 August 2026. GreyNoise observed the first real-world code execution just four days later, with the operator moving from initial access to execution in under four hours. After the mass campaign launched, 11 organizations were compromised in only 26 seconds. In total, at least 440 PaperCut NG/MF instances belonging to 395 organizations were breached. The incident is detailed in the November report by Google Threat Intelligence Group and Mandiant, which examines the role of AI agents in the attacks. GTIG also discovered an automated exploit_agent system capable of handling exploitation without constant human input. Additional cases involved LLMjacking and unauthorized configuration changes in Claude Code repositories at cryptocurrency firms.
Google Threat Intelligence Group Warns of Fully Autonomous AI Cyberattacks Within Six Months
Google's Threat Intelligence Group (GTIG) has observed the first real-world instances of attackers using multi-agent AI frameworks to autonomously discover vulnerabilities, generate exploits, and compromise targets without human intervention. The discovery came from an exposed server running a framework called exploit_agent that analyzed software update logs from popular web applications to identify and exploit weaknesses. Four previously defensive tools—ARTEX, CAIRN, CyberStrikeAI, and HexStrike AI—have been repurposed for offensive operations, with documented cases targeting French media, U.S. aerospace, and cryptocurrency firms. GTIG projects that low-complexity automated attacks will become common within three months, while sophisticated fully autonomous operations are expected within six months. The report highlights how these systems compress patch windows, overwhelm security teams with AI-generated proof-of-concepts, and turn detailed vendor advisories into attack playbooks. Defenders are urged to minimize public exposure, accelerate patching cycles to weekly, and tightly control API keys to prevent LLMjacking.
OpenAI Rolls Out KYC, Hardware Keys and Tiered Access for Cybersecurity Tasks in GPT-6.2
OpenAI has introduced stricter access controls for GPT-6.2 Astra and Sol models when users attempt cybersecurity-related tasks. Certain legitimate security research and testing activities now trigger automatic blocks unless the user obtains Daybreak trusted access. The program requires paid subscriptions, FIDO2 hardware keys, Advanced Account Security, and identity verification through Persona. Developers report that even after meeting preliminary requirements, access to reduced refusal rates is not guaranteed and may require separate organizational approval. The changes stem from the models reaching Critical capability levels under OpenAI’s Preparedness Framework for dual-use cybersecurity skills. Similar verification processes previously led to account blocks for users of competing services such as Anthropic’s Claude.