CIGO token icon evidence labels COSIGO public record
COSIGO Public Record
MetaMask record and wallet-side restrictions
Independent COSIGO public record. No affiliation with MetaMask, Consensys, Blockaid, CertiK, PancakeSwap, BscScan, BNB Chain, or any third-party scanner, wallet, exchange, or data provider. This page documents COSIGO’s position, observations, and evidence requests.

MetaMask record

Timeline, support conduct, owner-wallet friction, non-owner inconsistency, and interface-layer restriction around CIGO.

Back to overview Evidence log

MetaMask record

CIGO contract source is public, verified, and inspectable. Despite that, MetaMask maintained a malicious label without providing a clear technical remediation path.

  • April 27, 2026: MetaMask Support stated that malicious flag would not be removed and referred to “known risky/malicious features,” but did not identify a specific contract function, permission, scanner rule, transaction behavior, or remediation path.
  • Later support chat: MetaMask referred CIGO to external scanner findings rather than providing a direct MetaMask standard or exact technical remediation path. In documented chat shown in this record, TokenSniffer was explicitly referenced. CertiK findings are included separately in this record as a public scanner reference.
  • Follow-up support response: MetaMask stated: “I'm not here to tell you how to make a scam token appear safe,” ended further assistance on same matter, and indicated future chat access would be removed for this issue.
  • April 29, 2026 — observed interface restriction: MetaMask no longer allowed normal click-through interaction with CIGO contract warning flow in browser-based owner/admin use.
  • Subsequent MetaMask test: A separate non-owner MetaMask wallet was able to complete a CIGO to USDT swap successfully, while owner/admin interaction and contract-warning click-through behavior remained restrictive. This suggests inconsistent or context-specific treatment rather than a total token-wide disablement.
  • April 29, 2026 — switch to Rabby Wallet for connectivity: CIGO contract remained operable through alternate EVM wallet infrastructure. Rabby connected and simulated owner/admin calls correctly, confirming that restriction was wallet-side rather than an on-chain failure of contract itself. Contract remained functional; blockage appeared at interface layer.
A malicious designation carries serious reputational weight. If a verified public contract is labeled malicious, any party applying or surfacing that label should identify exact technical basis and exact remediation path.