boadocument[.]weebly[.]com

This domain, boadocument[.]weebly[.]com, operates as a credential harvesting platform designed to mimic legitimate Bank of America secure document portals. Analysis indicates the site presents a counterfeit login interface under the page title 'BOA SECURED DOCUMENT - Home,' targeting customers of the financial institution to capture sensitive authentication details such as usernames, passwords, and potentially multi-factor authentication codes. The fraudulent nature of the site extends to its infrastructure, which employs deceptive design elements to create an illusion of legitimacy, including the use of reCAPTCHA and SSL encryption via Let's Encrypt to lower user suspicion. Infrastructure analysis reveals multiple technical indicators confirming malicious intent. The domain was registered through MarkMonitor, Inc. on March 29, 2006, though the phishing content appears to have been deployed more recently. Detection engines on VirusTotal flagged the domain as malicious, with 16 out of 95 security vendors identifying it as a phishing threat. The site resolves to the IP address 74.115.51.8 and is hosted on Weebly’s platform, leveraging technologies such as PHP, MySQL, and Amazon Web Services for backend operations. Additionally, the domain appears on two security blocklists and is categorized under 'SOCIAL_ENGINEERING' by Google Safe Browsing, further corroborating its fraudulent purpose. Individuals who have visited boadocument[.]weebly[.]com or entered credentials on the site should take immediate action to mitigate potential compromise. First, affected users must change their Bank of America login credentials from a secure device, ensuring the new password is unique and complex. Multi-factor authentication should be enabled if not already active. Users are advised to monitor their financial accounts for unauthorized transactions and report any suspicious activity to their financial institution. Device scans using updated security tools are recommended to detect potential malware infections. Finally, affected parties should report the phishing domain to relevant authorities, such as the Anti-Phishing Working Group or the Federal Trade Commission, to aid in broader mitigation efforts.