Fake Incident Reports in Phishing: A Case Study of a Poorly Crafted Campaign

In mid-February 2026, cybersecurity analysts identified a new phishing campaign that attempts to manipulate victims by leveraging a bogus “security incident report” PDF hosted on Amazon Web Services (AWS) infrastructure. Unlike more sophisticated scams seen in recent years, this campaign stands out for its rudimentary execution and glaring quality issues — yet it highlights enduring social engineering techniques that remain effective against unsuspecting users.

Anatomy of the Scam

The threat actors behind this campaign distributed phishing emails purporting to be a warning related to suspicious account activity. The email contains a link to a page on an AWS S3 bucket, where a PDF titled Security_Reports.pdf is available for download. This document supposedly outlines unusual login activity for the recipient’s account and urges action — specifically, enabling two-factor authentication (2FA) to secure it.

From a technical standpoint, several aspects of this campaign reveal its low quality:

  • Unbranded PDF Content: The attached PDF was generated using a generic reporting tool (ReportLab) and is not personalized with the recipient’s information, nor does it bear any recognizable corporate branding. This lack of personalization is a hallmark of low-effort phishing lures.
  • Non-spoofed Sender: The email’s “From” address is not convincingly forged. In many advanced phishing campaigns, attackers spoof legitimate domains or closely mimic trusted senders to bypass basic user skepticism; here, the absence of such spoofing reduces the likelihood of success.
  • No Malicious Payload: The PDF itself is not inherently harmful — it contains no malware or direct exploit code. The threat lies in the psychological pressure it attempts to create, encouraging victims to click through and potentially disclose credentials or enable features under false pretenses.

Target and Objective

According to the security consultant who reported the campaign, this phishing attempt is aimed primarily at users of MetaMask — a popular cryptocurrency wallet extension. By invoking the fear of unauthorized access, the attackers prompt users to take action that could inadvertently expose sensitive credentials or allow attackers to compromise accounts indirectly.

The goal, at its core, is typical of phishing: to elicit an emotional reaction and drive the victim toward an action that benefits the scammer, such as credential theft or installation of unwanted software. In this case, the requested action — enabling 2FA — could be part of a broader credential harvesting scheme.

Why It Matters

Phishing remains one of the most prevalent vectors for cybercrime globally. By disguising malicious intent within seemingly legitimate communication, attackers exploit human psychology rather than technical vulnerabilities. Security firms consistently classify phishing as a major threat because it often succeeds without requiring technical exploits, instead relying on deception and urgency.

Even though this particular campaign was poorly structured — making it easier to identify and dismiss for vigilant users — it underscores several key points:

  • Social Engineering Is Still Effective: Scammers can achieve results purely through manipulative messaging, without needing sophisticated malware or exploits.
  • User Awareness Is Critical: Many phishing emails can be detected through basic indicators such as unexpected attachments, generic content, or unusual sender information.
  • Technical Controls Aren’t Enough: Organizations and individuals must adopt layered defenses — including training, email filtering, and authentication protocols — to mitigate phishing threats.

Technical Considerations and Preventive Measures

From a cybersecurity architecture perspective, defending against phishing requires both user education and robust technical controls:

  • Email Filtering and DMARC Enforcement: Implementing Domain-based Message Authentication, Reporting, and Conformance (DMARC) policies can reduce the chance of spoofed emails reaching end users.
  • Multi-Factor Authentication: While 2FA is generally a strong security control, users must be wary of unsolicited prompts to “enable” or “upgrade” it unless initiated through known legitimate channels.
  • URL and Attachment Scrutiny: Training users and deploying automated tools to assess URLs and attached documents for legitimacy can preempt credential harvesting attempts.

Conclusion

Phishing attacks evolve constantly, but the underlying premise remains the same: trick users into lowering their guard. This poorly crafted campaign serves as a reminder that attackers are willing to use even low-effort tactics in pursuit of sensitive information. The resilience of phishing underscores the importance of comprehensive cybersecurity education, vigilant system design, and strategic defensive technologies.