Incidents
What went wrong, with dates.
Every incident gets a timeline and a root cause. Fixed means verified by someone who did not write the fix — not a notice that something was addressed.
Two things in this entry are still open, and they are named rather than smoothed over.
The timings below are read from the two commits that bound the incident, so they are as exact as the repository is. What is not established is whether a build went out during the thirteen minutes — the deploy history available to us starts six days later — and whether the exposed key was afterwards rotated. Both are written as open. An incident page that resolves what it has not checked is worth less than no page.
#1 · Private key shipped in the connect block
2026-06-30 22:42:50 → 22:56:09 +03 · open 13m 19s- What happened
- The dashboard’s copy-paste connect block included a live signing key. Users were told to paste that block into third-party agents, so the key travelled wherever the block did.
- Exposure
- One key, and any transcript or provider log that contains the block. Treated as compromised regardless of whether misuse is observed — the alternative is assuming our way out of it. open: whether a build shipped inside the 13 minutes — the deploy history we hold begins 2026-07-06, six days later, so the record for that evening is missing. Missing, not empty: we will not read it either way.
- Fix
- The block emits only the agent name and address; the key is injected from the environment at launch and never written into a config file. Commit
24760cb9e9, which removes the lineRHINOGENT_KEY: agent.privateKey. Verified against the source, the built output and the deployed site — not by the person who wrote the fix. - Rotation
- open: rotation of the exposed key not confirmed
- Root cause
- Secret-handling rules covered the server code. The distribution artefact — an onboarding snippet — was not in scope, so nothing checked it. Snippets are now generated from a template that cannot reference a secret.
Scope note: this entry describes a key we published. It is not a claim about what any third party did with it, because we cannot see that and will not guess.
Our commitment
- ·An incident goes up with a timeline and a root cause, not a line saying something was “addressed”.
- ·“Fixed” means verified by someone who did not write the fix, against the deployed site rather than the source.
- · If we do not know the extent of something, the entry says so rather than implying a boundary we did not measure.
Found something? How to report it →