eventchecker-ht[.]netlify[.]app

This domain, eventchecker-ht.netlify.app, is identified as an active crypto phishing infrastructure designed to harvest wallet credentials and private keys. Analysis indicates the site mimics legitimate cryptocurrency verification portals, likely deploying a wallet drainer kit to exfiltrate funds upon user interaction. No specific brand impersonation has been confirmed, but the domain follows patterns consistent with generic credential theft targeting decentralized finance (DeFi) users. The infrastructure lacks overt branding, suggesting a broader, opportunistic phishing campaign rather than a targeted impersonation of a single entity. Technical indicators reveal the domain is hosted on Netlify’s platform and resolves to the IP address 63.176.8.218, geolocated in Germany under Amazon.com, Inc.’s AS16509. Despite its malicious intent, the domain has evaded detection by major scanning engines, with a VirusTotal score of 0/95. It appears on three security blocklists and is actively blocked by at least three independent threat intelligence feeds, including MetaMask’s internal systems. The domain’s registration details are obscured by Netlify’s hosting service, limiting visibility into its creation date or ownership. Google Safe Browsing (GSB) status remains unconfirmed at this time, though the domain’s presence on multiple blocklists suggests prior malicious activity. As of the latest verification, eventchecker-ht.netlify.app remains active and continues to pose a high risk to users. Response actions by security providers have included real-time blocking, but the domain’s persistence indicates ongoing evasion tactics. Users are advised to treat any interaction with this domain as malicious, particularly links or prompts requesting wallet credentials or seed phrases. Organizations should update firewall rules to deny traffic to 63.176.8.218 and monitor for related subdomains under netlify.app. Given the domain’s unflagged status on VirusTotal, reliance on traditional detection mechanisms may prove insufficient; proactive blocking based on threat intelligence feeds is recommended.