Loops HouseMimicwatch for NEAR: lookalike-account and phishing registry

NEAR HACKATHON
Links
Team
1 member- KAOwner
Kacper Gumieniuk
Overview
Scammers on NEAR use names that look like the projects users trust: lookalike accounts (linear_protocol.near next to linear-protocol.near), fake "rewards" tokens and clones of dApp sites. A wallet's send screen or an AI agent cannot tell them apart. Mimicwatch for NEAR finds them, has a person review them, and publishes the confirmed ones to an on-chain registry that any wallet or agent queries with one view call before it sends funds or opens a link. The scanner generates 30k lookalikes of 72 official accounts of 34 NEAR dApps (NEAR ids are ASCII-only, so the tricks are confusable letters, separators, lure words and fake sub-accounts), checks which exist with RPC view_account, and scores each from on-chain facts via free FastNEAR indexers: creator, age, keys, contract, token metadata, holders, who paid it. Address-poisoning dust and brand-owned names are labelled, not flagged. Lookalike domains come from our existing Mimicwatch engine. First scan (2026-11-01): 507 lookalikes exist, including a fake-airdrop campaign of three NEP-141 tokens named after LiNEAR, Meta Pool and Burrow held by 2,205, 9,434 and 7,079 accounts, and a Rhea app clone asking for seed phrases that no wallet blocklist had listed. Nothing publishes itself: only reviewed high/critical findings are written to the registry contract (Rust, NEAR testnet) with the sha256 of their evidence. is_flagged(id) also covers sub-accounts and subdomains of flagged entries; anyone can dispute an entry with a deposit (BLOCK becomes WARN), and the owner keeps or clears it. An SDK, CLI, HTTP API and an MCP tool (check_near_recipient) return ALLOW/WARN/BLOCK with reasons. Live now: 33 reviewed findings (the three fake tokens, the Rhea clone and 29 more phishing domains) are in the testnet registry.