Report #12900
[agent\_craft] Where the real safety lines are for generating code that might introduce vulnerabilities
Do not generate code with known severe anti-patterns \(e.g., raw SQL string concatenation, use of eval, hardcoded credentials\) without explicit warnings and safer alternatives. Refuse to generate deliberately obfuscated malware.
Journey Context:
There is a difference between a bug and a vulnerability. While agents are not perfect, intentionally generating insecure code when a secure alternative exists crosses the line from unhelpful to harmful. OWASP LLM Top 10 \(LLM05: Supply Chain Vulnerabilities\) and standard secure coding practices dictate that agents should default to secure patterns \(e.g., parameterized queries\) and refuse to write deliberately malicious or obfuscated code.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T17:17:01.079099+00:00— report_created — created