A scammer posing as GCI's CFO emailed payroll and, after the employee's initial pushback, persuaded them to hand over 2015 W-2s for every GCI.
Social Engineering Examples·5 sources
In February 2016, GCI's payroll department received an email in which a third party impersonated the company's chief financial officer (identified in press reporting as CFO Pete Pounds) and requested copies of the W-2 Wage and Tax Statement forms for everyone who worked for GCI during calendar year 2015. According to GCI's own breach notification, the payroll employee who received the message "correctly questioned the request as unusual," but the impersonator persisted, and the employee ultimately emailed the requested W-2 information to the outside party on February 24, 2016. GCI discovered the disclosure on March 3, 2016 and notified employees and regulators shortly after.
The company believes the 2015 W-2s of all employees who worked for GCI, Denali Media, UUI and Unicom at any time during 2015 were disclosed. Each W-2 included the person's Social Security number, name and address, and 2015 income and tax-withholding information. GCI emphasized that no IT systems or networks were breached and no customer information was affected.
This was a real, documented incident, confirmed by GCI's breach-notification letter filed with the Montana Department of Justice and corroborated by contemporaneous reporting.
This is a business email compromise (BEC) variant known as CEO/CFO-spoof W-2 phishing. Rather than deploying malware or breaking into systems, the attacker abused trust and authority: an email crafted to appear to come from a senior executive asked a payroll staffer for a bulk of sensitive tax documents. It succeeded because the request came, apparently, from a known, high-ranking person; because tax season made a request for W-2s plausible; and because the attacker applied social pressure.
Notably, the employee's instincts were correct: they flagged the request as unusual. The failure was that the doubt was resolved by continued email exchange with the attacker instead of by out-of-band verification (a phone call or in-person check with the real CFO). The attacker's persistence overcame the initial hesitation.
Lure: an email purporting to be from GCI's CFO asking payroll to send the full set of 2015 employee W-2 forms. Tells: an executive making an unusual bulk data request over email; pressure and insistence when questioned; a request routed to a single payroll employee rather than through normal channels; and timing during tax-filing season when W-2 requests can seem routine.
The reliable defense is out-of-band verification of any executive request for bulk employee or financial data, using a known phone number or in-person contact, never by replying to the email itself.
GCI's incident response team interviewed the relevant employees, preserved evidence, and notified the FBI. The company notified all affected employees, filed breach notifications with state authorities, and offered two years of free AllClear ID credit monitoring, identity-theft counseling, and identity-theft insurance. Employees were urged to file IRS Form 14039 (Identity Theft Affidavit) to guard against fraudulent 2015 tax returns.
GCI said it would strengthen protections and launch an anti-phishing training program. No public attribution or arrest followed. The incident was one of 41+ organizations hit by W-2 BEC phishing in Q1 2016, a wave that prompted an IRS payroll/HR alert (IR-2016-34).
The GCI case is a textbook example of why W-2/payroll phishing is dangerous and why human vigilance alone is not enough. The targeted employee actually recognized the request as suspicious yet still complied under persistence, showing that awareness must be paired with a mandatory verification procedure that removes judgment-under-pressure from the equation.
A single successful email exposed the SSNs and income data of thousands of people, with no malware and no network intrusion, making it cheap for attackers and devastating for victims. It also sits within a documented 2016 epidemic of executive-spoof W-2 scams serious enough to trigger a federal IRS warning, underscoring that this is a repeatable, industrialized tactic rather than a one-off.
Require out-of-band verification (phone or in-person to a known contact) for any request for bulk W-2, payroll, or employee PII, regardless of who appears to be asking. Establish a policy that no single employee can release mass sensitive data on email authority alone; route such requests through a defined approval workflow. Deploy email authentication (SPF/DKIM/DMARC) and display-name/lookalike-domain warnings to flag executive impersonation.
Give payroll/HR and finance targeted anti-phishing and BEC training with a psychologically safe path to escalate and refuse suspicious requests, so persistence pressure cannot override initial doubt. Minimize and encrypt stored W-2/PII, and pre-plan breach response (IRS Form 14039 guidance, credit monitoring) so victims can act fast.
Social Engineering Examples. “GCI (Alaska telecom) W-2 phishing: CFO-spoof email drained 2,500+ employees' tax data”. Accessed 19 September 2026. https://socialengineeringexamples.com/gci-w2-ceo-spoof-phish-2016
BEC operators running CEO/CFO-spoof W-2 campaigns typically identify a target company's finance leadership (the real CFO's name and title) and its payroll or HR contacts through public sources such as the corporate website, press coverage, and professional-networking profiles, then infer which internal mailbox is likely to process bulk employee tax paperwork.
Public exposure of a company's CFO name and payroll/HR contact structure is very hard to eliminate at enterprise scale; the realistic control assumes attackers already have this and hardens the process it later gets used against (see Stage 3), rather than trying to hide organizational information that is often legitimately public.
the attacker sets up a sender identity designed to pass a quick glance, typically a spoofed or look-alike display name and reply-to address made to resemble the CFO's real one, and drafts a request written in an executive's plausible voice and vocabulary.
Email authentication controls (SPF, DKIM, DMARC) and inbox warnings for spoofed display names or lookalike domains can flag or block a forged executive sender before the message ever reaches the payroll inbox.
the attacker sends the spoofed email to the payroll employee during tax-filing season, when a request for bulk W-2 data is more likely to read as a routine, time-sensitive business ask rather than an anomaly.
A standing policy that any bulk request for W-2s, payroll data, or employee PII requires out-of-band verification, regardless of season or apparent urgency, removes the advantage the attacker gets from timing the request to tax season.
when the employee questions the unusual bulk request, as GCI's payroll staffer did, the attacker replies with continued insistence rather than any verifiable proof of identity, relying on authority and persistence pressure to outlast the employee's doubt.
Give payroll and finance staff a psychologically safe, clearly defined escalation path and a two-person or manager sign-off rule for sensitive data releases, so an employee's initial correct instinct cannot be overridden by a single attacker's persistence.
the employee, having exhausted their hesitation without seeking out-of-band confirmation, emails the requested 2015 W-2 files (SSNs, names, addresses, income and withholding data) directly to the attacker-controlled address.
Data-loss-prevention rules that flag or block bulk SSN-pattern attachments leaving via email to unverified external recipients, combined with minimizing and encrypting stored W-2/PII, can catch or slow the exfiltration step itself.
the attacker uses the stolen Social Security numbers and income data for the documented downstream purposes GCI itself flagged, most likely fraudulent federal tax-refund filings and/or fraudulent credit or identity-theft schemes, completing the attacker's objective with no need to ever touch GCI's networks or systems.
Once SSNs and income data have left the organization, there is no technical control that un-does the exposure; the nearest realistic response is the pre-planned breach-response playbook GCI actually used, fast IRS Form 14039 identity-theft-affidavit guidance and credit monitoring for victims, which limits harm rather than preventing it.
Browse by what this case has in common with others in the library.
A Snap Inc. payroll employee emailed the W-2 and payroll data of roughly 700 current and former employees to an…
A spoofed email impersonating Seagate's CEO tricked an HR/payroll employee into emailing every 2015 W-2 to a scammer.
A fraudster impersonating CEO Rob Mee tricked a Pivotal employee into emailing back the W-2 tax data of the company's…
A blogger paid $89.95 to an online data broker (CellTolls.com) to buy retired Gen. Wesley Clark's cell-phone call log obtained…
Fraudsters built a fake WhatsApp profile of WPP CEO Mark Read and staged a Microsoft Teams call using an AI…
Scheme participants posed as veteran finance professionals inside private WhatsApp investment groups to lure at least 18 U.S. retail investors…
A Russian-speaking threat actor used disposable, one-conversation ChatGPT accounts to iteratively build and debug a Go-based Windows malware family.
A single spear-phishing email titled "2011 Recruitment Plan," with a booby-trapped Excel attachment.
Evaldas Rimasauskas ran a five-year, $120M fraud against Google and Facebook using forged Quanta Computer invoices.
Fugitive hacker Kevin Mitnick impersonated a vacationing Novell employee on a "top-secret" project.
A Telegram/dark-web "blackhat ChatGPT" sold $200/month subscriptions promising AI-generated phishing pages, malware and BEC lures.
Attackers stood up a real Azure subscription and Azure Monitor alert rule to make Microsoft's own mail servers send a…
A Lapsus$ affiliate bought a contractor's stolen Uber password, flooded them with MFA push prompts, then posed as Uber IT…
An interstate Indian gang used AI-generated "eye-blink" deepfake videos made from stolen social-media photos to fool Aadhaar's facial-liveness e-KYC.
Between 2000 and 2009, GAO undercover investigators repeatedly used fake law-enforcement badges (and, in a related 2009 test.
A retired New Jersey man lost $390,000 in two days after a fake Norton/PayPal refund call escalated into a bogus…
A US Attorney's Office (EDVA) court order seized seven domains spoofing the Singapore International Monetary Exchange that pig-butchering scammers used.
Between 2006 and 2008 the FTC sued 16 data-broker and private-investigation defendants who pretexted telecom carriers.