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

Tag: report a scam

  • Casefile TEAMTRUSTFX — The Professor’s Note

    // FROM THE CASEFILE — TEAMTRUSTFX

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

    From the marginalia — the deposit pathway:

    • Deposit transaction hashes from the claimant wallet to the TEAMTRUSTFX 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 map — where the funds left the chain:

    • TEAMTRUSTFX’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 TEAMTRUSTFX off-ramp wallet against historical laundering throughput.
    • The TEAMTRUSTFX packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for TEAMTRUSTFX, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

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

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

    What the Professor tracks across TEAMTRUSTFX casefiles:

    • Chains the TEAMTRUSTFX 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 TEAMTRUSTFX — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the TEAMTRUSTFX 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:

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

    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

  • Clone NumisFX — Annotated by the Professor

    // FROM THE CASEFILE — CLONE NUMISFX

    Clone NumisFX is a casefile under reading. The deposits to numisfx.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 — Clone NumisFX casefile:

    • Claimant-to-platform deposit transactions on the deposit chain used by Clone NumisFX.
    • 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.

    The annotation continues — off-ramp endpoint:

    • Clone NumisFX 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 Clone NumisFX is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for Clone NumisFX — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Clone NumisFX casefile.

    The Professor’s recovery note for Clone NumisFX:

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

    What the casefile records — chains and counterparties:

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

    Boundaries on every Clone NumisFX casefile — never crossed:

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

    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

  • CryptSparkFx — Annotated by the Professor

    // FROM THE CASEFILE — CRYPTSPARKFX

    The Professor opens the file on CryptSparkFx 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.

    Wallet trace — what the Professor maps:

    • Initial deposit hashes to the CryptSparkFx receiving address at cryptsparkfx.com.
    • Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
    • Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
    • Obfuscation events through mixer contracts and privacy services.
    • Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

    From the lectern — off-ramp identification:

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

    The Professor’s recovery note for CryptSparkFx:

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

    What we read in a CryptSparkFx casefile:

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

    Lines the Professor will not cross:

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

    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

  • Reading the Chain: American First City Corporation

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to American First City Corporation via americanfirstcitycorp.net 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 American First City Corporation:

    • Claimant-to-platform deposit transactions on the deposit chain used by American First City Corporation.
    • 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.

    Off-ramp reading — exchange counterparty for American First City Corporation:

    • American First City Corporation 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 American First City Corporation is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for American First City Corporation — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the American First City Corporation casefile.

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

    • Chains tracked on American First City Corporation — 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 American First City Corporation — named exchange counterparties with public compliance contacts.
    • Filings supported on American First City Corporation — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

    Why this platform is on our casefile

    American First City Corporation has been flagged as a fake broker/platform by IOSCO I-SCAN (United States of America – Securities and Exchange Commission). reported 2026-06-04. Jurisdiction: United States of America. 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 Vega Gainlux — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

    The Professor opens the file on Vega Gainlux 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 Vega Gainlux.
    • 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:

    • Vega Gainlux off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Vega Gainlux 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 Vega Gainlux — the packet meets the off-ramp’s published compliance standard.
    • When the Vega Gainlux off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

    How a Vega Gainlux casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

    • Deposit-side chains in Vega Gainlux 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 Vega Gainlux packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Vega Gainlux — 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 Vega Gainlux casefile — never request a seed phrase. Ever.
    • On the Vega Gainlux casefile — never request remote-access logins to a wallet or exchange.
    • On the Vega Gainlux casefile — never demand an upfront cash retainer to scope the matter.
    • On the Vega Gainlux casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the Vega Gainlux 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

    Vega Gainlux has been flagged as a fake broker/platform by IOSCO I-SCAN (Sweden – Finansinspektionen). reported 2026-06-09. Jurisdiction: Sweden. 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/

  • From the Lectern: ADSS Market

    // FROM THE CASEFILE — ADSS MARKET

    ADSS Market is a casefile under reading. The deposits to addsmarkets.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.

    On-chain reading — wallet flow for ADSS Market:

    • Claimant-to-platform deposit transactions on the deposit chain used by ADSS Market.
    • 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.

    Off-ramp reading — exchange counterparty for ADSS Market:

    • On the ADSS Market 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 ADSS Market is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the ADSS Market casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, ADSS Market escalates to IC3, state AG, and civil-discovery overlay.

    Recovery pathway — how this casefile moves toward filing:

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

    What the casefile records — chains and counterparties:

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

    Lines the Professor will not cross:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • From the Lectern: Superfxtrading

    // FROM THE CASEFILE — SUPERFXTRADING

    Funds you sent to Superfxtrading (superfxtrading.com) are still recorded on the public ledger; the question is no longer whether the money moved but where the off-ramp opened — and that is what the Professor reads.

    The annotation reads — wallet trace:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Superfxtrading.
    • 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.

    Off-ramp summary — Superfxtrading casefile:

    • Superfxtrading off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Superfxtrading 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 Superfxtrading — the packet meets the off-ramp’s published compliance standard.
    • When the Superfxtrading off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

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

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

    What the Professor tracks across Superfxtrading casefiles:

    • Chains the Superfxtrading 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 Superfxtrading — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the Superfxtrading 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:

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

    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: Swift Trades

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Swift Trades via https: 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 Swift Trades:

    • Claimant-to-platform deposit transactions on the deposit chain used by Swift Trades.
    • 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.

    Off-ramp reading — exchange counterparty for Swift Trades:

    • Swift Trades 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 Swift Trades is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for Swift Trades — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Swift Trades casefile.

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

    • Chains tracked on Swift Trades — 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 Swift Trades — named exchange counterparties with public compliance contacts.
    • Filings supported on Swift Trades — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

    Why this platform is on our casefile

    Swift Trades has been flagged as a fake broker/platform by IOSCO I-SCAN (British Columbia – British Columbia Securities Commission). reported 2026-06-25. Jurisdiction: British Columbia. 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/

  • Reading the Chain: Metaglobal Brokers

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Metaglobal Brokers via https: 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 Metaglobal Brokers:

    • Claimant-to-platform deposit transactions on the deposit chain used by Metaglobal Brokers.
    • 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.

    Off-ramp reading — exchange counterparty for Metaglobal Brokers:

    • Metaglobal Brokers 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 Metaglobal Brokers is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for Metaglobal Brokers — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Metaglobal Brokers casefile.

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

    • Chains tracked on Metaglobal Brokers — 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 Metaglobal Brokers — named exchange counterparties with public compliance contacts.
    • Filings supported on Metaglobal Brokers — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

    Recovery scammers do these things; the Professor never does:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

    Why this platform is on our casefile

    Metaglobal Brokers has been flagged as a fake broker/platform by IOSCO I-SCAN (British Columbia – British Columbia Securities Commission). reported 2026-06-25. Jurisdiction: British Columbia. 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/

  • Office Hours on swiftglobaltrade

    // FROM THE CASEFILE — SWIFTGLOBALTRADE

    The Professor opens the file on swiftglobaltrade 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.

    On-chain reading — wallet flow for swiftglobaltrade:

    • Deposit transaction hashes from the claimant wallet to the swiftglobaltrade 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.

    The Professor’s off-ramp note:

    • swiftglobaltrade off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The swiftglobaltrade 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 swiftglobaltrade — the packet meets the off-ramp’s published compliance standard.
    • When the swiftglobaltrade off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

    The Professor’s recovery note for swiftglobaltrade:

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

    What the casefile records — chains and counterparties:

    • Deposit-side chains in swiftglobaltrade 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 swiftglobaltrade packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on swiftglobaltrade — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    Lines the Professor will not cross:

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

    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