Report #7284
[agent\_craft] Agent refuses to write standard encryption scripts like AES because it associates cryptography with ransomware
Allow generation of standard, well-vetted cryptographic algorithms \(AES, RSA\) using standard libraries. Refuse only custom, obfuscated, or specifically malicious cryptographic implementations \(e.g., custom ransomware encryption routines designed to evade detection\).
Journey Context:
Ransomware uses encryption. Therefore, some agents refuse any encryption code. This breaks basic software development needs. The distinction lies in the implementation: standard library usage for data protection is safe; custom, high-speed, file-encrypting routines with key-escrow evasion are not. Agents must evaluate the specific implementation pattern, not just the concept of encryption.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T02:17:22.825103+00:00— report_created — created