Phishing false-positive remediation
This record documents why the official CrownFi hostname is requesting human blocklist review, what was audited, and what was hardened on September 3, 2026.
Verified scope
- Official hostname
- stellar-crown-fi-ap-jr77.vercel.app
- Network
- Stellar Testnet; no real-value assets
- Wallet providers
- Freighter and optional Privy authentication
- Secret handling
- No recovery phrase, seed phrase, private key, or wallet password collection
Listing timeline
The exact hostname was absent from MetaMask’s configuration at commit c956215 on August 26, 2026 at 17:11:28 UTC. It first appeared three minutes later in automated synchronization commit d5f88c9, authored by security-alliance-bot. The public synchronization PR does not include a malicious path, captured credential form, transaction hash, impersonated brand, malware sample, or reporter evidence for this hostname. ChainPatrol lists this exact subdomain as blocked while the parent vercel.app asset is allowed.
Audit and remediation
- Upgraded Next.js, Stellar SDK, Privy, Sharp, PostCSS, and vulnerable transitive packages; complete and production npm audits report zero known vulnerabilities.
- Replaced deprecated Privy server authentication with the maintained Privy Node SDK.
- Bound fan and admin wallet challenges to exact server-generated content, address, expiry, and canonical deployment origin.
- Added same-origin protection for unsafe browser API requests and fail-closed PayMongo webhook verification with timestamp freshness checks.
- Decode and re-encode uploaded PNG, JPEG, and WebP files; reject unsupported formats and apply upload rate limits.
- Published CSP, HSTS, anti-framing, MIME-sniffing, referrer, permissions, and cross-domain-policy headers.
- Removed nonfunctional social links, a simulated newsletter response, raw authentication errors, and user-identifying debug logs.
Local validation passed TypeScript checks, Merkle receipt tests, security regression tests, both npm audits, and the optimized production build. Live validation confirmed HTTP 200 for the trust page, security.txt, robots, and sitemap; cross-site API mutation attempts return HTTP 403. Freighter and Privy remain available, and Privy’s real login dialog loads under the deployed Content Security Policy.
Request to security providers
Please perform a human review and remove this official hostname from the ChainPatrol, SEAL, and MetaMask blocklists. If non-public incident evidence exists, please provide the owner with a sanitized path, timestamp, or indicator so it can be investigated and remediated.
