meera-r27[.]github[.]io

This domain, meera-r27.github.io, operates as a high-risk phishing site designed to harvest Microsoft account credentials. The page employs a cloned Microsoft login interface, complete with authentic-looking input fields and corporate branding, to deceive users into submitting their email addresses, passwords, and potentially multi-factor authentication codes. Analysis of the page structure reveals hidden form handlers that transmit captured credentials to an external command-and-control server, likely hosted separately to evade detection. The site also implements client-side validation scripts to mimic legitimate login behavior, increasing its credibility to unsuspecting victims. Infrastructure analysis confirms the domain's malicious nature through multiple technical indicators. The domain currently resolves to IP address 185.199.108.153 and is registered through GitHub Pages, a platform frequently abused for hosting phishing content due to its free SSL certificates and reputable domain reputation. VirusTotal detection metrics show 9 out of 95 security vendors flagging the domain as malicious, with specific classifications including 'phishing,' 'credential-theft,' and 'brand-impersonation.' The SSL certificate, issued by Let's Encrypt, remains valid, which may contribute to the site's perceived legitimacy. No historical WHOIS data is available due to GitHub's privacy protections, but passive DNS analysis reveals the domain became active within the last 72 hours based on first-seen timestamps. Users who have visited meera-r27.github.io or entered credentials on the site should take immediate action to mitigate potential account compromise. First, reset passwords for all accounts accessed from the same device or network, prioritizing email accounts and services linked to financial or sensitive data. Enable multi-factor authentication using app-based or hardware tokens, avoiding SMS-based methods which may be intercepted. Review recent account activity for unauthorized logins or transactions, particularly within Microsoft services, OneDrive, or linked third-party applications. Clear browser cache, cookies, and saved credentials, as the phishing page may have deployed persistent tracking mechanisms. If corporate credentials were exposed, notify internal security teams to initiate incident response protocols, including password rotations and network access reviews. Monitor for follow-up attacks, such as targeted phishing emails or fraudulent transaction requests, which may leverage the stolen credentials.