Case Library / Pretexting & Impersonation / Retired General's Phone Records Pretexting Incident (2005-2006)
Pretexting & Impersonation Documented incident

Retired General's Phone Records Pretexting Incident (2005-2006)

A phone-record pretexting incident involving a retired U.S. Army general was followed by FTC enforcement and broader privacy-policy scrutiny.

Share:

Social Engineering Examples·11 sources

What happened

An online data-broker site obtained 100 consecutive calls made to and from a retired U.S. Army general's personal T-Mobile (Omnipoint) cell phone between Nov. 15 and 18, 2005, by pretexting the carrier: impersonating the account holder to a customer-service representative to get the call log released. In January 2006, blogger John Aravosis of AMERICAblog purchased that call log for $89.95, needing only the retired general's cell number and a credit card, and received the data within 24 hours. Aravosis had first tested the market on himself, buying his own Cingular Wireless records for $110 from a related site. He published the purchase on AMERICAblog on Jan. 12, 2006, as a proof-of-concept that private communications metadata could be bought online with little buyer verification.

How it worked

Web-based data-broker sites advertised the ability to produce a target's cell-phone call log for a fee, needing only the target's phone number and a credit card. Behind the storefront, brokers or subcontracted information specialists used pretexting by misrepresenting identity or authority to induce carrier personnel to release call-detail records. The broker then repackaged that data and sold it to the online purchaser.

The lure and the tell

The lure operated on two levels. First, data-broker sites attracted paying customers with a simple e-commerce promise of obtaining someone's call log from limited identifying information. Second, inside the transaction, the broker's pretext to the carrier involved impersonation or other misrepresentation to obtain the records. The transaction was publicly disclosed by John Aravosis on AMERICAblog as a proof-of-concept.

Outcome

An EPIC petition to the FCC described online data brokers offering telephone call records with only a telephone number and short turnaround times, and argued that existing authentication standards were insufficient to prevent unauthorized access to CPNI. The episode therefore fits a broader documented concern about weak carrier authentication, rather than establishing that this single disclosure triggered every later enforcement or legislative action.

Why it matters

This incident concerns the commercial sale of phone records and subsequent regulatory scrutiny. It illustrates privacy risks from unauthorized release of account records.

Defenses

The episode exposed the risk that weak carrier authentication could let pretexters impersonate account holders to obtain call-detail records. The broader control lesson supported by the EPIC petition is to strengthen authentication before releasing CPNI or similar account data by phone.

Sources
Cite this case

Social Engineering Examples. “Retired General's Phone Records Pretexting Incident (2005-2006)”. Accessed 22 October 2026. https://socialengineeringexamples.com/public-official-phone-records-pretexting-2006

Attack Chain & Defense
1Target selection and number acquisition
What happened

The broker needed only the subject's cell number to begin, not privileged access; reporting from the period indicates such numbers circulated through personal contacts, prior press coverage, or public directories, reflecting how low the entry bar was for targeting even a high-profile figure like the retired general.

The control that would have stopped it

A public figure's phone number is nearly impossible to fully suppress once it has circulated through contacts, campaigns, or prior reporting; the realistic control is not hiding the number but hardening what a caller can do with it once obtained, which is addressed at Stage 3.

2Pretext identity-building
What happened

Consistent with contemporaneous reporting on the same broker market (commercial data-broker lookup services and cross-referenced personal data such as partial SSNs or dates of birth), brokers and their subcontracted "information specialists" typically assembled enough identifying detail about the account holder to sound plausible to a carrier's phone-based verification process.

The control that would have stopped it

Limiting how much identity-verifying data (partial SSNs, dates of birth) commercial data-broker and people-search services expose for lookup or resale reduces the raw material pretexters use to sound convincing; this is a data-minimization control on the broader personal-data industry rather than on the phone carrier itself.

3Pretext call to the carrier
What happened

A broker employee called the carrier's (T-Mobile/Omnipoint's) customer-service line impersonating the account holder and used the gathered details to talk a representative into reading out or faxing the call-detail records, exploiting reps trained to be helpful toward callers who "sounded like" the customer rather than treating the request as adversarial.

The control that would have stopped it

Carriers should require stronger account-specific authentication before releasing CPNI or call-detail records by phone, rather than relying on a caller sounding like the account holder.

4Data packaging and storefront listing
What happened

The broker aggregated the extracted call log and listed a fee-for-any-target lookup service on a public e-commerce storefront, advertising fast turnaround with no check on the buyer's identity, intent, or relationship to the subject.

The control that would have stopped it

The record documents five FTC actions in 2006 and an FCC Notice of Apparent Liability involving 1st Source Information Specialists d/b/a LocateCell.com; the supplied FCC order states that the forfeiture issue was failure to respond to a subpoena, not the CPNI disclosure itself.

5Commercial purchase
What happened

John Aravosis paid $89.95 online with nothing more than the retired general's cell number and a credit card, received the 100-call log within about 24 hours.

The control that would have stopped it

Requiring documented buyer purpose or written customer authorization before a broker or carrier releases any call-detail data mirrors the consent standard Public Law 109-476 later imposed criminally on exactly this no-questions-asked resale model.

6Disclosure and follow-up
What happened

The transaction was publicly disclosed, and the episode was followed by FTC enforcement actions.

The control that would have stopped it

After a disclosure, organizations should use responsible disclosure and incident-response procedures rather than assume exposed records can be contained retroactively.

Quick Facts
Victim
A retired U.S. Army general
(former NATO Supreme Allied Commander Europe, 2004 Democratic presidential candidate); secondarily, T-Mobile/Omnipoint Communications and Cingular Wireless as the carriers whose CPNI-release procedures were exploited
Location
United States (national; purchase transaction online, subject and blogger both US-based)
Date
2005-11-15 to 2006-01-12
(records obtained Nov 15-18, 2005; purchased and publicized by AMERICAblog on/around Jan 12, 2006)
Impact
The case records five FTC enforcement actions filed in May 2006.
BasisunquantifiedThe enforcement-action count is not a financial amount; the monetary evidence remains unresolved.
That count is not a monetary loss measure; case-specific financial loss and monetary relief remain subject to source verification.
Status
Documented incident
Case Type
Real-World Incident
Sector
Government & Public Sector, Media & Entertainment, Professional & Business Services, Telecommunications
Threat Actor
Organized Crime
Explore more

Related Cases

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

GAO Covert Testers Use Counterfeit Law-Enforcement Credentials and Forged Building Passes to Breach Federal Buildings (2000-2009)

Three separate congressional watchdog engagements, not one campaign. In 2000, GAO agents carrying counterfeit badges declared themselves armed officers and…

Incident 2000Read →

Ahmedabad Aadhaar Deepfake e-KYC Loan Fraud (2026)

Ahmedabad police alleged that an interstate gang used AI-generated "eye-blink" deepfake videos made from stolen social-media photos to fool Aadhaar…

Incident 2026Read →

FTC Task-Scam / Gamified Job-Scam Data Spotlight (December 2024)

FTC's December 2024 Data Spotlight quantified an explosion in "task scams," gamified job-offer frauds launched via unsolicited text/WhatsApp messages, showing…

Incident 2024Read →

DOJ/IRS-CI Unseal $65M Alleged "Mistaken Refund" Elder-Fraud Indictments Against 28 Defendants

DOJ/IRS-CI unsealed four indictments charging 28 defendants in an alleged Chinese organized-crime money-laundering network tied to India-based call-center scams that…

Incident 2025Read →

Yujing Zhang Mar-a-Lago Intrusion

A Chinese national entered Mar-a-Lago after a pool-visit pretext and staff's unverified assumption that she was related to a member.…

Incident 2019Read →

Cabarrus County $1.7M vendor-impersonation BEC (2019)

Scammers impersonating a school construction contractor submitted a bank-account-change request with seemingly valid documentation, and Cabarrus County, NC wired $2.5M…

Incident 2018Read →