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

Category: Scam Brokers

Annotated readings of brokers and platforms the Cryptocurrency Professor has documented.

  • Reading the Chain: $PUN PUNISHER COIN

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to $PUN PUNISHER COIN 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 $PUN PUNISHER COIN:

    • Claimant-to-platform deposit transactions on the deposit chain used by $PUN PUNISHER COIN.
    • 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 $PUN PUNISHER COIN:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

    • Chains tracked on $PUN PUNISHER COIN — 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 $PUN PUNISHER COIN — named exchange counterparties with public compliance contacts.
    • Filings supported on $PUN PUNISHER COIN — 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 $PUN PUNISHER COIN casefile — never request a seed phrase. Ever.
    • On the $PUN PUNISHER COIN casefile — never request remote-access logins to a wallet or exchange.
    • On the $PUN PUNISHER COIN casefile — never demand an upfront cash retainer to scope the matter.
    • On the $PUN PUNISHER COIN casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the $PUN PUNISHER COIN 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

    $PUN PUNISHER COIN has been flagged as a fake broker/platform by IOSCO I-SCAN (Nigeria – Securities and Exchange Commission). reported 2025-08-25. Jurisdiction: Nigeria. 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 LevaQuant — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

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

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

    How a LevaQuant casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    LevaQuant has been flagged as a fake broker/platform by IOSCO I-SCAN (Italy – Commissione Nazionale per le Società e la Borsa). reported 2026-03-04. Jurisdiction: Italy. 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: Affiliatetradecoin24

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Affiliatetradecoin24 via affiliatetradecoin24.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 Affiliatetradecoin24:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

    • Chains tracked on Affiliatetradecoin24 — 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 Affiliatetradecoin24 — named exchange counterparties with public compliance contacts.
    • Filings supported on Affiliatetradecoin24 — 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 Affiliatetradecoin24 casefile — never request a seed phrase. Ever.
    • On the Affiliatetradecoin24 casefile — never request remote-access logins to a wallet or exchange.
    • On the Affiliatetradecoin24 casefile — never demand an upfront cash retainer to scope the matter.
    • On the Affiliatetradecoin24 casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the Affiliatetradecoin24 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

    Affiliatetradecoin24 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 SwayHorizonAI — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

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

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

    How a SwayHorizonAI casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    SwayHorizonAI has been flagged as a Fraudulent online trading platforms by FSMA Belgium. FSMA warning 30/06/2026. Jurisdiction: BE. 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.fsma.be/en/warnings/companies-operating-unlawfully-in-belgium

  • From the Lectern: BethleAsterFX

    // FROM THE CASEFILE — BETHLEASTERFX

    When deposits to BethleAsterFX via blafx.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.

    Wallet trace — what the Professor maps:

    • Deposit confirmations from the claimant to BethleAsterFX’s receiving wallet at blafx.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 reading — exchange counterparty for BethleAsterFX:

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

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

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

    Chains and off-ramps the Professor follows:

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

    Lines we never cross — by published policy:

    • What the Professor will not do on BethleAsterFX — ask for a seed phrase.
    • What the Professor will not do on BethleAsterFX — request remote-access logins.
    • What the Professor will not do on BethleAsterFX — demand cash up front.
    • What the Professor will not do on BethleAsterFX — promise a guarantee.
    • What the Professor will not do on BethleAsterFX — 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

  • Casefile Venus Capital — The Professor’s Note

    // FROM THE CASEFILE — VENUS CAPITAL

    Funds you sent to Venus Capital (venuscapitals.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.

    From the marginalia — the deposit pathway:

    • Deposit confirmations from the claimant to Venus Capital’s receiving wallet at venuscapitals.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 reading — exchange counterparty for Venus Capital:

    • Off-ramp endpoint for Venus Capital resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Venus Capital’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Venus Capital is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Venus Capital 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. Casefile triage on Venus Capital — the submission is read; a written assessment is delivered.
    2. Forensic trace on Venus Capital — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the Venus Capital endpoint is named.
    4. Recovery filing on Venus Capital — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of Venus Capital — the Professor follows the casefile until next-step documentation exists.

    What the casefile records — chains and counterparties:

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

    Lines the Professor will not cross:

    • Hard line on Venus Capital — no seed-phrase requests, period.
    • Hard line on Venus Capital — no remote logins requested.
    • Hard line on Venus Capital — no upfront cash retainer.
    • Hard line on Venus Capital — no guarantee language.
    • Hard line on Venus Capital — 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

  • Professor’s Brief: Lafanda LLC

    // FROM THE CASEFILE — LAFANDA LLC

    Lafanda LLC, operating from lafanda.net, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    From the marginalia — the deposit pathway:

    • Deposit-side hashes from claimant wallets into Lafanda LLC’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.

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

    • Off-ramp endpoint for Lafanda LLC resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Lafanda LLC’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Lafanda LLC is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Lafanda LLC 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. First read on Lafanda LLC — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on Lafanda LLC — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for Lafanda LLC is named to a centralised exchange wallet.
    4. Packet filing on Lafanda LLC — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with Lafanda LLC until a documented outcome or escalation step is on file.

    What the casefile records — chains and counterparties:

    • Chains the Professor reads for Lafanda LLC casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
    • Off-ramps named in Lafanda LLC — major centralised venues with compliance desks that accept regulator-grade packets.
    • Filing pathways available on Lafanda LLC — IC3 for US claimants, state AG offices, off-ramp compliance, and civil-discovery overlay for high-value loss.

    Boundaries on every Lafanda LLC casefile — never crossed:

    • Recovery scammers do these things on Lafanda LLC; the Professor never does — request seed phrases.
    • Recovery scammers do these things on Lafanda LLC; the Professor never does — request remote logins.
    • Recovery scammers do these things on Lafanda LLC; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on Lafanda LLC; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on Lafanda LLC; 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

  • Casefile HOTKEYFx — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

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

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

    How a HOTKEYFx casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    HOTKEYFx has been flagged as a fake broker/platform by IOSCO I-SCAN (Thailand – Securities and Exchange Commission). reported 2025-10-31. 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/

  • Casefile Fenix Securities — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

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

    • Fenix 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 Fenix 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 Fenix Securities — the packet meets the off-ramp’s published compliance standard.
    • When the Fenix Securities off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

    How a Fenix Securities casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    Fenix Securities 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/

  • Office Hours on IREM LLC – Exchange

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to IREM LLC – Exchange via iremllcfd.trade 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 iremllcfd.trade:

    • Deposit confirmations from the claimant to IREM LLC – Exchange’s receiving wallet at iremllcfd.trade.
    • 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:

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

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

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

    What the on-chain reading covers:

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

    Lines we never cross — by published policy:

    • IREM LLC – Exchange policy — seed phrases are never requested.
    • IREM LLC – Exchange policy — remote-access logins are never requested.
    • IREM LLC – Exchange policy — no upfront cash retainer to scope.
    • IREM LLC – Exchange policy — no guaranteed-recovery language. None.
    • IREM LLC – Exchange 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

    IREM LLC – Exchange has been flagged as a fake broker/platform by IOSCO I-SCAN (New Zealand – Financial Markets Authority). reported 2026-07-06. Jurisdiction: New Zealand. 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/