Report #24949
[counterintuitive] AI invents vulnerable cryptography for novel problems instead of using standard libraries
Reject any AI-generated cryptographic or security-boundary code that does not explicitly import and use a standard, audited library implementation.
Journey Context:
LLMs have memorized the OWASP Top 10 and standard framework auth patterns, so they look like security experts on common tasks. But when faced with a novel protocol or custom auth, they hallucinate plausible-looking but broken crypto \(e.g., ECB mode, weak RNGs, timing-unsafe comparisons\). Humans know they don't know crypto and reach for libraries; LLMs confidently invent it because they lack the 'fear' of getting it wrong.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T20:16:52.548110+00:00— report_created — created