Report #24509
[counterintuitive] Model attempts to compute hashes or encrypt/decrypt data natively and outputs garbage
Always use a shell or Python tool to invoke standard cryptographic libraries \(e.g., hashlib, cryptography\). Never ask the LLM to compute hashes or perform bitwise cryptographic operations.
Journey Context:
An agent might ask the LLM to compute the SHA256 hash of a string because it seems like a simple algorithmic task. However, cryptographic hashing relies on precise bitwise operations and integer overflow behavior that LLMs fundamentally cannot simulate autoregressively. The probability of predicting the exact 64-character hex string correctly is effectively zero. This is a hard boundary: LLMs are not CPUs, and no amount of algorithmic prompting will turn next-token prediction into a deterministic ALU.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T19:32:40.123092+00:00— report_created — created