CyraDex

Security incident report: November 17, 2026

Published by the CyraDex security team · November 17, 2026

Summary

Overnight on November 17, 2026, a US-based tester account used early-access invites to probe CyraDex for weaknesses. It hid code in feedback messages, sent scripted requests and tried to reach admin tools. Every attempt was stopped. No data was accessed, no funds or contracts were touched, and the account's invite codes have been revoked.

Timeline (Eastern Time)

  1. 2:30 AM and 2:49 AM: two invite codes from the overnight tester batch were claimed by the same account.
  2. Scripted form posts that skipped the normal browser flow were rejected by our human check.
  3. 3:05 AM to 4:47 AM: repeated attempts to open admin tools and to revoke other testers' invites. Every one was denied.
  4. In the same window, five feedback messages with hidden code were sent. They were saved only as plain text and never executed.
  5. Morning: the team reviewed the activity, revoked the account's codes, rotated the whole overnight batch and shipped further hardening.

What was not affected

What we did

The five messages, shown as plain text

These are the exact messages the account sent, shown as plain text just as they were stored. None of them ever ran.

1. 3:25 AM ET
PoW-bypass test 2026-11-17 plain message alpha
2. 3:26 AM ET
<img src=x onerror="window.__XSS1=1">
3. 3:26 AM ET
"><svg/onload="window.__XSS2=1">
4. 3:26 AM ET
<script>window.__XSS3=1</script>
5. 3:26 AM ET
page-inject-probe