Case Library / Phishing / Target's 2013 breach: a phished HVAC contractor as the way in
Phishing Documented incident

Target's 2013 breach: a phished HVAC contractor as the way in

Target's 2013 breach began with malware emailed to a small HVAC contractor. 40M cards and 70M records exposed. What's known, what's myth, and what it cost.

Share:

Social Engineering Examples·11 sources

Target's 2013 data breach began not at Target but at Fazio Mechanical Services, a small refrigeration and HVAC contractor in Pennsylvania. A malware-laden email at the contractor stole its login for Target's vendor systems. The attackers used it to get into Target's network and plant card-stealing malware on checkout terminals. Between 27 November and 15 December 2013, about 40 million payment cards were exposed, along with personal details for up to 70 million customers. Status: Documented incident.

Key takeaways

  • A small supplier was the way in. Its legitimate credentials made the attackers look like a trusted partner.
  • The popular story says the HVAC firm was connected to store thermostats. The firm itself said its link was only for billing, contracts and project management.
  • Nobody knows exactly what the phishing email said, or which Target system the stolen login opened.
  • Target reported $292 million in breach costs, or $202 million after insurance, by early 2017.

How it happened

Stage What happened
Research Target had vendor documents on public pages whose file details revealed internal network and user names
Phish the supplier A malware-laden email reached Fazio at least about two months before the card theft
Steal the login Password-stealing malware captured Fazio's credentials for Target's vendor systems
Get in The attackers logged in as a trusted vendor, around 15 November 2013
Move They reached more sensitive systems and the checkout terminals
Steal cards Malware read card data from memory at the till from 27 November to 15 December

Investigators told KrebsOnSecurity that Fazio's main protection against malware was the free consumer version of Malwarebytes, which doesn't scan in real time. Target announced the breach on 19 December 2013.

Tip: your security is only as good as your weakest supplier's. Treat vendor logins as a risk, not a convenience.

What's known and what isn't

Claim Status
The attack started with a stolen vendor login Well supported: Target's filings, the Senate report, Fazio's own statement
Fazio controlled store heating and cooling remotely False. Fazio said its connection was for billing, contracts and project management only
The login opened Target's Ariba billing system Likely, per one unnamed former Target staffer quoted by the Senate report
The malware was Citadel Named by two sources to KrebsOnSecurity; never confirmed
It was a targeted spear phish, not mass spam Unknown; sources lean different ways
What the email said Unknown. The Senate report guesses a PDF or Office attachment

The Senate Commerce Committee's 2014 "kill chain" report is widely cited, but it says itself that it relies on media reports and expert analyses, mostly KrebsOnSecurity. It faulted Target for rarely requiring two-factor login for small contractors, for weak separation between vendor systems and card systems, and for not acting on automated intrusion alerts. That's why this case also counts as supply-chain social engineering.

The cost

Item Amount Source
Cumulative breach expenses to January 2017 $292 million Target Form 10-K, fiscal 2016
Insurance recoveries $90 million Same
Net cost $202 million Same
Settlement with 47 states and Washington DC (May 2017) $18.5 million State attorneys general
Consumer class settlement fund (approved November 2015) $10 million, plus fees paid separately US District Court, Minnesota

The Senate report's "as many as 110 million" customers is an estimate combining the card and personal-data counts. Target's chief executive and chief information officer later left. No one has been charged over the intrusion.

What would have stopped it

  • Two-factor login for every vendor account, however small the supplier.
  • Keep vendor systems apart from payment and checkout networks.
  • Act on alerts. The Senate report says automated warnings were raised and not acted on.
  • Don't publish internal details in public documents and file metadata.
  • Ask suppliers about their security, including real-time malware protection.

See also spear phishing and credential harvesting.

Common questions

How did the Target breach happen?

Attackers stole login details from Fazio Mechanical, a small HVAC contractor, through malware sent by email. They used that vendor login to get into Target's network and install card-stealing malware on tills.

How many people were affected by the Target breach?

About 40 million payment cards and up to 70 million customer records. A Senate report estimated as many as 110 million customers in total.

How much did the Target breach cost?

Target reported $292 million in cumulative costs by January 2017, or $202 million after insurance, before an $18.5 million state settlement.

Did the HVAC company control Target's thermostats?

No. Fazio said its connection to Target was only for billing, contracts and project management.

Sources
  • A "Kill Chain" Analysis of the 2013 Target Data Breach (Majority Staff Report for Chairman Rockefeller). U.S. Senate Committee on Commerce, Science, and Transportation, Mar 26, 2014 (primary as a committee document, secondary as to the facts it recounts). Read as evidence with care: the report states its account is "based on media reports and expert analyses," and its footnotes for the vendor-compromise chain point to KrebsOnSecurity. Source for the "as many as 110 million" figure, the Eastern Europe exfiltration server, the Reconnaissance placement of the public-documentation metadata, the "would more than likely" hedge on Ariba access, the Malwarebytes finding, and the two-factor and segmentation criticisms. Re-fetched and quoted Sep 1, 2026.
  • Target Corporation Form 10-K, Commitments and Contingencies note (FY2013, year ended Feb 1, 2014). U.S. Securities and Exchange Commission (Target Corp. filing) (primary). Confirms approximately 40 million card accounts for guests who shopped between November 27 and December 15, 2013, and guest information for up to 70 million individuals. Its expense figures are FY2013 only: $61M gross, $44M insurance receivable, $17M net. Do not cite this filing for the cumulative $292M. Re-fetched Sep 1, 2026.
  • Target Corporation Form 10-K, Commitments and Contingencies note (fiscal 2016, year ended Jan 28, 2017). U.S. Securities and Exchange Commission (Target Corp. filing) (primary). The filing that carries the cumulative figures, verbatim: "Since the Data Breach, we have incurred $292 million of cumulative expenses, partially offset by insurance recoveries of $90 million, for net cumulative expenses of $202 million." Re-fetched Sep 1, 2026. Full filing at tgt-20170128x10k.htm.
  • Assurance of Voluntary Compliance, Target multistate settlement ($18,500,000). Connecticut Attorney General (multistate AGs) (primary). Paragraph 29 sets the $18,500,000 payment; paragraphs 17 and 18 set the segmentation, penetration-testing and two-factor requirements. Note the signatory count: the instrument itself is entered into by 46 states and the District of Columbia, with California settling in a parallel instrument per footnote 3, its payment drawn from the same total. Re-fetched Sep 1, 2026.
  • A.G. Schneiderman Announces $18.5 Million Multi-State Settlement With Target Corporation Over 2013 Data Breach. New York State Attorney General, May 23, 2017 (primary). The support for both "47 states and the District of Columbia" and "the largest multistate data breach settlement achieved to date." Lists all participating states including California. Re-fetched Sep 1, 2026.
  • In re: Target Corporation Customer Data Security Breach Litigation, MDL 14-2522, order list. U.S. District Court for the District of Minnesota (primary). The court's own docket page, listing the Mar 19, 2015 preliminary approval and the Nov 17, 2015 order approving the consumer settlement. The $10 million figure is the settlement fund capped in the preliminary approval order, with notice and administration costs and up to $6.75M in fees payable by Target separately. Re-fetched Sep 1, 2026.
  • Target Provides Preliminary Update on Second-Quarter Expenses Related to the Data Breach. Target Corporation, Aug 5, 2014 (primary). A single-quarter disclosure, not a cumulative one: Q2 2014 gross expenses of $148M offset by a $38M insurance receivable, including an accrual for payment-card-network claims. Re-fetched Sep 1, 2026.
  • Email Attack on Vendor Set Up Breach at Target. KrebsOnSecurity, Feb 12, 2014 (secondary). The reporting that broke the vendor-phishing angle and the origin of most downstream retellings. Two unnamed sources named Citadel, which the article says "could not be confirmed." The "shotgun attacks" framing is the reporter's own general observation, not a sourced finding about this campaign. Also the source for the public supplier-portal documentation and its file metadata. Re-fetched Sep 1, 2026.
  • Target Hackers Broke in Via HVAC Company (incl. full Fazio Mechanical official statement). KrebsOnSecurity, Feb 5, 2014 (secondary, and primary for the vendor statement it reproduces). Sources close to the investigation date the first network breach to Nov 15, 2013 and describe the test-then-scale POS rollout and drop servers in Miami and Brazil. Reproduces the vendor's statement in full, including that its Target data connection was exclusively for electronic billing, contract submission and project management and that it did not remotely monitor or control Target's HVAC systems. Re-fetched Sep 1, 2026.
  • Target vendor says hackers breached data link used for billing. Reuters, Feb 6, 2014 (secondary). Independent corroboration that a vendor representative confirmed the billing data connection as the entry point. Re-fetched Sep 1, 2026.
  • Ten Years Later, New Clues in the Target Breach and An Interview With the Target & Home Depot Hacker. KrebsOnSecurity, Dec 14, 2023 and Nov 14, 2024 (secondary). Single-outlet identification of the "Rescator" card-shop handle, plus the subject's own confirmation and his claim that his team wrote the card-stealing malware. Neither article mentions the vendor, HVAC or the phishing, and no conviction relating to this breach has been reported, so this record does not name him and does not treat the claim as attribution. Re-fetched Sep 1, 2026.
Cite this case

Social Engineering Examples. “Target's 2013 breach: a phished HVAC contractor as the way in”. Accessed 3 November 2026. https://socialengineeringexamples.com/target-fazio-hvac-vendor-phishing-breach-2013

Attack Chain & Defense
1Phishing delivery to the vendor
What happened

attackers sent malware-laced email to employees at Fazio Mechanical, an HVAC and refrigeration contractor, at least about two months before the card theft began. Whether this was a broad untargeted blast or a selected one is not settled in public sources: KrebsOnSecurity offered the mass-blast reading as a general pattern, "Many of these email malware attacks start with shotgun attacks", while the Senate staff report places the emails alongside attacker reconnaissance of Target's vendor ecosystem. Two of Krebs's sources named the malware as Citadel, a Zeus-derived password stealer, and both Krebs and the Senate report state this was never confirmed.

The control that would have stopped it

standard email security controls, being attachment sandboxing/detonation, spam and malware filtering, and staff training on unexpected attachments, catch malware-laden email whether it arrives as a broad blast or a selected one. The Senate report names training staff to recognize and report phishing emails as the control missing at this step.

2Vendor compromise and credential harvesting
What happened

the malware ran undetected at Fazio Mechanical, whose primary anti-malware was the free, on-demand-only version of Malwarebytes, which offers no real-time protection and is licensed for individual use (investigators via KrebsOnSecurity, repeated by the Senate report). It captured the vendor's login for Target's vendor-facing systems. Which system was never established publicly: the Senate report says only that the vendor "would more than likely" have had access to Target's Ariba external billing system, on the account of one unnamed former Target security team member.

The control that would have stopped it

business-grade endpoint protection with real-time (not on-demand-only) detection, contractual security baselines for vendors, and MFA on vendor accounts, so a stolen static password alone cannot be reused to authenticate.

3Attacker-side reconnaissance and victim selection
What happened

attackers triaged which infected machines were worth pursuing, and Target's own public web properties helped. The Senate report files under Reconnaissance that Target's supplier and facilities-management pages, which required no login, carried HVAC vendor files whose metadata "allowed the attacker to map Target's internal network prior to the breach."

The control that would have stopped it

an attacker's triage of which infected victims are worth pursuing happens on the attacker's own systems and cannot be observed or blocked by the victim organization. What can be controlled is the open-source half: the Senate report's recommendation at this step is that Target "could have limited the amount of publicly available vendor information", which means keeping supplier documentation behind a login and stripping file metadata that exposes internal domain and user names.

4Initial access via stolen vendor credentials
What happened

attackers authenticated into Target-facing systems from outside using the vendor's legitimate login, entering as an apparently trusted third party rather than as an unauthorized intruder. Investigators told KrebsOnSecurity the first breach of Target's network was Nov 15, 2013.

The control that would have stopped it

enforce multifactor authentication for all vendor and remote logins, the specific gap the Senate report identifies, so possession of a stolen password is insufficient to gain access.

5Movement into the cardholder environment
What happened

from the low-privilege vendor-facing foothold, attackers reached more sensitive parts of Target's network. How they escalated was never established publicly. The Senate report states it is "unclear exactly how the attacker could have escalated its access from the Ariba external billing system to deeper layers of Target's internal network", and the only explanation offered anywhere is one anonymous former insider's guess that the outside portal was not fully isolated from the rest of the network.

The control that would have stopped it

network segmentation isolating vendor-facing systems from the cardholder-data environment, least-privilege access scoping for vendor accounts, and penetration testing that proves the segmentation holds rather than assuming it. The 2017 multistate settlement required exactly these of Target: mapping every connection into the cardholder-data environment, segmenting it from the rest of the network, and running a risk-based penetration testing program.

6Missed detection
What happened

Target's own automated intrusion-detection and anti-malware alerting tooling generated warnings as the intrusion progressed, but per the Senate staff report these alerts were not acted upon in time to stop the attack.

The control that would have stopped it

enforced alert-triage and incident-response processes and staffing, so automated security-tooling warnings trigger investigation and containment rather than being logged and ignored.

7POS malware deployment
What happened

attackers installed RAM-scraping malware onto a small number of point-of-sale registers first to test it, then scaled it to a majority of Target's US store registers to capture card track data directly from live transactions in memory. The test-then-scale sequence appears both in the Senate report timeline and in KrebsOnSecurity's reporting from investigators.

The control that would have stopped it

POS hardening such as point-to-point encryption or tokenization so card data is never available in cleartext in register memory, plus file-integrity monitoring to flag new or unauthorized executables on point-of-sale systems.

8Exfiltration and monetization
What happened

stolen card and customer data was moved out of Target's network to external staging infrastructure. The Senate report's summary names a server in Eastern Europe; the same report and KrebsOnSecurity also describe compromised drop servers elsewhere, including in Miami and Brazil. The card data was then sold through underground card-shop markets, completing the attackers' financial objective.

The control that would have stopped it

egress monitoring and data-loss-prevention controls, plus network flow-anomaly detection, to catch unusual outbound transfers of large data volumes to unfamiliar external destinations before they complete.

Quick Facts
Victim
Target Corporation
(retailer); initial victim: Fazio Mechanical Services, a refrigeration/HVAC contractor in Sharpsburg, Pennsylvania
Company
Target Corporation
Location
United States (Target stores nationwide; vendor in Sharpsburg, PA; Target data centers in Minnesota)
Date
2013-11 to 2013-12
(breach window; POS card capture Nov 27 to Dec 15, 2013 per Target's FY2013 Form 10-K; first network breach dated Nov 15, 2013 by investigators via KrebsOnSecurity; vendor phishing began at least about 2 months earlier; publicly disclosed Dec 19, 2013)
Impact
~40M payment card accounts (Nov 27 to Dec 15, 2013) and up to 70M customer PII records exposed, per Target's Form 10-K for FY2013 filed Mar 2014: measured.
BasismeasuredCumulative expenses and insurance recoveries per the Form 10-K
The Senate staff report put the total at "as many as 110 million Target customers", Mar 2014: estimated. Target's Form 10-K for fiscal 2016, year ended Jan 28, 2017, states: "Since the Data Breach, we have incurred $292 million of cumulative expenses, partially offset by insurance recoveries of $90 million, for net cumulative expenses of $202 million": measured, and it predates the May 2017 state settlement. Settlements: $18.5M to 47 states and DC, May 2017, the largest multistate data-breach settlement to that date per the participating attorneys general: measured. A $10M consumer class settlement fund, final approval Nov 17, 2015 in In re Target Corp. Customer Data Security Breach Litigation, D. Minn., with notice, administration and up to $6.75M in fees paid separately by Target: measured. Separate settlements with payment-card networks and banks followed.
Status
Documented incident
Case Type
Real-World Incident
Sector
Financial Services & Insurance, Manufacturing & Industrial, Retail & E-commerce
Threat Actor
unknown
Explore more

Related Cases

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