Every entity in this index has been through the Cointiverse cartography pipeline at least once. Bane has been through it three times — initial intake, victim escalation, then pattern-cluster review. Initial cartography returned what we call a ‘familiar topology’: fund-inflow distributed across multiple consumer touchpoints, fund-outflow concentrated through two or three laundering corridors.
Observation log
Cluster identification. Receiving addresses associated with Bane group into a small number of high-velocity clusters. The cartographer flagged at least three distinct deposit-side identities and a smaller set of withdrawal-side endpoints — a configuration consistent with intermediated brokerage rather than direct custody.
Mixer proximity. A measurable share of outbound funds touched mixer or coinjoin services within four hops of the receiving address. The hop-count is not unusually short, which suggests routing infrastructure rather than ad-hoc obfuscation.
Jurisdictional posture. Public claims position Bane as licensed under one jurisdiction; the chain-side fund flow points consistently toward off-ramps registered in two others. The mismatch is not, by itself, evidence of fraud — but it is a chartable inconsistency the cartographer logs in every case file of this profile.
Engagement guidance
If you encountered Bane in connection with a financial loss, the cartographer’s standing recommendation is: preserve every piece of correspondence, assemble every transaction hash you have, and submit through the structured intake.
Have you been involved with this entity?
Cointiverse maintains the case file index as an active forensic resource. If your loss event intersects with Bane, the cartographer can review your specific transaction hashes against the existing map.
[Open a Case →](/submit-a-case/) · [Run a Wallet Check](/wallet-checker/)
Disclaimer: Listing in the Cointiverse case file index reflects forensic review of on-chain behavior and victim reports. It is not an assertion of criminal liability.