Aavegotchi GHST Honeypot Flag: What On-Chain Data Can Show

Two automated security scanners returned opposite verdicts on the same official Aavegotchi GHST contract on Ethereum on September 11, 2026, with GoPlus Security flagging address 0x3F382DbD960E3a9bbCeaE22651E88158d2791550 as a honeypot even as Honeypot.is classified the identical token as low-risk with a 0% simulated sell tax, leaving the "Aavegotchi GHST honeypot flag" unresolved rather than proven. The disagreement matters because a honeypot label signals a token buyers can acquire but cannot sell, and a false positive on a token listed on both Binance and Coinbase carries reputational weight disproportionate to any verified on-chain harm. No exploit, loss figure, or first-alert date has been established from the evidence reviewed here. For related coverage, see Ripple Adds AI Agents to Treasury Platform Acquired for $1B. What was flagged, and which GHST contract does it concern? The canonical Ethereum GHST contract is 0x3F382DbD960E3a9bbCeaE22651E88158d2791550, an address the official Aavegotchi token page and Etherscan both identify as the "Aavegotchi: GHST Token," matching the on-chain token name "Aavegotchi GHST Token" returned by both scanners. For related coverage, see Bitget API Adds CFD Trading for Gold, Forex and Stock Indices. At 09:37:26 UTC on September 11, 2026, GoPlus Security returned is_honeypot='1' for that address on chain ID 1, the verified contract on Etherscan showing open-source code and eight active Uniswap and SushiSwap liquidity pools. That flag confirms a scanner classification, not a demonstrated exploit or universal inability to sell. For related coverage, see ChatGPT for Financial Services: What Happens to Junior Bankers?. GoPlus Ethereum GHST honeypot flag 1 GoPlus returned is_honeypot='1' at 2026-09-11 09:37:26 UTC for the official Ethereum GHST contract. This confirms a scanner flag, not an exploit or universal inability to sell. Honeypot.is returned isHoneypot=false. The linked explorer provides contract context; the scanner observation comes from the supplied research API snapshot. The scope is Ethereum only. The official page separately lists a Polygon contract at 0x385eeac5cb85a38a9a07a70c73e0a3271cfb54a7 and a Base contract at 0xcD2F22236DD9Dfe2356D7C543161D4d260FD9BcB, and the Ethereum scanner results cannot be generalized to those deployments. A shared ticker or token name never establishes contract identity; only a chain-and-address match against an authoritative reference does. The GoPlus response also returned owner_change_balance='1', transfer_pausable='1' and external_call='1', while reporting buy_tax='0', sell_tax='0' and, notably, cannot_sell_all='0'. Those secondary fields describe code capabilities the scanner detected; the response supplied no failing trace or causal explanation for the honeypot classification itself. The bonding-curve token behind the warning GHST launched on Ethereum in 2020 through a bonding curve that closed in March 2023, capping supply at a figure the official page now displays as 52,747,802 tokens, closely matching the 52,747,802.71 total supply both scanners read on-chain.