The terminal froze. No warnings, no errors. Just a cursor breathing in the dark.
This is the hallmark of an environment agnostic Linux terminal bug — the type that slips past local tests, ignores CI pipelines, and appears in production without a traceable fingerprint. It does not care about your distro, your shell, or your container runtime. Bash, zsh, tmux — all vulnerable. The bug is self-contained, indifferent to environment variables, locale settings, or custom dotfiles. It operates on core terminal behavior, making replication and debugging a high-friction process.
The trigger often comes from subtle mismatches between terminal emulators and low-level I/O handling. A sequence of bytes, often tied to control characters, will silently poison output rendering or input handling. This is not influenced by $TERM values or common config overrides. It survives SSH hops, survives Docker, survives Kubernetes pods. Engineers attempting to isolate the source find themselves chasing ghost processes, phantom file descriptors, and race conditions between stdout and stderr.