Dated security and solvency incidents affecting services in this directory, and how far the sourcing goes on each one.
26Incidents
1Confirmed
25Reported only
9Still open
Every incident was read against its own sources on . This page lists incidents an editor reviewed and is not a census of everything that has happened to these services. An incident is recorded here only after review; automated detection files leads for an editor and never publishes.
How to read a record
CONFIRMED
Three or more sources were read directly, at least one of them primary: the operator's own advisory, a court or government record, or the vendor's own repository. This is the bar an article must clear.
REPORTED
Fewer than three sources, or no primary source. The row is recorded because it bears on user risk, but it rests on what one party published and Cunicula has not independently confirmed it.
Status words
STATEONGOING
The exposure is still live for at least some users as of the review date on the record.
STATERESOLVED
The operator or an outside party closed the exposure and obligations were settled.
STATEDISPUTED
The parties disagree on the facts and no record read for this row settles it.
STATEUNPATCHED
A fix exists in principle but has not shipped, or shipped without repairing users already affected.
The prior review recorded an unreliable Tor route. The current status page reports the storefront, payments and served private-network routes operational; one recent I2P payment check failed but no ongoing service outage is reported.
What this means for a userThe prior review recorded an unreliable Tor route. The current status page reports the storefront, payments and served private-network routes operational; one recent I2P payment check failed but no ongoing service outage is reported.
Why it carries this statusThe reviewed record marks this incident resolved; remediation is complete. Independent corroboration was not established in the reviewed source set.
Upgrade to v2.4.3 or later, especially on shared multi-user servers; the release does not claim a confirmed compromise.
What this means for a userUpgrade to v2.4.3 or later, especially on shared multi-user servers; the release does not claim a confirmed compromise.
Why it carries this statusThe reviewed record does not establish full resolution; remediation is unknown. Independent corroboration was not established in the reviewed source set.
SageSwap reports an active campaign impersonating its support across Telegram and platform accounts and warns that support will never request wallet connection or wallet information. No resolution notice was found.
What this means for a userSageSwap reports an active campaign impersonating its support across Telegram and platform accounts and warns that support will never request wallet connection or wallet information. No resolution notice was found.
Why it carries this statusThe reviewed record does not establish full resolution; remediation is unresolved. Independent corroboration was not established in the reviewed source set.
The current official status history records a resolved network-connectivity issue at 03:31 UTC on 21 August 2026; no data or asset compromise is claimed.
What this means for a userThe current official status history records a resolved network-connectivity issue at 03:31 UTC on 21 August 2026; no data or asset compromise is claimed.
Why it carries this statusThe reviewed record marks this incident resolved; remediation is complete. Independent corroboration was not established in the reviewed source set.
The current official status history records a second resolved network-connectivity issue at 05:15 UTC on 21 August 2026; no data or asset compromise is claimed.
What this means for a userThe current official status history records a second resolved network-connectivity issue at 05:15 UTC on 21 August 2026; no data or asset compromise is claimed.
Why it carries this statusThe reviewed record marks this incident resolved; remediation is complete. Independent corroboration was not established in the reviewed source set.
GHSA-rxx8-rv5g-wpch describes a high-severity pull_request_target workflow flaw through 0.8.5-alpha. RoboSats identifies 0.8.6-alpha as patched and that release was already current when the advisory was published.
What this means for a userGHSA-rxx8-rv5g-wpch describes a high-severity pull_request_target workflow flaw through 0.8.5-alpha. RoboSats identifies 0.8.6-alpha as patched and that release was already current when the advisory was published.
Why it carries this statusThe reviewed record marks this incident resolved; remediation is complete. Independent corroboration was not established in the reviewed source set.
GHSA-xjwx-6j4q-hrr6 describes high-severity arbitrary runner-code execution through 0.8.5. RoboSats identifies 0.8.6 as patched and that release was already current when the advisory was published.
What this means for a userGHSA-xjwx-6j4q-hrr6 describes high-severity arbitrary runner-code execution through 0.8.5. RoboSats identifies 0.8.6 as patched and that release was already current when the advisory was published.
Why it carries this statusThe reviewed record marks this incident resolved; remediation is complete. Independent corroboration was not established in the reviewed source set.
Evidence basis: Claims on this page are linked to published sources for comparison, not certification, audit, endorsement, or recommendation; read the methodology and coverage map before relying on an entry.
