Recovery Doctrine: chain-of-custody · verifiable on-chain trail · regulator-ready packets verification chain: Etherscan · SlowMist · CertiK
62 claims under active investigation 106 wallet routes mapped this month Open a Free Recovery Consultation →

Tag: scam broker

  • Casefile Trade Room 24 — The Professor’s Note

    // FROM THE CASEFILE — TRADE ROOM 24

    Trade Room 24 is a casefile under reading. The deposits to traderoom24.com sit on-chain, immutable; the wallet pathway is the primary source, and the off-ramp endpoint is the conclusion the Professor’s marginalia points toward.

    Reading the wallets — Trade Room 24 casefile:

    • Deposit transaction hashes from the claimant wallet to the Trade Room 24 platform receiving address.
    • Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
    • Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
    • Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
    • Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

    From the lectern — off-ramp identification:

    • Endpoint counterparty in the Trade Room 24 casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Trade Room 24’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
    • Leverage is applied to that named counterparty — the Trade Room 24 packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Trade Room 24 off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

    How a Trade Room 24 casefile becomes a regulator-ready filing:

    1. Triage on Trade Room 24 — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on Trade Room 24 — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on Trade Room 24 — off-ramp endpoint matched to a named exchange counterparty.
    4. File the Trade Room 24 packet — IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
    5. Follow-through on Trade Room 24 — the Professor stays on the casefile until a documented next step exists.

    What we read in a Trade Room 24 casefile:

    • Chains in scope for Trade Room 24 — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
    • Off-ramps in scope for Trade Room 24 — named centralised exchanges with compliance leverage.
    • Filings supported on Trade Room 24 — IC3, state AG, off-ramp desk, civil discovery as applicable.

    Boundaries on every Trade Room 24 casefile — never crossed:

    • Recovery scammers do these things on Trade Room 24; the Professor never does — request seed phrases.
    • Recovery scammers do these things on Trade Room 24; the Professor never does — request remote logins.
    • Recovery scammers do these things on Trade Room 24; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on Trade Room 24; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on Trade Room 24; the Professor never does — call you unsolicited.

    Open a free consultation

    Book a reading of your wallet — file at /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Adal GROUP

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to Adal GROUP via this platform go quiet, the on-chain record stays loud. The Professor’s reading begins where the platform’s silence does — with the wallet that received the funds and the path it took afterward.

    Trace summary — funds that left this platform:

    • Deposit confirmations from the claimant to Adal GROUP’s receiving wallet at this platform.
    • Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
    • Cross-chain bridge transactions where the operator routed value out of the deposit chain.
    • Mixer or coin-join interactions, where applicable.
    • Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

    From the lectern — off-ramp identification:

    • Adal GROUP casefiles end at a centralised exchange — Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
    • Off-ramp wallet for Adal GROUP is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for Adal GROUP — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Adal GROUP casefile.

    Filing pathway — the next step after the off-ramp is identified:

    1. Submission triage — Adal GROUP casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — Adal GROUP deposit and forwarding wallets captured.
    3. Endpoint identification — Adal GROUP off-ramp wallet named.
    4. Filing — Adal GROUP packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — Adal GROUP stays on file until a documented next step is reached.

    What the on-chain reading covers:

    • Deposit-side chains in Adal GROUP casefiles — typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT) — with bridge crossings noted.
    • Off-ramps named in Adal GROUP packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Adal GROUP — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    Lines we never cross — by published policy:

    • Adal GROUP policy — seed phrases are never requested.
    • Adal GROUP policy — remote-access logins are never requested.
    • Adal GROUP policy — no upfront cash retainer to scope.
    • Adal GROUP policy — no guaranteed-recovery language. None.
    • Adal GROUP policy — no unsolicited calls. The Professor responds in writing only.

    Open a free consultation

    The Professor reads claims at no charge to begin — open a consultation at /contact-us/.

    Open a Free Case Consultation   Submit Wallet for Trace

    Why this platform is on our casefile

    Adal GROUP has been flagged as a fake broker/platform by IOSCO I-SCAN (Ukraine – National Securities and Stock Market Commission). reported 2024-03-12. Jurisdiction: Ukraine. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.iosco.org/i-scan/

  • Casefile Trust Vestify — The Professor’s Note

    // FROM THE CASEFILE — TRUST VESTIFY

    Trust Vestify, operating from trustvestify.com, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    Wallet trace — what the Professor maps:

    • Deposit-side hashes from claimant wallets into Trust Vestify’s receiving addresses.
    • Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
    • Inter-chain bridge transactions when value moves toward off-ramp liquidity.
    • Mixer/obfuscation events the operator routed through, where present.
    • Final off-ramp endpoint and named counterparty exchange.

    The annotation continues — off-ramp endpoint:

    • Off-ramp endpoint for Trust Vestify resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Trust Vestify’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Trust Vestify is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Trust Vestify off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

    Pathway to recovery — what happens after the trail is mapped:

    1. Read the Trust Vestify submission — written go/no-go returned.
    2. Map the Trust Vestify wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the Trust Vestify off-ramp — endpoint counterparty identified.
    4. Build and file the Trust Vestify recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the Trust Vestify file — until written next steps exist.

    Reading-list — chains and exchanges in scope:

    • Deposit + forwarding chains for Trust Vestify — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
    • Off-ramps the Trust Vestify casefile may resolve to — centralised exchanges that respond to compliance filings.
    • Filing pathways on Trust Vestify — IC3, state AG, off-ramp compliance, and civil-discovery overlay.

    What the Professor will never do — by policy:

    • Hard line on Trust Vestify — no seed-phrase requests, period.
    • Hard line on Trust Vestify — no remote logins requested.
    • Hard line on Trust Vestify — no upfront cash retainer.
    • Hard line on Trust Vestify — no guarantee language.
    • Hard line on Trust Vestify — no unsolicited phone outreach.

    Open a free consultation

    Open a free first consultation — /contact-us/ — written response within one business day.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: AmiusGroup

    // FROM THE CASEFILE — AMIUSGROUP

    AmiusGroup is a casefile under reading. The deposits to amiusgroupltd.com sit on-chain, immutable; the wallet pathway is the primary source, and the off-ramp endpoint is the conclusion the Professor’s marginalia points toward.

    Trace summary — funds that left amiusgroupltd.com:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for AmiusGroup.
    • Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
    • Bridge events into chains where the operator can off-ramp at scale.
    • Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
    • Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

    The Professor’s off-ramp note:

    • On the AmiusGroup casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
    • The off-ramp wallet for AmiusGroup is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the AmiusGroup casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, AmiusGroup escalates to IC3, state AG, and civil-discovery overlay.

    Pathway to recovery — what happens after the trail is mapped:

    1. Triage on AmiusGroup — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on AmiusGroup — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on AmiusGroup — off-ramp endpoint matched to a named exchange counterparty.
    4. File the AmiusGroup packet — IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
    5. Follow-through on AmiusGroup — the Professor stays on the casefile until a documented next step exists.

    Reading-list — chains and exchanges in scope:

    • Chains in scope for AmiusGroup — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
    • Off-ramps in scope for AmiusGroup — named centralised exchanges with compliance leverage.
    • Filings supported on AmiusGroup — IC3, state AG, off-ramp desk, civil discovery as applicable.

    What is never asked of a claimant:

    • Recovery scammers do these things on AmiusGroup; the Professor never does — request seed phrases.
    • Recovery scammers do these things on AmiusGroup; the Professor never does — request remote logins.
    • Recovery scammers do these things on AmiusGroup; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on AmiusGroup; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on AmiusGroup; the Professor never does — call you unsolicited.

    Open a free consultation

    Open a free first consultation — /contact-us/ — written response within one business day.

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: Orbimount

    // FROM THE CASEFILE — ORBIMOUNT

    Orbimount is a casefile under reading. The deposits to orbimount.io sit on-chain, immutable; the wallet pathway is the primary source, and the off-ramp endpoint is the conclusion the Professor’s marginalia points toward.

    Reading the wallets — Orbimount casefile:

    • Deposit confirmations from the claimant to Orbimount’s receiving wallet at orbimount.io.
    • Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
    • Cross-chain bridge transactions where the operator routed value out of the deposit chain.
    • Mixer or coin-join interactions, where applicable.
    • Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

    The Professor’s off-ramp note:

    • Orbimount off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Orbimount off-ramp address is matched to known compliance feeds — the Professor’s standing dataset plus chain-analytics references.
    • Compliance leverage is applied at the named counterparty for Orbimount — the packet meets the off-ramp’s published compliance standard.
    • When the Orbimount off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

    How a Orbimount casefile becomes a regulator-ready filing:

    1. First read on Orbimount — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on Orbimount — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for Orbimount is named to a centralised exchange wallet.
    4. Packet filing on Orbimount — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with Orbimount until a documented outcome or escalation step is on file.

    What the Professor tracks across Orbimount casefiles:

    • Chains the Orbimount casefile may touch — Bitcoin and Ethereum at the deposit side, Tron USDT-TRC20 in stablecoin pathways, BNB Smart Chain and the L2s (Arbitrum, Optimism, Polygon, Base) where bridges link them.
    • Off-ramps relevant to Orbimount — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the Orbimount packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

    Lines we never cross — by published policy:

    • What the Professor will not do on Orbimount — ask for a seed phrase.
    • What the Professor will not do on Orbimount — request remote-access logins.
    • What the Professor will not do on Orbimount — demand cash up front.
    • What the Professor will not do on Orbimount — promise a guarantee.
    • What the Professor will not do on Orbimount — call you out of the blue.

    Open a free consultation

    Bring the casefile to office hours — open a free consultation at /contact-us/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: Zentrox Trade

    // FROM THE CASEFILE — ZENTROX TRADE

    When deposits to Zentrox Trade via zentroxtrade.com go quiet, the on-chain record stays loud. The Professor’s reading begins where the platform’s silence does — with the wallet that received the funds and the path it took afterward.

    On-chain reading — wallet flow for Zentrox Trade:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Zentrox Trade.
    • Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
    • Bridge events into chains where the operator can off-ramp at scale.
    • Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
    • Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

    The annotation continues — off-ramp endpoint:

    • Zentrox Trade’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage — typically named in the packet alongside the deposit address.
    • Chain-analytics datasets cross-reference the Zentrox Trade off-ramp wallet against historical laundering throughput.
    • The Zentrox Trade packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for Zentrox Trade, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

    Recovery pathway — how this casefile moves toward filing:

    1. Triage on Zentrox Trade — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on Zentrox Trade — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on Zentrox Trade — off-ramp endpoint matched to a named exchange counterparty.
    4. File the Zentrox Trade packet — IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
    5. Follow-through on Zentrox Trade — the Professor stays on the casefile until a documented next step exists.

    What the Professor tracks across Zentrox Trade casefiles:

    • Deposit + forwarding chains for Zentrox Trade — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
    • Off-ramps the Zentrox Trade casefile may resolve to — centralised exchanges that respond to compliance filings.
    • Filing pathways on Zentrox Trade — IC3, state AG, off-ramp compliance, and civil-discovery overlay.

    Boundaries on every Zentrox Trade casefile — never crossed:

    • Hard line on Zentrox Trade — no seed-phrase requests, period.
    • Hard line on Zentrox Trade — no remote logins requested.
    • Hard line on Zentrox Trade — no upfront cash retainer.
    • Hard line on Zentrox Trade — no guarantee language.
    • Hard line on Zentrox Trade — no unsolicited phone outreach.

    Open a free consultation

    Send the wallet for trace — /submit-a-case/ — the Professor responds in writing.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on CGS International Securities

    // FROM THE CASEFILE — CGS INTERNATIONAL SECURITIES

    When a deposit ledgered to CGS International Securities at cgsi.com stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    Reading the wallets — CGS International Securities casefile:

    • Deposit confirmations from the claimant to CGS International Securities’s receiving wallet at cgsi.com.
    • Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
    • Cross-chain bridge transactions where the operator routed value out of the deposit chain.
    • Mixer or coin-join interactions, where applicable.
    • Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

    Off-ramp map — where the funds left the chain:

    • CGS International Securities off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The CGS International Securities off-ramp address is matched to known compliance feeds — the Professor’s standing dataset plus chain-analytics references.
    • Compliance leverage is applied at the named counterparty for CGS International Securities — the packet meets the off-ramp’s published compliance standard.
    • When the CGS International Securities off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

    Pathway to recovery — what happens after the trail is mapped:

    1. Casefile triage on CGS International Securities — the submission is read; a written assessment is delivered.
    2. Forensic trace on CGS International Securities — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the CGS International Securities endpoint is named.
    4. Recovery filing on CGS International Securities — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of CGS International Securities — the Professor follows the casefile until next-step documentation exists.

    What the casefile records — chains and counterparties:

    • Deposit + forwarding chains for CGS International Securities — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
    • Off-ramps the CGS International Securities casefile may resolve to — centralised exchanges that respond to compliance filings.
    • Filing pathways on CGS International Securities — IC3, state AG, off-ramp compliance, and civil-discovery overlay.

    Recovery scammers do these things; the Professor never does:

    • Hard line on CGS International Securities — no seed-phrase requests, period.
    • Hard line on CGS International Securities — no remote logins requested.
    • Hard line on CGS International Securities — no upfront cash retainer.
    • Hard line on CGS International Securities — no guarantee language.
    • Hard line on CGS International Securities — no unsolicited phone outreach.

    Open a free consultation

    Submit your wallet for a forensic reading — /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Website and Line “TDXM PRO — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

    The Professor opens the file on Website and Line “TDXM PRO the same way every casefile is opened — by treating the wallet history as text and the off-ramp endpoint as the citation a regulator can verify.

    From the marginalia — the deposit pathway:

    • Claimant-to-platform deposit transactions on the deposit chain used by Website and Line “TDXM PRO.
    • Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
    • Cross-chain bridge events to chains with deeper exchange liquidity.
    • Privacy-service interactions, where present in the trail.
    • Off-ramp wallet — the named centralised-exchange endpoint.

    From the lectern — off-ramp identification:

    • Website and Line “TDXM PRO off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Website and Line “TDXM PRO off-ramp address is matched to known compliance feeds — the Professor’s standing dataset plus chain-analytics references.
    • Compliance leverage is applied at the named counterparty for Website and Line “TDXM PRO — the packet meets the off-ramp’s published compliance standard.
    • When the Website and Line “TDXM PRO off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

    How a Website and Line “TDXM PRO casefile becomes a regulator-ready filing:

    1. First read on Website and Line “TDXM PRO — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on Website and Line “TDXM PRO — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for Website and Line “TDXM PRO is named to a centralised exchange wallet.
    4. Packet filing on Website and Line “TDXM PRO — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with Website and Line “TDXM PRO until a documented outcome or escalation step is on file.

    Reading-list — chains and exchanges in scope:

    • Deposit-side chains in Website and Line “TDXM PRO casefiles — typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT) — with bridge crossings noted.
    • Off-ramps named in Website and Line “TDXM PRO packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Website and Line “TDXM PRO — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    What is never asked of a claimant:

    • On the Website and Line “TDXM PRO casefile — never request a seed phrase. Ever.
    • On the Website and Line “TDXM PRO casefile — never request remote-access logins to a wallet or exchange.
    • On the Website and Line “TDXM PRO casefile — never demand an upfront cash retainer to scope the matter.
    • On the Website and Line “TDXM PRO casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the Website and Line “TDXM PRO casefile — never call the claimant unsolicited. Written-only.

    Open a free consultation

    Open a free first consultation — /contact-us/ — written response within one business day.

    Open a Free Case Consultation   Submit Wallet for Trace

    Why this platform is on our casefile

    Website and Line "TDXM PRO has been flagged as a fake broker/platform by IOSCO I-SCAN (Thailand – Securities and Exchange Commission). reported 2025-10-08. Jurisdiction: Thailand. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.iosco.org/i-scan/

  • CF Merchants — Annotated by the Professor

    // FROM THE CASEFILE — CF MERCHANTS

    When a deposit ledgered to CF Merchants at cfmerchants.com stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    On-chain reading — wallet flow for CF Merchants:

    • Deposit transaction hashes from the claimant wallet to the CF Merchants platform receiving address.
    • Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
    • Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
    • Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
    • Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

    Off-ramp summary — CF Merchants casefile:

    • On the CF Merchants casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
    • The off-ramp wallet for CF Merchants is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the CF Merchants casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, CF Merchants escalates to IC3, state AG, and civil-discovery overlay.

    Pathway to recovery — what happens after the trail is mapped:

    1. Triage on CF Merchants — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on CF Merchants — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on CF Merchants — off-ramp endpoint matched to a named exchange counterparty.
    4. File the CF Merchants packet — IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
    5. Follow-through on CF Merchants — the Professor stays on the casefile until a documented next step exists.

    What we read in a CF Merchants casefile:

    • Chains tracked on CF Merchants — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
    • Off-ramps tracked on CF Merchants — named exchange counterparties with public compliance contacts.
    • Filings supported on CF Merchants — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

    Boundaries on every CF Merchants casefile — never crossed:

    • Boundary on CF Merchants — seed phrases are off-limits.
    • Boundary on CF Merchants — remote logins are off-limits.
    • Boundary on CF Merchants — upfront cash retainers are off-limits.
    • Boundary on CF Merchants — guaranteed-recovery promises are off-limits.
    • Boundary on CF Merchants — unsolicited outbound contact is off-limits.

    Open a free consultation

    Book a reading of your wallet — file at /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Exodus Movement Inc

    // FROM THE CASEFILE — EXODUS MOVEMENT INC

    When a deposit ledgered to Exodus Movement Inc at exodus.com stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    Trace summary — funds that left exodus.com:

    • Deposit confirmations from the claimant to Exodus Movement Inc’s receiving wallet at exodus.com.
    • Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
    • Cross-chain bridge transactions where the operator routed value out of the deposit chain.
    • Mixer or coin-join interactions, where applicable.
    • Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

    Off-ramp map — where the funds left the chain:

    • On the Exodus Movement Inc casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
    • The off-ramp wallet for Exodus Movement Inc is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the Exodus Movement Inc casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, Exodus Movement Inc escalates to IC3, state AG, and civil-discovery overlay.

    Filing pathway — the next step after the off-ramp is identified:

    1. Casefile review on Exodus Movement Inc — reading the submission against the no-go list.
    2. Trace mapping on Exodus Movement Inc — pathway documented to chain-of-custody standard.
    3. Off-ramp naming on Exodus Movement Inc — exchange endpoint identified.
    4. Packet filing on Exodus Movement Inc — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
    5. Documented follow-through on Exodus Movement Inc.

    What the on-chain reading covers:

    • Chains the Exodus Movement Inc casefile may touch — Bitcoin and Ethereum at the deposit side, Tron USDT-TRC20 in stablecoin pathways, BNB Smart Chain and the L2s (Arbitrum, Optimism, Polygon, Base) where bridges link them.
    • Off-ramps relevant to Exodus Movement Inc — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the Exodus Movement Inc packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

    Recovery scammers do these things; the Professor never does:

    • Recovery scammers do these things on Exodus Movement Inc; the Professor never does — request seed phrases.
    • Recovery scammers do these things on Exodus Movement Inc; the Professor never does — request remote logins.
    • Recovery scammers do these things on Exodus Movement Inc; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on Exodus Movement Inc; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on Exodus Movement Inc; the Professor never does — call you unsolicited.

    Open a free consultation

    Send the wallet for trace — /submit-a-case/ — the Professor responds in writing.

    Open a Free Case Consultation   Submit Wallet for Trace