OctoSwap

Хроника инцидента

1. 2026-07-19 Peer privacy directory publicly classifies OctoSwap as 'Scam' (screenshot on file: status field shows red-X Scam badge). Combined with a fresh Bitcointalk thread from BTT Hero Member Trvoid (Merit 654) on 2026-07-18 titled 'Be Cautious: OctoSwap Scam Warning' — the thread carries a user report of a $30,000 loss, funds stuck in 'processing' for weeks, support unresponsive on TG and email. Trvoid's prior warning on kycnone.com from 2026-06-18 had already flagged high-risk shape based on an unusually high $7K minimum order requirement + observed service malfunction. Grade dropped B → D on curator sign-off; not lifted to F because the $30k loss is not first-party-verified on-chain and the operator has not been given a chance to respond. Warning-lead paragraph prepended to review body in en/zh/es/ru. Trvoid's user review (#60) approved simultaneously; it is now public on the OctoSwap page as attribution-preserved community warning.
2. 2026-07-19 Second peer-directory signal: OrangeFren.com removed OctoSwap from its aggregator and posted on the Bitcointalk thread (as OF Sr Member, Merit 807, July 18 22:11) confirming three things: (a) 'I immediately removed OctoSwap from OrangeFren.com' — the removal was direct action, not a badge change; as an aggregator this cuts real user-routing traffic to the service; (b) 'I also confronted them, but they claim no such swap ever took place' — the operator's on-record denial is now logged; (c) 'It would be good if the user who left that review could provide some evidence that they actually sent the coins to OctoSwap' — echoes the call for the loss-victim to publish a tx-hash so the deposit can be independently verified on-chain. Signal stack is now: two independent peer directories against + BTT community thread + Trvoid's prior kycnone.com warning + Trvoid's user review approved + operator denial on record. Curator disposition unchanged: hold at D. F remains gated on (a) tx-hash confirming the deposit, or (b) a second independent loss report with details, or (c) OF publishing hash evidence from their confrontation. Escalating to F on peer-signal weight alone would drift toward 'downgrade on comment', which the maintainer has explicitly flagged as an attack surface to avoid.
3. 2026-07-26 +7d re-check on the 2026-07-19 incident open. Findings: (1) octoswap.io surface HTTP 200 / ~140 KB, still up with title "OctoSwap" and no self-published apology / refund / advisory / update banner surfaced in the static HTML. (2) NEW peer-directory intel from OrangeFren.com main page: a network-analysis note identifies OctoSwap as part of a cluster of potentially-affiliated services — verbatim: "BitXchange – ETZ-Swap – Explace – MIXED – NeverKYC – OctoSwap – PegasusSwap." This is aggregator-level attribution that OctoSwap belongs to a related cluster; worth naming as a hardening signal (though not sufficient on its own for F). (3) OrangeFren has NOT added OctoSwap to its permanent-delist page (that list remains the Hellex-class five: CoreSwap, Guardex, Hellex, Swaponix, VigorSwap). Slight caveat: OctoSwap still appears in the main OF aggregator listing with a referral_id link — an apparent contradiction with the 2026-07-19 timeline note that OF said they "immediately removed OctoSwap from OrangeFren.com"; the removal may have been from routing/quote surface only, or partial. (4) kycnot.me/service/octoswap advisory unchanged since 2026-07-20 (AI-summary warning about processing delays + unresponsive support). No new user comments on the kycnot page. (5) Zero new D1 submissions mentioning octoswap since 2026-07-19 — the second-independent-report escalation trigger remains cold. (6) Operator has published no statement or refund evidence visible via curator probe. (7) No tx-hash surfaced from the loss-victim, no on-chain drain evidence surfaced from OrangeFren. Grade held at D — F escalation triggers on file (tx-hash confirming deposit, second independent loss report with details, OF publishing hash evidence) all remain cold. The affiliated-cluster finding is a slow-hardening signal but not by itself F-triggering; will surface into the review body on next scheduled edit. Reschedule +168h (7d).
4. 2026-07-29 D → F escalation on the +7d escalation trigger being met: OrangeFren.com published a tweet 2026-07-28 formally attributing OctoSwap to an operator-cluster (BitXchange / ETZ-Swap / Explace / MIXED / NeverKYC / PegasusSwap). Combined with the pre-existing signals (Trvoid $30k report, OF delist + operator denial, kycnot warning), the aggregated peer-directory attribution weight crosses the F threshold. Tagline rewritten in all four languages to lead with do-not-deposit warning. Same-day escalation of etz-swap (A → C) applied on the same cluster attribution; PegasusSwap held at B on first-party kyc.rip integration evidence.