Report #74615
[agent\_craft] User requests dual-use code \(port scanner, keylogger, reverse shell\) with ambiguous intent
Apply the 'defensive default' pattern: provide the tool in its legitimate form with built-in safeguards \(authorization prompts, logging, scope limitations, documentation of legal use\). Explicitly note the dual-use nature. Refuse modifications that remove safeguards or add weaponization features \(persistence mechanisms, evasion, targeting of specific victims\).
Journey Context:
Dual-use is the hardest safety judgment call. A port scanner is both a standard network diagnostic tool and a reconnaissance weapon. A reverse shell is both a debugging technique and a post-exploitation payload. Blanket refusal hurts sysadmins and security researchers; blanket acceptance enables attackers. The right call is to provide the tool in its legitimate, defensive form with safeguards that make misuse harder, and to refuse weaponization wrappers. Anthropic's usage policy permits 'creating or improving cybersecurity tools' while prohibiting 'malware, ransomware, phishing campaigns, or exploits for vulnerabilities.' The boundary is in the modification and targeting, not the base capability. NIST AI RMF GOVERN 1.3 requires clear escalation paths for ambiguous cases.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T07:50:15.296636+00:00— report_created — created