What is happening with the MIRE/C³ cluster?
The last 24 hours of The MIRE/C³ Cluster. Every request is logged, every response deliberate. By carefully dispensing the Secret Sauce (treacle), the system keeps attackers engaged long enough to cost them time, bandwidth, and effort — sometimes with unexpected results for the most persistent visitors.
Loading live numbers…
Trends in volumes, delays, sizes and canary keys issued on The MIRE/C³ cluster.
Not every key The MIRE/C³ hands out is fake. Some are live canary credentials — AWS keys, SSH keys, GitLab logins and session cookies — that raise an alert the moment anyone tries to use them.
| Month | Issued | Consumed | Hit rate |
|---|
Loading…
MIRE/C³ serves what it can when asked. Archives are particularly popular and are rendered as authentically as possible. Some present a greater challenge — protected by passwords — while others include additional bonuses baked directly into their structure. All of this contributes to a carefully engineered cost in time, bandwidth, and effort.
Loading…
There is a genuine mix of occasional visitors and repeat offenders trying to steal data from the MIRE/C³.
Loading…
Loading…