claude-agent-sdk
Audited by Socket on Sep 18, 2026
3 alerts found:
SecurityAnomalyx2The fragment is ordinary SDK documentation and contains no clear malicious payload or supply-chain backdoor. It does contain significant security hazards in example implementations: unrestricted JavaScript eval, weakly restricted Python eval, arbitrary-URL fetching, credential-bearing API requests with caller-controlled paths, direct SQL execution, and unencoded Python query parameters. These examples should not be deployed unchanged with untrusted model or user input. The findings indicate security risk but not malicious intent.
No clear malware or intentional supply-chain payload is present. This is a permission-callback demonstration, but its security controls are weak: arbitrary readable-file access is approved, and Bash filtering based on a short substring blacklist can be bypassed. It should not be treated as a secure sandbox without stronger allowlisting, path canonicalization, isolation, and command restrictions.
The fragment is intended as a Claude-based code-analysis and repair orchestrator, but it cannot run because of malformed prompt references and incomplete assignment syntax. It contains no direct malicious behavior or explicit data theft. If corrected, its broad Bash, Write, and Edit permissions combined with acceptEdits could permit significant model-directed host changes and should be constrained with least-privilege tools and explicit approval.