🕵️ OSINT Phishing Investigation: Case Study Report


Foreword

All names/contacts were replaced for privacy concerns, and pictures of any methods are not provided for the same reasons. This is not a highly technical investigation; it was more of a personal exercise in practicing OSINT with an actual application and relevance to a real-world scenario (not just a home lab or experimentation with tools).


Brief

An employee, John Doe, was solicited on WhatsApp by someone impersonating the CEO of CompanyX, Mark Smith. The conversation progressed into a request for John Doe to speak with a company-unaffiliated lawyer, Edward Lam, and keep the conversation confidential. The employee became suspicious and escalated the matter to management for verification. The incident was subsequently reported in an email chain with attached pictures and references to the conversation.


Social Engineering Method


Conversation Timeline

  1. Initial Contact: The attacker messaged John Doe on WhatsApp, claiming to be Mark Smith. The attacker immediately began making a request for John Doe's involvement in a fake financial move for CompanyX.
  2. Engagement: The conversation included discussions about a supposed acquisition. The attacker encouraged John Doe to keep the information confidential.
  3. Escalation: The attacker requested John Doe speak to a lawyer named Edward Lam to finalize financial arrangements.
  4. Suspicion: John Doe found the conversation suspicious and escalated it to management.

Tactics Observed


Possible Inspiration


Names and Roles


Companies


Evidence and Findings

Sources included people search sites, Google queries, and relevant articles. Have I Been Pwned was used to check for possible email compromises.

John Doe, Edward Lam, and Martha Carter all had their emails compromised in the following breaches:


Conclusion

The threat actors likely accessed leaked data to identify and target CompanyX. While the exact motivation remains unclear, the attackers demonstrated a working knowledge of CompanyX’s acquisition history and key personnel. Their tactics suggest deliberate use of public information and compromised credentials to craft a believable phishing attack. This case highlights the importance of safeguarding personal information and regularly monitoring data breach exposure. Organizations should maintain strong awareness of their public footprint and conduct tabletop exercises to strengthen resilience.


Potential Next Steps for Further Investigation

  1. Analyze the attacker’s language and style for possible attribution, including links to known Advanced Persistent Threat (APT) groups.
  2. Investigate additional breaches involving CompanyX employees to gather comprehensive intelligence.
  3. Provide spear-phishing awareness training for employees, supplemented with practical exercises and case studies.