containment
Audited by Socket on Feb 16, 2026
1 alert found:
Security[Skill Scanner] AWS access key detected All findings: [CRITICAL] hardcoded_secrets: AWS access key detected (HS002) [AITech 8.2] [HIGH] data_exfiltration: Credential file access detected (DE002) [AITech 8.2.3] [HIGH] skill_discovery_abuse: System prompt extraction attempt (SD002) [AITech 4.3] This skill document is a containment playbook specification and example interface; it is internally consistent with its stated purpose and does not contain code that exfiltrates data, contacts untrusted domains, or embeds obfuscated malicious logic. The main security concerns are operational: it requires high-privilege credentials that must be protected, the examples show printing sensitive data (which is insecure), and executing generated containment commands without human review or proper safeguards could cause significant disruption. Recommend treating credentials and outputs as sensitive, enforcing least-privilege, adding explicit warnings about not printing secrets, and ensuring playbooks are integrated into a controlled SOAR/IR process with approvals. LLM verification: The skill is conceptually appropriate for containment playbooks and the requested capabilities align with its stated purpose. However, there are concerning issues: a realistic-looking AWS key appears in the documentation, references to reading configuration files and printing rollback instructions could lead to accidental credential leakage, and no implementation detail is provided about where action payloads/credentials are sent. Because the skill needs highly privileged credentials and the doc