Case Library / Pretexting & Impersonation / Federal Pretexting Prosecutions Post-2006: Bunch and Anderson Charged Under New Anti-Pretexting Statute (2008)
Pretexting & Impersonation Documented incident

Federal Pretexting Prosecutions Post-2006: Bunch and Anderson Charged Under New Anti-Pretexting Statute (2008)

In the first-ever prosecutions under the federal anti-pretexting statute Congress passed after the 2006 HP boardroom spying scandal, Nicholas Shaun Bunch and Vaden Anderson were separately charged in late 2008 with tricking T-Mobile and Sprint/Nextel into handing over customers' confidential call records: one by posing as the account holder with a name and partial Social Security number, the other by serving the carrier a fake federal court subpoena.

Share:

Social Engineering Examples·5 sources

What happened

In late 2008, federal prosecutors brought what the Department of Justice described as the first-ever criminal charges under 18 U.S.C. Section 1039, the pretexting statute Congress created via the Telephone Records and Privacy Protection Act of 2006 (signed into law January 12, 2007) as a direct legislative response to the 2006 Hewlett-Packard boardroom spying scandal, in which HP-hired investigators had used victims' Social Security numbers and impersonation to obtain journalists' and directors' phone records. Two unrelated defendants were charged: Nicholas Shaun Bunch, accused in the Northern District of Alabama (via criminal information) of using a T-Mobile customer's name and the last four digits of that customer's Social Security number to obtain the customer's confidential phone records; and Vaden Anderson, indicted by a federal grand jury on December 30, 2008 in the Northern District of Ohio (Case No. 1:08CR528) for serving Sprint/Nextel with a fictitious U.S. District Court civil subpoena to obtain a customer's confidential call records. Both cases turned on the same underlying vulnerability the 2006 law targeted: telecom carriers' processes for verifying who was entitled to receive a customer's call detail records were exploitable either through weak identity-verification scripts (name plus a partial SSN) or through insufficiently scrutinized legal-process paperwork.

How it worked

Bunch was charged with using a T-Mobile customer's name and the last four digits of that customer's Social Security number to obtain confidential phone records. Anderson used a different vector: he served Sprint/Nextel with what the indictment described as a fictitious U.S. District Court civil subpoena. The cited evidence does not establish the carriers' internal handling or verification steps.

The lure and the tell

Bunch's alleged method was social engineering aimed at a customer-service authentication process: presenting the subscriber's name and last four Social Security number digits as identity verification. The "tell" was that neither item is a strong secret. Anderson's method leaned on institutional trust in the form of legal process: he used a fictitious U.S. District Court civil subpoena to obtain confidential Sprint/Nextel records.

Outcome

Vaden Anderson, 28, was indicted by a federal grand jury on December 30, 2008 in the Northern District of Ohio for violating 18 U.S.C. Section 1039(a)(3) by providing Sprint/Nextel a fictitious civil subpoena to obtain confidential phone records. DOJ characterized this as the first indictment under the statute. Anderson pleaded guilty on March 11, 2009 and was sentenced on June 3, 2009 to 21 months in prison, two years of supervised release, and a $100 special assessment. Nicholas Shaun Bunch was separately reported by Wired as charged in November 2008 with using a T-Mobile customer's name and the last four digits of that customer's Social Security number to obtain confidential phone records. TLJ's report of an unnamed Northern District of Alabama information is not used to identify that matter as Bunch's case.

Why it matters

These cases matter as an early real-world test of the law Congress passed after the HP boardroom pretexting scandal. They pair two methods aimed at the same goal: the name-and-partial-SSN technique alleged in the charge against Bunch and the fictitious legal process underlying Anderson's conviction. For an education audience, the pairing illustrates that pretexting is a category rather than one technique: an attacker may target a support interaction or counterfeit institutional paperwork, so defenders must secure both channels.

Defenses

The two alleged methods illustrate distinct verification risks: reliance on static personal identifiers and reliance on an official-looking document. Carriers should use stronger account verification and independently confirm legal process with the purported issuing court through independently sourced contact information before releasing records.

Sources
Cite this case

Social Engineering Examples. “Federal Pretexting Prosecutions Post-2006: Bunch and Anderson Charged Under New Anti-Pretexting Statute (2008)”. Accessed 3 November 2026. https://socialengineeringexamples.com/federal-pretexting-prosecutions-bunch-anderson-2008

Attack Chain & Defense
1Reconnaissance
What happened

The public record does not describe exactly how Bunch obtained the victim's name and last four Social Security number digits, or how Anderson produced a document formatted to resemble a genuine U.S. District Court civil subpoena, but pretexting operations of this era typically relied on cheaply available personal data (data brokers, prior breaches, public records) for the name-plus-SSN-digits method, and on copying real court caption formats and case-numbering conventions, which are publicly visible on court filings, for the fake-subpoena method.

The control that would have stopped it

The underlying personal data (SSN digits, names) and public court-filing formats are widely available and hard to suppress at the source; the realistic control sits downstream, at Stage 4, where the institution receiving the pretext can be hardened rather than trying to keep this information from ever circulating.

2Pretext construction
What happened

The charge against Bunch alleged that he presented himself as the legitimate account holder using the customer's name and partial Social Security number; Anderson used a fictitious federal civil subpoena tailored to Sprint/Nextel's legal-process channel.

The control that would have stopped it

Because the pretext itself (a rehearsed phone script, a formatted paper document) leaves no trace before delivery, there is no practical pre-delivery control; defenses have to intercept the pretext at delivery and verification, covered in Stages 3 and 4.

3Delivery via the targeted channel
What happened

Bunch was alleged to have used the T-Mobile customer's identity information to seek the records; Anderson served his fictitious subpoena on Sprint/Nextel, using a channel intended for legal-process requests rather than customer authentication.

The control that would have stopped it

Restricting which channels can even reach an account or trigger a records release, for example requiring stronger verification for any phone-based CDR request and routing all purported legal process through a single, specifically trained compliance function rather than any inbound channel, narrows the attack surface Bunch and Anderson each exploited.

4Verification bypass
What happened

Bunch was charged with using a customer's name and partial Social Security number to obtain confidential T-Mobile records; Anderson was accused of providing Sprint/Nextel a fictitious federal civil subpoena. The supplied evidence does not establish the carriers' internal decision process.

The control that would have stopped it

Carriers should require stronger verification than static identity details, and legal-process staff should independently verify subpoenas with the issuing court through independently sourced contact information before releasing customer data.

5Exfiltration of confidential call records
What happened

Bunch was charged with obtaining a T-Mobile customer's confidential records using the customer's name and partial Social Security number; Anderson pleaded guilty after being charged with obtaining and attempting to obtain Sprint/Nextel records through a fictitious subpoena.

The control that would have stopped it

Once verification is bypassed, the carrier's own logging and anomaly detection is the backstop, for example flagging a name-plus-SSN request from an unrecognized inbound number or a subpoena whose docket number does not resolve at the stated court, before the disclosure is finalized rather than after.

6Downstream use and discovery
What happened

The cited accounts do not establish what either defendant did with the records after obtaining them. The conduct led to federal charges under 18 U.S.C. Section 1039, with a criminal charge reported against Bunch and a grand jury indictment against Anderson.

The control that would have stopped it

Neither defendant's downstream use of the records nor exactly how the scheme surfaced is documented in the available record, so there is no case-specific control to point to at this final stage; the durable defense remains upstream, at Stage 4's verification chokepoint, since once confidential records leave the carrier undetected, recovery depends on victim reporting or, as happened here, unrelated law-enforcement attention to the broader pretexting and data-broker ecosystem.

Quick Facts
Victim
Individual T-Mobile and Sprint/Nextel subscriber account holders whose confidential call detail records were obtained without their knowledge or consent
(identities not publicly disclosed in the available record)
Location
United States: N.D. Alabama
(Bunch, T-Mobile matter) and N.D. Ohio, Eastern Division, Cleveland (Anderson, Case No. 1:08CR528, Judge Christopher Boyko, Sprint/Nextel matter)
Date
2008-2009
(Bunch: charged in November 2008 per Wired's contemporaneous report; Anderson: indicted December 30, 2008, pleaded guilty March 11, 2009, and sentenced June 3, 2009)
Impact
No victim-loss figure is stated here.
Basisnot-a-lossAnderson's $250,000 figure was statutory maximum exposure, not an imposed fine or victim loss; DOJ reported a separately ordered $100 special assessment
Anderson faced a statutory maximum fine of $250,000, which was exposure rather than an amount imposed, and the DOJ reported that he was ordered to pay a $100 special assessment to the Crime Victim's Fund. No restitution payment or fine imposed on Bunch is asserted.
Status
Documented incident
Case Type
Real-World Incident
Sector
Telecommunications
Threat Actor
Unaffiliated Individual
Explore more

Related Cases

Browse by what this case has in common with others in the library.